Link Slack, Discord, WhatsApp and Eleven Other Channels to Your AI Agent
The Channels page in Settings can reach your agent from fifteen different messaging platforms — here's the full list and how pairing actually works.
Most agent or assistant products let you talk to them through a chat window and, if you're lucky, Slack. Settings' Channels page connects your agent to fifteen: Telegram, Email, Slack, Discord, WhatsApp, LINE, ntfy, SMS, Mattermost, Feishu, Matrix, Microsoft Teams, Google Chat, DingTalk, and WeCom.
How linking works
Each channel is its own adapter, built and deployed independently — a compromised or misbehaving adapter is scoped to one channel rather than the whole platform. To link one, you request a pairing code from Settings while signed in, then provide that code on the channel itself (say, sending it to your agent's Telegram bot, or pasting it wherever that platform expects it). Once the code is confirmed, that channel identity is linked to your account and the agent can be reached through it.
Why fifteen separate paths instead of one generic connector
Every adapter points at its own fixed backend path — nothing here is a template that gets filled in with whatever a user requests. That's a deliberate allowlist rather than a flexible system, because a flexible "point at any messaging platform" design would mean a caller effectively choosing which backend service handles their request. Keeping the list closed and explicit means every channel that shows up here is one that's actually been built and reviewed, not a generic pass-through.
Checking what's linked
Settings shows your linked channels as one combined list, pulled from all fifteen adapters at once, even though each one is backed by an entirely separate service. You don't need to know or care which worker holds which bot token — you see "my channels," the same way you'd think about it.
What to expect if a channel isn't configured on your deployment
Not every workspace has every one of the fifteen channels set up — that's normal, not a bug. See the companion piece on why an unavailable channel doesn't take down the rest of the list; the short version is that each adapter fails on its own without affecting the others.
Getting started
If your team is already using Slack or Discord day to day, those are usually the highest-value first connections — they put the agent where the conversation already happens rather than adding one more place to check.