.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
One of the things that makes ZeroClaw interesting compared to building separate bots for each platform is that a single agent instance can serve multiple messaging channels at once. You configure it once, connect Telegram and Discord and WhatsApp (and Slack, Signal, Matrix, Email or any of the 20+ supported channels), and the same AI assistant with the same memory and personality answers on all of them. No duplication, no separate configs per platform.
This guide walks through adding multiple channels to an existing ZeroClaw setup. I'm assuming you've already got ZeroClaw running with at least one channel. If you're starting from scratch, the VPS setup guide covers the initial configuration.
How multi-channel works in ZeroClaw
Every channel in ZeroClaw implements the same Channel trait. When a message arrives from any channel, it goes through the same agent pipeline: the message is processed, context is loaded from memory, the AI provider generates a response and the response is routed back to whichever channel the message came from. Memory is shared across channels by default, which means your assistant on Telegram knows about conversations you had on Discord.
This shared-memory behavior is usually what people want, but it's worth being aware of. If you tell your bot something private on Telegram, that context could surface in a Discord response if it's relevant. For most personal or team setups that's fine. If you need channel-isolated memory, that requires running separate ZeroClaw instances with different config files.
Add Telegram
If you haven't set up Telegram yet, create a bot through @BotFather on Telegram (send /newbot, pick a name and username, copy the token). Then bind it:
zeroclaw channel bind-telegram YOUR_TELEGRAM_BOT_TOKENThe full Telegram guide covers BotFather settings, privacy mode and voice messages if you want more detail.
Add Discord
Discord requires a bit more setup than Telegram because you need to create an application in the developer portal.
Go to the Discord Developer Portal, click "New Application" and give it a name. Navigate to the Bot section in the left sidebar and click "Add Bot." Copy the bot token.
This is the step most people miss: under the Bot section, scroll down to "Privileged Gateway Intents" and enable Message Content Intent. Without this, ZeroClaw connects to Discord but can't read any messages. The bot will connect and immediately disconnect in a loop, throwing "Invalid Session" errors, and nothing in the ZeroClaw logs explains why. It's the single most common Discord integration issue.
Now generate an invite link. Go to OAuth2 > URL Generator, check the "bot" scope, then add permissions for "Send Messages", "Read Message History" and "Read Messages/View Channels." Copy the generated URL, open it in your browser and add the bot to your Discord server.
Back on your VPS, bind the channel. The exact command depends on your ZeroClaw version, but the general approach is to add the Discord token to your config or use the channel binding command. Check zeroclaw onboard and select Discord as the channel type, then paste your bot token when prompted.
If you've done Discord integrations with OpenClaw before, our OpenClaw Discord guide covers the portal setup in more detail. The developer portal steps are identical for both projects.
Add WhatsApp
ZeroClaw supports two WhatsApp connection methods, and the right choice depends on your situation.
WhatsApp Web (via whatsapp-rust) — This connects through WhatsApp Web, the same way your browser connects to WhatsApp. You scan a QR code from your personal WhatsApp account and ZeroClaw bridges through that session. It's the fastest way to get started and doesn't require any business verification. The downside is reliability: if your phone loses internet or WhatsApp ends the web session, ZeroClaw loses the connection. For personal use or testing, it's fine. For anything production-grade, it's fragile.
WhatsApp Business Cloud API — This is Meta's official API for businesses. It requires a Meta Business account and application approval, which takes a few days. Once set up, it's far more stable than the Web method because it doesn't depend on your phone being online. If you're building something other people will rely on, this is the route to take.
For both methods, the channels reference documentation has the specific configuration fields you'll need in config.toml.
Verify all channels are active
After adding your channels, check the full list:
zeroclaw channel listEach channel should show as active. Run diagnostics across all of them:
zeroclaw channel doctorThis tests connectivity for every bound channel and reports problems individually. If one channel is down, the others continue working independently. A Telegram outage doesn't affect your Discord bot, and vice versa.
Testing across channels
Send a message on each platform and verify you get responses. Then test the shared memory: tell your bot something specific on Telegram ("My favorite programming language is Rust"), then ask about it on Discord ("What's my favorite language?"). If memory is working correctly, the Discord response should reflect what you said on Telegram.
Keep an eye on response times across channels. Telegram and Discord responses are usually fast (1-3 seconds for a cloud API). WhatsApp can be slightly slower due to the message relay, especially with the Web method. If one channel is noticeably laggy, zeroclaw channel doctor will often identify the bottleneck.
If you're coming from an OpenClaw setup, we wrote a similar multi-channel guide for OpenClaw that covers some of the same platform-specific gotchas. The channel configuration format differs between the two projects, but the platform-side setup (BotFather, Discord portal, WhatsApp Business) is identical.
