Channels Overview

Channels are how you communicate with your agent. Rather than forcing you into a dedicated app, OpenClaw meets you where you already are — your existing messaging apps, team tools, and communication platforms.

Channel Comparison

OpenClaw supports 24 official channels. They're grouped below by category.

Messaging

Workplace

Social & Community

Other

Setup Guides

Step-by-step setup instructions are available for the most popular channels:

Message Routing

The MESSAGING.md file controls how your agent handles incoming messages across all channels. Write it in plain English — your agent reads it as natural language instructions.

Example routing rules:

Route all work-related requests from Slack to my work assistant mode.
For iMessage, use a casual conversational tone.
If someone messages me on Telegram about technical questions, be more formal.
Priority messages that require immediate attention should trigger a response even during quiet hours.

As the guide notes: "Your agent reads MESSAGING.md as natural language instructions, so you can write routing rules conversationally."

Starting Strategy

Don't connect everything at once. The most common mistake is setting up five channels simultaneously, ending up with five unstable channels and no idea which configuration is causing problems.

Recommended starting setup:

1. WebChat — zero setup, perfect for testing
2. BlueBubbles (macOS / iMessage users) or Slack (work-focused) — your primary daily channel
3. Second channel once the first is stable

Get one channel working well. Understand how DM policies and tool permissions interact on it. Then expand.

Security Is Per-Channel

A critical point: security settings are per-channel. An allowlist on iMessage doesn't automatically apply to Telegram. An open DM policy on WebChat doesn't affect Slack.

Review your DM policy and tool permissions separately for each channel you connect. Start restrictive and loosen as needed.

Common Troubleshooting

Non-responsive channel: Check if the gateway is running (openclaw status) and that the channel is enabled in your config.

Message routing errors: Review MESSAGING.md for conflicting rules. The agent processes rules top-to-bottom and stops at the first match.

Disconnections: Some channels (especially WhatsApp) require reconnection after extended periods. Configure auto-reconnect where available.

Latency: If responses are slow, check whether you're using the right model tier for the channel. Consider a faster, cheaper model for simple channel messages.

BlueBubbles (recommended for iMessage)

The recommended way to connect iMessage. BlueBubbles bridges iMessage to OpenClaw via the BlueBubbles macOS server REST API.

{
  "channels": {
    "bluebubbles": {
      "dmPolicy": "allowlist",
      "allowlist": ["your.email@icloud.com", "+1234567890"]
    }
  }
}

openclaw channels setup bluebubbles

You'll need the BlueBubbles server running on a Mac. Follow the permission prompts. Works with iPhone's Messages app and iMessage on Mac. Not compatible with Android SMS.

Running Multiple Channels Simultaneously

You can run all channels at once. Each channel has its own pairing/allowlist. The agent maintains separate conversation contexts per channel but shares SOUL.md, USER.md, and MEMORY.md.

{
  "channels": {
    "telegram": { "..." },
    "slack": { "..." },
    "whatsapp": { "..." }
  }
}

For routing specific automations to specific channels, use the channel field in each automation config. See MESSAGING.md & Routing for advanced routing rules.