A widget on your website only reaches people who visit your website. These integrations put the same agent — same knowledge, same prompt, same citations — inside the tools your customers and colleagues are already in. Everything below is configured from the Integrations page in a bot's sidebar.
1. What connects to what
| Channel | Audience | How it connects |
|---|---|---|
| Slack | Internal teams | OAuth — install the app into a workspace |
| Microsoft Teams | Internal teams | Azure bot registration credentials |
| Discord | Communities | Bot token from the Discord Developer Portal |
| Telegram | Consumers, international | Bot token from @BotFather |
| Consumers, support | Meta WhatsApp Business API credentials | |
| Zendesk | Support teams | Subdomain, admin email and API token |
| Zoho Desk | Support teams | OAuth |
| Notion | Internal knowledge | OAuth |
2. Slack
The lowest-friction integration on the list, and the one most teams get value from first. Slack uses OAuth, so there are no credentials to create or paste.
- 1
Start the install from Integrations
Open the bot's Integrations page and choose Slack.
- 2
Approve in Slack
Slack shows exactly what the app can do and asks you to pick a workspace. You need permission to install apps there — in many organisations that means a Slack admin does this step.
- 3
Invite the bot into channels
Installing does not put it anywhere. Invite it into the channels it should serve — start with one, not all of them.
- 4
Ask it something
Mention it with a question you know the answer to. If it answers from your knowledge base, the connection is real.
Connected workspaces are listed on the Integrations page, so you can see and revoke what is installed.
3. Microsoft Teams
More involved than Slack, because Teams bots are registered in Azure rather than installed from a marketplace. You will need:
| Field | Where it comes from |
|---|---|
| Microsoft App ID | Your Azure bot registration |
| App Password (client secret) | Generated alongside the App ID |
| Tenant ID | Optional — leave empty for a multi-tenant bot, set it to lock the bot to one organisation |
| Bot display name | Optional — what your colleagues see |
A setup code flow is also available for connecting an already-registered bot. Once connected, use the connection's test action before announcing it — Teams misconfigurations tend to fail silently rather than loudly.
4. Discord
Create an application in the Discord Developer Portal, add a bot to it, and paste the bot token into the Discord card on the Integrations page. Once connected, the page lists the servers the bot is in, and you can disconnect or reconnect without recreating the application.
5. Telegram
The quickest of the token-based integrations. Message @BotFather on Telegram, run /newbot, and it hands you a token that looks like 123456789:ABCdefGhIJKlmNOPQRstUVwxyz. Paste it into the Telegram card and connect.
Telegram is worth considering wherever your audience is international — it has reach in markets where WhatsApp does not, and unlike WhatsApp it needs no business verification.
6. WhatsApp
The heaviest setup here, because Meta requires a verified WhatsApp Business account before you can send anything. Budget real time for the Meta side; the Chat.co side is five fields.
| Field | Where it comes from |
|---|---|
| Permanent Access Token | Meta Developer Portal |
| Phone Number ID | Your WhatsApp Business number in Meta |
| Business Account ID | Meta Business Suite |
| Display Phone Number | The number customers will see |
| Webhook Verify Token | A secret you choose, then enter identically in the Meta Developer Portal |
Broadly, the order is:
- Create a WhatsApp Business account in Meta Business Suite
- Create an app with the WhatsApp product in the Meta Developer Portal
- Generate a permanent access token and collect the IDs above
- Enter everything into the WhatsApp card here and connect
- Set the webhook URL and verify token on the Meta side to match
7. Zendesk & Zoho Desk
These are a different shape from the chat channels. Rather than giving customers a new place to talk to your bot, they connect your bot to where your support team already works — so escalations arrive as tickets inside your existing queue, assignment rules and SLAs.
Zendesk
Three fields, all from your Zendesk instance:
- Subdomain — the
mycompanyinmycompany.zendesk.com - Admin email — an admin account on that instance
- API token — created in Zendesk Admin Center
Zoho Desk
OAuth — authorise from the Integrations page and grant access. No tokens to copy. Zoho Desk tickets can be created directly from handoff requests, which is the main reason to connect it.
8. Notion
Notion connects over OAuth and is about knowledge rather than conversation: it links the bot to Notion content your team maintains, so the answers track the workspace instead of a snapshot you uploaded once.
Worth it when Notion is genuinely where your documentation lives. If your Notion is half-finished — as most are — fix that first; connecting it does not improve it.
9. Running a multi-channel bot
Connect one channel and let it settle
Each channel surfaces different failure modes. Slack users ask in fragments; WhatsApp users expect brevity; Discord users test the boundaries for entertainment. Learning that on one channel is manageable; learning it on five at once is not.
Test every connection before you announce it
Most of these cards expose a test action. Use it. A channel that looks connected but silently fails is worse than one that was never set up, because people stop asking.
Treat internal and external as different bots
The knowledge base is shared across every channel attached to a bot. There is no per-channel content filter. If a document should reach your staff and not your customers, it belongs in a separate bot — see managing multiple bots.
Watch the credentials
Tokens expire, get rotated, and get revoked when someone leaves. When a channel goes quiet, check the connection status on the Integrations page before assuming the bot broke.