Connect one channel first, usually the one that matches your real workflow. WhatsApp and Telegram are common first choices because they surface auth and gateway issues quickly.
Channel Setup
Connect OpenClaw to every messaging platform
Each platform has its own auth flow, rate limits, and failure modes. This guide covers what the official docs leave out.
WWhatsApp
Authentication
QR code scan via Baileys (no API key needed)
Rate Limit
~200 messages/day before soft throttle
Pro tip
Scan the QR within 60 seconds. Keep a stable connection during initial sync.
Known Issues
- QR scan gets stuck at 'logging in' — delete auth_info_multi and retry
- Session drops after 24hr inactivity on some carriers
- Multi-device mode required (legacy mode not supported)
T
Telegram
Authentication
Bot token from @BotFather
Rate Limit
30 messages/second per bot
Pro tip
Always disable Privacy Mode for group functionality. Use /setprivacy in BotFather.
Known Issues
- Bot appears online but ignores messages — disable Privacy Mode in BotFather
- Group messages not received — add bot as admin or disable privacy mode
- Webhook conflicts if multiple services use the same bot token
D
Discord
Authentication
Bot token from Discord Developer Portal
Rate Limit
50 requests/second per bot
Pro tip
Message Content Intent is off by default. Enable it in Bot settings or DMs will not work.
Known Issues
- Bot does not receive messages — enable Message Content Intent in Developer Portal
- Slash commands not registering — takes up to 1 hour to propagate globally
- Rate limiting on high-traffic servers
S
Slack
Authentication
Bot token from Slack App settings (OAuth)
Rate Limit
1 message/second per channel (Tier 1 API)
Pro tip
Socket Mode is easier for development. Switch to Events API for production stability.
Known Issues
- DM replies do not deliver — check bot permissions include chat:write
- Socket mode disconnects on VPS — use Events API with HTTPS webhook instead
- App not appearing in workspace — needs admin approval in Enterprise Grid
S
Signal
Authentication
Signal CLI with linked device
Rate Limit
No official limit (be reasonable)
Pro tip
Use a dedicated number. Signal CLI is community-maintained and can lag behind protocol changes.
Known Issues
- Signal CLI requires a dedicated phone number
- Group V2 messages may not be received without proper registration
- Signal updates can break the CLI adapter
C
Custom Webhook
Authentication
HTTP endpoint (URL + optional secret header)
Rate Limit
Depends on your server capacity
Pro tip
Use the webhook adapter to connect any platform that supports outgoing webhooks.
Known Issues
- Webhook validation failures — ensure your endpoint returns 200 within 3 seconds
- Payload format must match OpenClaw's expected schema
- No built-in retry mechanism — implement idempotency on your end
Sources referenced on this page
These references anchor the guide in the underlying platform and channel docs rather than treating messaging setup as trial-and-error.
OpenClaw channels FAQ
These answers are written for high-intent setup and troubleshooting queries around WhatsApp, Telegram, Discord, Slack, and webhook connections.
The common failures are privacy settings, expired QR or webhook state, missing platform permissions, and gateway sessions that were never fully stable in the first place.
No. Get one working end to end, then layer in the next platform. Multi-channel setups are much easier to debug after the first known-good channel path exists.
Channel not connecting?
WhatsApp and Telegram issues are the #1 reason clients hire Milan.