Channels
The web UI is enough. Telegram, Discord, WhatsApp, and WeCom reach the same chat. A channel does not grow its own agent. Replies are directional: a channel only receives responses to messages it sent. The desk still shows every message.
If the process binds beyond this machine, set a web auth token. See Setup wizard.
Add a bot
Section titled “Add a bot”Settings → Integrations → Add bot instance. Restart Meido before the bot can answer. Telegram and Discord can have more than one bot. WhatsApp and WeCom support one app or number on this Meido.
| Platform | What to paste |
|---|---|
| Telegram bot | Bot token. Optional numeric group ids. Empty means all groups. |
| Discord bot | Bot token. Optional channel ids. Empty means all channels. |
| WhatsApp number | The single WhatsApp Business number. |
| WeCom bot | Long connection: Bot ID and Secret from a 智能机器人 with API mode set to 长连接. No HTTPS callback. Self-built app: token and EncodingAESKey that match the admin console, and the receive URL https://your-host/callback after restart. Allowed ids are chatid or userid, not the group name. |
Shared access is one comma-separated list of those ids across platforms.
Legacy channel variables in .env are imported once on the first boot after an upgrade. After that, tokens live in this screen.
Who answers
Section titled “Who answers”Settings → Channels is External channel persona mode. The next message from that bot uses the choice.
Telegram, Discord, and WeCom can answer as all personas or as one persona. WhatsApp stays on one persona. Focused sessions stay in the web UI. On main chat, topics still separate stretches of the continuous thread. A bot that is not linked yet shows pending link.
The persona marked active in the sidebar is the one channel messages route to when the mode is a single persona.