OpenClaw channels: three ways to connect a chat app

Choose by where you want to talk

The official channel catalog lists the supported services and which plugins they need. A channel is not a model provider: Telegram carries your messages, while your chosen model generates the agent’s response. Connecting another messenger does not itself change that model.

• Telegram is OpenClaw’s suggested first channel: create a bot, connect its token and approve access. It does not need a dedicated phone number for the bot.
• WhatsApp links to a real account with a QR scan. Decide whose number the agent will speak from before linking.
• Discord and Slack fit work already happening in servers or workspaces. Their app permissions and room access are part of setup.
• Signal uses a Signal account and its bridge; iMessage needs a signed-in Mac in the connection, even when the agent runs elsewhere.
• Google Chat and Twilio SMS send events to a webhook. The service must be able to reach the configured URL.

Three ways to add a channel

Ask the agent from a working chat

You do not have to leave Telegram to begin connecting another service. As of September 2026 (OpenClaw 2026.9.2), a request in chat starts WhatsApp and Discord setup, and Slack connects through the agent too. You still supply the provider credentials, or scan the QR, and approve access. Asking the agent delegates setup work, not ownership of those decisions.

Use the secure credential form when OpenClaw opens one, not an ordinary chat message containing a token. If a plugin install restarts the Gateway and interrupts setup, reconnect and check what was installed before beginning again. If an approval immediately becomes cancelled on 2026.9.1, the version-specific approval fix is the first thing to check.

Use the control panel

Open Channels in the OpenClaw Control UI. As of September 2026, it has guided setup rows for the listed channels, with DM access requests alongside them. The panel is useful for seeing the connection and pending permissions in one place. A listed setup flow is not proof that the provider connection has completed: WhatsApp’s guided panel path, for example, can fail at linking.

Use the CLI

openclaw channels add
openclaw channels list
openclaw channels status --probe

The channels command reference covers provider-specific options and login commands. Adding an account, logging it in and admitting a sender are separate steps. A configured channel may still need a QR login; a connected channel may still be waiting for your pairing approval.

Connection method matters on a server

Telegram, Discord and Slack’s Socket Mode work without a provider calling a public port on the agent’s machine, and WhatsApp keeps a linked session. Webhook-based services have the opposite direction: their servers call yours. A successful outbound internet check cannot prove that inbound path exists.

For a machine behind NAT, a tunnel or managed public endpoint can provide the inbound URL without opening a router port. Keep that URL stable across restarts and retain the service’s authentication checks. The n8n and webhook guide covers that distinction for automation calls.

Test the conversation, not just the status

Send a message from the account you intend to use, complete its access request, and confirm a reply in that same app. For an always-on installation, verify again after a restart. On 2026.9.2, WhatsApp, Discord and Slack connections come back after one, but only the check shows that yours did; a channel appearing in the catalog does not.