Chat Channels: Messaging Platforms OpenClaw Connects To
OpenClaw connects to chat apps you already use via the Gateway. This page lists supported channels including Discord, Feishu, Google Chat, iMessage, and IRC.
Read this when
- You want to choose a chat channel for OpenClaw
- You need a quick overview of supported messaging platforms
OpenClaw can communicate with you through any chat app you already use. Every channel connects via the Gateway. Text works everywhere; media and reactions differ by channel.
iMessage, Telegram, and the WebChat UI come with the core install. Channels labeled
"official plugin" install with one command (openclaw plugins install @openclaw/<id>)
or on demand during openclaw onboard / openclaw channels add, then require a Gateway
restart. "External plugin" channels are maintained outside the OpenClaw repo.
Supported channels
- Discord - Discord Bot API + Gateway; supports servers, channels, and DMs (official plugin).
- Feishu - Feishu/Lark bot via WebSocket (official plugin).
- Google Chat - Google Chat API app via HTTP webhook (official plugin).
- iMessage - Included in core. Native macOS integration via the
imsgbridge on a signed-in Mac (or SSH wrapper when the Gateway runs elsewhere), including private API actions for replies, tapbacks, effects, attachments, and group management. - IRC - Classic IRC servers; channels + DMs with pairing/allowlist controls (official plugin).
- LINE - LINE Messaging API bot (official plugin).
- Matrix - Matrix protocol (official plugin).
- Mattermost - Bot API + WebSocket; channels, groups, DMs (official plugin).
- Microsoft Teams - Bot Framework; enterprise support (official plugin).
- Nextcloud Talk - Self-hosted chat via Nextcloud Talk (official plugin).
- Nostr - Decentralized DMs via NIP-04 (official plugin).
- QQ Bot - QQ Bot API; private chat, group chat, and rich media (official plugin).
- Reef - Guarded, end-to-end-encrypted claw-to-claw messaging between OpenClaw agents of different people (bundled plugin).
- Raft - Raft CLI wake bridge for human and agent collaboration (official plugin).
- Signal - signal-cli; privacy-focused (official plugin).
- Slack - Bolt SDK; workspace apps (official plugin).
- SMS - Twilio-backed SMS through the Gateway webhook (official plugin).
- Synology Chat - Synology NAS Chat via outgoing+incoming webhooks (official plugin).
- Telegram - Included in core. Bot API via grammY; supports groups.
- Tlon - Urbit-based messenger (official plugin).
- Twitch - Twitch chat via IRC connection (official plugin).
- Voice Call - Telephony via Plivo, Telnyx, or Twilio (official plugin).
- WebChat - Included in core. Gateway WebChat UI over WebSocket.
- WeChat - Tencent iLink bot via QR login; private chats only (external plugin).
- WhatsApp - Most popular; uses Baileys and requires QR pairing (official plugin).
- Yuanbao - Tencent Yuanbao bot (external plugin).
- Zalo - Zalo Bot API; Vietnam's popular messenger (official plugin).
- Zalo ClawBot - Personal Zalo assistant via QR login; owner-bound (external plugin).
- Zalo Personal - Zalo personal account via QR login (official plugin).
Delivery notes
- Telegram replies that contain markdown image syntax, such as
, are converted into media replies on the final outbound path when possible. - Slack multi-person DMs route as group chats, so group policy, mention behavior, and group-session rules apply to MPIM conversations.
- WhatsApp setup is install-on-demand: onboarding can show the setup flow before the plugin package is installed, and the Gateway loads the external ClawHub/npm plugin only when the channel is actually active.
- Channels that accept bot-authored inbound messages can use shared bot loop protection to prevent bot pairs from replying to each other indefinitely.
- Supported always-on rooms can use ambient room events
so unmentioned room chatter becomes quiet context unless the agent sends with
the
messagetool.
Notes
- Channels can run simultaneously; configure multiple and OpenClaw will route per chat.
- Fastest setup is usually Telegram (simple bot token, no plugin install). WhatsApp requires QR pairing and stores more state on disk.
- Group behavior varies by channel; see Groups.
- DM pairing and allowlists are enforced for safety; see Security.
- Troubleshooting: Channel troubleshooting.
- Model providers are documented separately; see Model Providers.