Skip to main content
Join the waitlist

Connectors.

Discord, Telegram and Slack at launch. Each platform limits what a connector can read, and every limit is listed here.

  • Discord

    Available at launch

    Bot install, no admin ticket for servers you manage

    Install the bot on a server you manage and pick the channels. Message Content is a privileged intent and the limits are real.

    What the Discord connector reads

  • Telegram

    Available at launch

    Add the bot to a chat, no approval needed

    The quickest setup of the three, and the most restricted. In groups the bot sees only messages addressed to it, unless an admin turns privacy mode off.

    What the Telegram connector reads

  • Slack

    Available at launch

    One workspace app install, done by somebody who can install apps

    One install path: the workspace app, added to a workspace by someone allowed to add apps to it. Public and private channels only, and no history from before the install.

    What the Slack connector reads

Everything else

Not at launch.

Some of these are being built. Some of them are gates held by somebody else, and one of them is never happening. They are written the same way, because the only version of this list worth reading is the one that tells you when the answer is no.

  • Microsoft Teams

    Next

    The same per-channel opt-in model, subject to Microsoft's own app validation and to the tenant admin consenting. Of everything on the roadmap this is the one with the fewest obstacles in front of it.

  • WhatsApp Business

    Depends on Meta

    The Business Cloud API is the only lawful route, and Meta's terms let it refuse providers whose primary function is AI, at its own discretion. We are one. So this is an application we intend to make rather than a date we can give you. Personal WhatsApp has no API at all and never will.

  • Gmail

    Not at launch

    Reading a Gmail mailbox needs a paid third party security assessment that takes about six weeks the first time and then recurs every year for as long as the product reads Gmail. It is a funded project rather than a connector, so it is not being promised for launch.

  • LinkedIn

    Never

    Out of scope permanently. There is no third party read access to LinkedIn messages, and LinkedIn's caching rules cap how long ordinary profile data may be held at hours, which an ordinary database with nightly backups cannot honour.

Personal WhatsApp is not on that list and it is not coming. There is no API for a personal WhatsApp account, and the tools that claim to read one are breaking the WhatsApp terms of service on your behalf. If a tracker tells you it covers your personal WhatsApp, that is the thing it is doing.

Connecting a work account?

The security page covers redaction, retention, where the data is stored and what deletion actually removes.

Read the data handlingJoin the waitlist