documented channels
22
Guides for WhatsApp, Telegram, Discord, Slack, Signal, Teams, Matrix, LINE, WebChat, and more.
OpenClaw channels
OpenClaw channels
Find the right OpenClaw channel for WhatsApp, Telegram, Discord, Slack, Signal, Teams, Google Chat, LINE, Matrix, WebChat, BlueBubbles, and more. Each page covers setup, access policy, transport, verification, and troubleshooting.
Most-used channels first
Setup, pairing, webhooks
Practical setup notes
built-in routes
10
Core, recommended, browser, and legacy channels that usually make the shortlist first.
community plugins
12
Plugin-backed, regional, and self-hosted channels including Feishu, Mattermost, Nextcloud Talk, Twitch, Tlon, and Zalo.
Common channel searches
WhatsApp Web Telegram Bot Discord Bot Slack Socket Mode Microsoft Teams bot Signal CLI Google Chat webhook LINE Messaging API Matrix rooms OpenClaw WebChat
OpenClaw channels
Start with the channels most teams use.
The list starts with the most common deployments, then moves into self-hosted, regional, and experimental channels.
Core Channel WhatsApp
WhatsApp for OpenClaw: QR linking, session ownership, account-safety posture, DM and group policy, and the failure modes operators need to plan for before going live.
Auth model
WhatsApp Web session or provider-backed credentials
Safety stance
Treat account safety as a first-class operating requirement, not a footnote after setup succeeds.
openclaw whatsapp whatsapp web qr pairing session health
Runtime stance
Measured rollout with explicit risk controls
Effort
30–45 min setup
Open dossier
Core Channel
Telegram
Telegram Bot setup for OpenClaw: BotFather token handling, DM versus group policy, privacy mode, verification, streaming behavior, and the failure patterns operators hit first.
Auth model
Bot token + DM pairing or group permissions
Safety stance
Lock pairing scope early and verify privacy mode before exposing the bot to public groups.
openclaw telegram telegram bot api telegram privacy mode telegram group permissions
Runtime stance
Rapid launch with iterative hardening
Effort
20–30 min setup
Open dossier
Core Channel
Discord
Discord Bot setup for OpenClaw: gateway intents, role permissions, DM versus guild behavior, verification drills, and moderation-aware rollout patterns.
Auth model
Bot token + gateway intents + guild roles
Safety stance
Make intents and role scope explicit before the bot ever lands in a shared server.
openclaw discord discord openclaw gateway intents guild roles
Runtime stance
Community deployment with moderation-aware defaults
Effort
25–40 min setup
Open dossier
Core Channel
Slack
Slack Bot setup for OpenClaw: scopes, Socket Mode or Events API behavior, thread policy, workspace rollout, and troubleshooting for silent bots.
Auth model
Slack app scopes + bot token + Socket Mode / Events API
Safety stance
Minimize scopes and verify thread semantics before broad workspace deployment.
openclaw slack slack openclaw oauth scopes socket mode
Runtime stance
Policy-aware internal deployment
Effort
35–50 min setup
Open dossier
Community Plugin
Microsoft Teams
Microsoft Teams support for OpenClaw covers plugin-backed Azure Bot setup, Teams app manifest and RSC permissions, Graph-dependent media behavior, and tenant-scoped routing boundaries.
Auth model
Installed plugin + Bot Framework / Azure app credentials + tenant policy
Safety stance
Treat Azure registration, tenant policy, and Teams app visibility as one combined deployment problem.
openclaw msteams microsoft teams openclaw azure bot teams app manifest
Runtime stance
Enterprise plugin rollout with admin coordination
Effort
45–90 min setup
Open dossier
Core Channel
Signal
Signal for OpenClaw: signal-cli setup, linked-device or dedicated-number decisions, daemon health, DM and group policy, and the recovery posture privacy-focused operators should expect.
Auth model
signal-cli linked device + local service paths + account identity
Safety stance
Treat device linking, number ownership, and state persistence as first-class operational controls.
openclaw signal signal-cli linked device daemon health
Runtime stance
Privacy-first deployment with explicit host dependencies
Effort
35–50 min setup
Open dossier
Community Plugin
LINE
LINE Messaging API setup for OpenClaw: plugin installation, webhook wiring, channel credentials, verification drills, and rollout notes for supported regions.
Auth model
Installed plugin + LINE Messaging API credentials + webhook endpoint
Safety stance
Respect webhook integrity and account boundaries before adding richer templates or menu actions.
openclaw line line openclaw line messaging api webhook verify
Runtime stance
Plugin-backed regional bot deployment
Effort
25–40 min setup
Open dossier
Core Channel
Google Chat
Google Chat setup for OpenClaw covers Chat API apps, webhook delivery, workspace permissions, and a clean verification path for internal rollouts.
Auth model
Google Chat app credentials + HTTP webhook configuration
Safety stance
Align Google Workspace permissions with the smallest audience possible before widening room access.
openclaw google chat google chat api google chat webhook google workspace chat app
Runtime stance
Internal workspace deployment with webhook discipline
Effort
25–35 min setup
Open dossier
Browser Surface
WebChat
WebChat for OpenClaw covers browser access, WebSocket reachability, token bootstrap, pairing, and safe remote exposure for the built-in chat surface.
Auth model
Gateway token + browser pairing + WebSocket session
Safety stance
Because it feels local and simple, operators often underestimate the trust model and remote-access implications.
openclaw webchat webchat openclaw websocket browser pairing
Runtime stance
Fastest browser-native path with trust-state awareness
Effort
10–20 min setup
Open dossier
Community Plugin
Matrix
Matrix support for OpenClaw covers plugin installation, homeserver login, DM and room policy, E2EE device verification, and federated routing boundaries.
Auth model
Installed plugin + Matrix homeserver credentials + room access policy
Safety stance
Document which homeserver, rooms, and federation assumptions define trust for this rollout.
openclaw matrix matrix openclaw matrix homeserver matrix e2ee
Runtime stance
Plugin-backed federated deployment
Effort
25–45 min setup
Open dossier
Community Plugin
Twitch
Twitch chat setup for OpenClaw: plugin install, bot-account credentials, channel join behavior, allowlist versus role gating, mention requirements, token refresh, and live-chat verification.
Auth model
Installed plugin + Twitch chat credentials / IRC-style channel auth
Safety stance
Moderation boundaries and rate expectations matter as much as raw connectivity on a live stream surface.
openclaw twitch twitch openclaw twitch irc bot twitch allowfrom
Runtime stance
Live-chat deployment with moderation discipline
Effort
20–35 min setup
Open dossier
Recommended Integration
BlueBubbles
BlueBubbles for OpenClaw covers macOS server setup, REST connectivity, pairing boundaries, and advanced messaging behaviors for Apple-centric workflows.
Auth model
BlueBubbles server credentials + trusted macOS host
Safety stance
Treat the Mac host and BlueBubbles server as production infrastructure, not a casual desktop toggle.
openclaw bluebubbles bluebubbles openclaw bluebubbles server macOS host
Runtime stance
Recommended Apple-device rollout with host stability first
Effort
30–45 min setup
Open dossier
Community Plugin
Mattermost
Mattermost support for OpenClaw covers plugin installation, bot token and base URL setup, channel chat modes, slash-command callbacks, and self-hosted workspace routing boundaries.
Auth model
Installed plugin + bot token + WebSocket / channel access config
Safety stance
Treat self-hosted chat policy and bot scope as part of the same operational document.
openclaw mattermost mattermost openclaw mattermost bot token mattermost slash commands
Runtime stance
Internal self-hosted collaboration rollout
Effort
20–35 min setup
Open dossier
Community Plugin
Feishu
Feishu integration for OpenClaw focuses on plugin installation, WebSocket bot setup, tenant permissions, verification, and team rollout hygiene.
Auth model
Installed plugin + tenant app credentials + WebSocket bot config
Safety stance
Treat tenant-level permissions and app scopes as part of the rollout plan, not a one-time form fill.
openclaw feishu feishu openclaw plugin install tenant app
Runtime stance
Plugin-backed enterprise deployment
Effort
30–45 min setup
Open dossier
Community Plugin
Nextcloud Talk
Nextcloud Talk for OpenClaw covers plugin setup, server credentials, room access, and a verification path tuned for self-hosted teams.
Auth model
Installed plugin + Nextcloud Talk credentials + room policy
Safety stance
Document which server, rooms, and identity policy define the trust boundary.
openclaw nextcloud talk nextcloud talk openclaw nextcloud talk self-hosted rooms
Runtime stance
Self-hosted collaboration rollout with room discipline
Effort
25–40 min setup
Open dossier
Community Plugin
Synology Chat
Synology Chat setup for OpenClaw: plugin install, outgoing versus incoming webhook roles, DM policy, user-ID allowlists, SSL posture, verification, and multi-account webhook routing.
Auth model
Installed plugin + outgoing / incoming webhooks + Synology Chat room config
Safety stance
Treat the NAS and webhook boundary as one security surface, especially on home or small-business networks.
openclaw synology chat synology webhook synology chat allowlist synology nas bot
Runtime stance
Self-hosted webhook deployment on Synology infrastructure
Effort
25–40 min setup
Open dossier
Core Channel
IRC
IRC for OpenClaw focuses on server connectivity, nick identity, channel versus DM rules, and allowlist-first operation on classic networks.
Auth model
IRC server connection + nick identity + channel access rules
Safety stance
On IRC, allowlists and pairing posture matter more than visual onboarding polish.
openclaw irc irc allowlist irc mention gating irc nickserv
Runtime stance
Text-first operations with strict routing controls
Effort
20–35 min setup
Open dossier
Legacy Integration
iMessage
Legacy iMessage support for OpenClaw via imsg: transition guidance, risk notes, verification expectations, and when to prefer BlueBubbles instead.
Auth model
Local macOS host + imsg CLI / JSON-RPC bridge
Safety stance
Present this lane as a migration or compatibility path, not the default recommendation.
openclaw imessage imessage openclaw imsg cli legacy bridge
Runtime stance
Legacy maintenance and transition planning
Effort
Legacy path
Open dossier
Community Plugin
Zalo
Zalo Bot API support for OpenClaw covers plugin-backed setup, bot credentials, local rollout conventions, and verification tuned for Vietnam-focused deployments.
Auth model
Installed plugin + Zalo Bot API credentials
Safety stance
Regional platform rules and account expectations should be documented alongside the technical setup.
openclaw zalo zalo openclaw zalo bot api regional rollout
Runtime stance
Regional plugin deployment with market-specific guardrails
Effort
25–40 min setup
Open dossier
Community Plugin
Tlon
Tlon/Urbit support for OpenClaw covers plugin-backed setup, identity assumptions, group access, and verification tailored to that ecosystem.
Auth model
Installed plugin + Urbit / Tlon identity and room configuration
Safety stance
Document the identity and room model explicitly because it differs from mainstream bot platforms.
openclaw tlon tlon openclaw urbit identity tlon rooms
Runtime stance
Protocol-specific community deployment
Effort
35–50 min setup
Open dossier
Community Plugin
Nostr
Nostr DM setup for OpenClaw: plugin install, relay strategy, private-key handling, DM policy, profile metadata, verification, and the protocol limits operators should understand before rollout.
Auth model
Installed plugin + key material + relay configuration
Safety stance
Key handling and relay selection are the actual product surface here, not just implementation details.
openclaw nostr nostr dm bot nip-04 nostr relay
Runtime stance
Protocol-native decentralized deployment
Effort
15–30 min setup
Open dossier
Community Plugin
Zalo Personal
Zalo Personal support for OpenClaw covers plugin-backed QR login, personal-account constraints, risk posture, and verification for cautious operators.
Auth model
Installed plugin + QR login + personal account session state
Safety stance
Make the personal-account tradeoffs explicit before anyone treats the lane as a safe default.
openclaw zalouser zalo personal openclaw qr login personal account
Runtime stance
Cautious experimental rollout with policy awareness
Effort
35–50 min setup
Open dossier
How to choose
Choose the channel that fits your rollout.
Step 01
Match the audience
Decide whether the real target is consumer chat, team workspace chat, self-hosted rooms, or the built-in WebChat console.
Step 02
Choose the transport
Pick the right operational model: QR login, bot token, Socket Mode, HTTP webhook, WebSocket, or local bridge.
Step 03
Lock the boundary
Set pairing, allowlists, requireMention, roles, and group policy before the first broad rollout.
Step 04
Prove it under stress
Validate direct replies, shared spaces, restart behavior, listener state, and one realistic failure before launch.
Every page covers
Auth model
Bot tokens, QR sessions, WebSocket credentials, webhook secrets, or local bridge identities.
Every page covers
Access control
Pairing, allowlists, group policy, mention requirements, role checks, and sender boundaries.
Every page covers
Verification path
First DM, group or room test, restart behavior, reconnect health, and known failure drills.