#OpenClaw Message Channels

OpenClaw's core interaction model is connecting the agent to the chat apps you already use — command it from WhatsApp / Telegram like texting an assistant.

#Channel Adapters

The gateway's first subsystem is the channel adapters: they normalize the varied messages from each platform into a unified format for the session manager and agent loop, then send replies back to the right platform.

[WhatsApp] ──┐
[Telegram] ──┼─→ channel adapters (normalize) → session manager → agent loop → reply → platforms
[Slack]    ──┘

Each platform is driven by a corresponding library, e.g. Baileys for WhatsApp and grammY for Telegram.

#Supported Platforms

Exact platforms and setup defer to your current version.

#Configuring Channels

Channels can be set up during openclaw onboard and managed in the Dashboard. Each platform needs its own credentials (e.g., create a Telegram bot via @BotFather for a token; WhatsApp logs in via QR code).

Keep credentials in environment variables or a separate config, not in shared files:

TELEGRAM_BOT_TOKEN=123456:ABC-...
SLACK_BOT_TOKEN=xoxb-...

Once configured, message your bot to start chatting.

#Sessions & Identity Resolution

The Session Manager resolves "who is talking and which conversation this belongs to":

• Each agent / workspace / sender gets an isolated session
• Group chats have their own session
• Direct messages (DMs) collapse into a main session

This keeps "one OpenClaw serving different people/groups" from mixing contexts. See Multi-Agent.

#Access Control: Don't Let Strangers Command Your Agent

Connecting an agent that can run shell, browser, and email to chat platforms makes access control a baseline:

• Restrict an allowlist of users/groups that may interact
• Route high-risk actions through tool-policy approval gates
• Do not expose the control-plane port :18789 to the public internet

deny by default → allow only trusted users → add approval for risky actions

OpenClaw had a critical cross-site WebSocket hijacking flaw (patched in 2026.1.29) — keep it updated and tighten your network exposure. See Security.

#Media & Rich Interaction

OpenClaw can send and receive images, audio, and documents, so you can:

• Send a screenshot for it to analyze
• Send a voice note to transcribe and act on
• Have it return generated reports/charts as files

#Practical Tips

• For personal use, start with Telegram: easiest setup, great push experience
• For teams use Slack / Discord with allowlists scoped to members
• Enable approval gates so the agent can't be tricked into dangerous actions in chat
• Keep the gateway alive with a daemon/container for 24×7 availability

#Next Steps

• Skills — invoke and draft skills from chat
• Multi-Agent — session isolation for serving many people/groups
• Permissions & Security — lock down the channels