OpenClaw Multi-Channel Setup
OpenClaw supports multiple communication channels. Curate-Me adds unified monitoring, health tracking, and message routing across all channels from a single dashboard.
Supported Channels
| Channel | Protocol | Setup Complexity | Status |
|---|---|---|---|
| Telegram | Bot API | Low (API token) | Supported |
| WhatsApp Business API | Medium (QR code + Business verification) | Supported | |
| Slack | Slack App / Bot Token | Low (OAuth) | Supported |
| Discord | Discord Bot Token | Low (Bot token) | Supported |
| Signal | Signal CLI | Medium (Phone number + PIN) | Preview |
| Microsoft Teams | Bot Framework | High (Azure AD + App registration) | Preview |
| Google Chat | Chat API | Medium (Service account + OAuth) | Preview |
Channel Configuration
Each channel is configured through the dashboard at /runners/{id}/channels or via API.
Telegram Setup
- Create a bot via @BotFather
- Copy the bot token
- Paste into the channel setup wizard
- Test connection
{
"channel": "telegram",
"config": {
"bot_token": "123456:ABC-DEF...",
"allowed_chat_ids": ["-1001234567890"]
}
}Slack Setup
- Create a Slack app at api.slack.com
- Add
chat:write,channels:read,im:read,im:writescopes - Install to your workspace
- Copy the bot token (
xoxb-...)
{
"channel": "slack",
"config": {
"bot_token": "xoxb-...",
"app_token": "xapp-...",
"channels": ["#general", "#ai-agent"]
}
}Discord Setup
- Create a bot at Discord Developer Portal
- Enable Message Content Intent
- Copy the bot token
- Invite bot to your server with appropriate permissions
{
"channel": "discord",
"config": {
"bot_token": "MTIz...",
"guild_ids": ["1234567890"]
}
}WhatsApp Setup
- Set up WhatsApp Business API (via Meta Business Suite)
- Configure webhook URL:
https://api.curate-me.ai/v1/runners/\{id\}/channels/whatsapp/webhook - Add phone number and verify
- Scan QR code from dashboard
Channel Monitoring
The dashboard provides real-time channel health monitoring:
- Connection status — Connected / Disconnected / Error
- Message volume — Messages per hour, per day, per week
- Last message — Timestamp of last received message
- Auto-reconnect — Automatic reconnection on disconnect
- Health alerts — Notification when a channel goes down
Message Routing
Route specific channels to specific skills or templates:
{
"routing_rules": [
{
"channel": "slack",
"channels": ["#support"],
"route_to": "customer-support-template"
},
{
"channel": "telegram",
"route_to": "personal-assistant-template"
}
]
}Cost Tracking Per Channel
The cost dashboard breaks down spend by channel:
| Channel | Messages/Day | Avg Cost/Message | Monthly Cost |
|---|---|---|---|
| Slack | 450 | $0.003 | $40.50 |
| Telegram | 200 | $0.005 | $30.00 |
| Discord | 100 | $0.002 | $6.00 |
| Total | 750 | $0.003 | $76.50 |
Best Practices
- Start with one channel — Get it working before adding more
- Set per-channel cost caps — Prevent any single channel from overwhelming budget
- Monitor connection health — Set up alerts for disconnects
- Use message routing — Send different channels to different templates
- Review audit trail — Check channel activity logs regularly