Discord
SoonBetter for community and cross-language scenarios. First version keeps entry only.
CHANNELS
Bring OpenClaw into the chat tools your team actually uses every day. Twelve channels supported, one Gateway, shared skills and workflows.
OpenClaw connects to 12 messaging platforms through a single Gateway. All channels share the same skills, models, and workflows—you add the surfaces your team actually uses.
| Channel | Access method | Scenario |
|---|---|---|
| Baileys (linked device) | Personal / small-team chat | |
| Telegram | Bot API (official) | Community, channels, cross-language |
| Discord | Bot token | Developer communities, gaming teams |
| Slack | Bolt SDK / OAuth | Remote teams, international collaboration |
| Feishu | Official plugin / self-built app | Chinese team collaboration |
| DingTalk | Self-built app | Chinese enterprise collaboration |
| Signal | Signal CLI | Privacy-focused scenarios |
| iMessage | macOS native / BlueBubbles | Apple ecosystem users |
| Microsoft Teams | Bot Framework | Enterprise workflows |
| Google Chat | Chat API | Google Workspace users |
| Matrix | Matrix SDK | Self-hosted, decentralized communities |
| WebChat | Built-in Web UI | Zero-config quick start |
openclaw channels add
The wizard lists all available channels and guides you through credentials for the one you choose.
If your team uses Feishu, use the official plugin for the smoothest setup:
openclaw skills install @openclaw/feishu
See Feishu setup for detailed configuration.
WebChat needs no extra credentials. After installation, open the dashboard:
http://127.0.0.1:18789/
You can test the full loop immediately without configuring any external channel.
Connect one channel first and confirm the message loop works:
Once that works, add more channels as needed.
Connect OpenClaw to Feishu for team collaboration. Install the plugin, configure permissions, and validate the message loop.
Better for community and cross-language scenarios. First version keeps entry only.
Lightweight message entry, topic to be added later.
First version keeps roadmap slot only, no config details yet.
Important for Chinese team scenarios, but first solidify the Feishu path.
RELATED
FAQ
Pick the one you actually check daily. For team collaboration, Feishu or DingTalk. For community or cross-language work, Discord or Telegram.
Each channel adds config, permissions, and debugging surface. Get one working end-to-end before expanding.
NEXT
If your main scenario is Chinese team collaboration, getting Feishu running first usually saves time.