Messaging Platform Integrations

OpenClaw supports over 50 messaging platforms through its channel system. This reference covers the major options, their trade-offs, and when to use each one.

Platform Comparison#

Tier 1: Easy Setup (< 10 minutes)#

| Platform | API Type | Key Feature | Best For | |----------|----------|------------|----------| | Telegram | Bot API (grammY) | Stable, formal bot support | Developers, beginners | | Discord | Bot API | Slash commands, embeds, threads | Communities, dev teams | | WebChat | Built-in | No third-party dependency | Quick testing | | Terminal | Built-in | Direct CLI interaction | Development, debugging |

Tier 2: Medium Setup (10-30 minutes)#

| Platform | API Type | Key Feature | Best For | |----------|----------|------------|----------| | WhatsApp | QR code pairing | Most popular messaging app globally | Personal use, mobile-first | | Slack | OAuth + Events API | Workspace integration, threads | Teams, workplaces | | Signal | Bridge | End-to-end encryption | Privacy-focused users | | Google Chat | Webhook | G Workspace integration | Google ecosystem users | | Microsoft Teams | Bot Framework | Enterprise integration | Microsoft ecosystem |

Tier 3: Advanced Setup (30+ minutes)#

| Platform | API Type | Key Feature | Best For | |----------|----------|------------|----------| | iMessage | BlueBubbles bridge | Apple ecosystem native | Mac users only | | Matrix | Protocol bridge | Federated, self-hosted | Privacy, interoperability | | LINE | Webhook | Popular in Japan, Taiwan, Thailand | Asian market users | | Mattermost | REST API | Self-hosted Slack alternative | Self-hosted teams |

Additional Supported Platforms#

OpenClaw also supports: IRC, Feishu (Lark), Nostr, Synology Chat, Tlon, Twitch, Zalo, Nextcloud Talk, and more through community skills.

Multi-Channel Architecture#

OpenClaw does not just support multiple platforms -- it unifies them. One Gateway process handles all channels, sharing the same session store and memory.

What this means in practice:

• Start a conversation on WhatsApp, continue on Telegram -- context is preserved
• Get notifications on Discord, respond via Slack -- same thread
• All channels share the same agent personality, memory, and skills

{
  "channels": {
    "telegram": {
      "enabled": true,
      "bot_token": "$TELEGRAM_BOT_TOKEN"
    },
    "discord": {
      "enabled": true,
      "bot_token": "$DISCORD_BOT_TOKEN",
      "guild_id": "$DISCORD_GUILD_ID"
    },
    "whatsapp": {
      "enabled": true
    }
  }
}

Cross-Platform Workflow Example#

A common pattern: monitor multiple channels and route intelligently.

1. A WhatsApp message arrives from a client
2. OpenClaw researches the question via web browser skill
3. Agent sends the answer back on WhatsApp
4. Simultaneously logs the interaction in Slack for your team
5. Updates your CRM via API skill

Platform-Specific Notes#

Telegram#

• Uses the grammY TypeScript framework under the hood
• Create bots via @BotFather -- no approval process needed
• Supports inline keyboards, reply markup, and file sharing
• Best documentation and community support of any channel

WhatsApp#

• Requires a dedicated phone number (never use your personal number)
• QR code pairing links your WhatsApp account to OpenClaw
• Third-party package dependency -- keep updated for security
• WhatsApp is the most-installed messaging skill on ClawHub (5,000+ installs)

Discord#

• Rich formatting: embeds, reactions, threads, slash commands
• Server-level permissions give you granular access control
• Great for community-facing bots with multiple users

Slack#

• OAuth flow required -- more complex initial setup
• 3-second response limit for interactive messages (OpenClaw handles this with acknowledgment + follow-up)
• Best for workplace teams already in the Slack ecosystem
• Requires a public domain for inbound webhooks

Security Considerations#

• Never expose the Gateway directly to the public internet
• Use dmPolicy: "pairing" to require identity confirmation
• On WhatsApp and Telegram, a bot that accepts messages from anyone is a liability
• Platforms requiring public domains (Slack, LINE, Google Chat) need extra care with webhook security
• Always use HTTPS for webhook endpoints

Voice Integration#

OpenClaw supports voice on select platforms:

• macOS/iOS: Wake word detection with system TTS
• Android: Continuous voice mode with ElevenLabs or system TTS fallback
• Voice features are experimental and platform-dependent

Recommendations#

| Scenario | Recommended Platform | |----------|---------------------| | Just getting started | Telegram | | Solo developer | Telegram + Terminal | | Small team | Discord or Slack | | Enterprise team | Slack or Microsoft Teams | | Personal assistant | WhatsApp + Telegram | | Privacy-critical | Signal or Matrix | | Multi-platform | Telegram (primary) + WhatsApp (mobile) + Slack (work) |

Next Steps#

• Messaging Quickstart -- Set up your first platform
• LLM Providers -- Configure your AI model
• Security Guide -- Secure your channels