How to Connect OpenClaw to Messaging Apps

OpenClaw uses channels-pluggable connectors-to talk to WhatsApp, Telegram, Discord, Slack, Signal, iMessage, Microsoft Teams, and 15+ other messaging platforms. One Gateway, one agent, many apps. This hub links to step-by-step setup guides for each platform.

📘 New to OpenClaw? Install OpenClaw first with our Quick Start Guide, then return here to add your first channel.

What Are OpenClaw Channel Adapters?

In OpenClaw’s architecture, channel adapters are the bridge between the OpenClaw Gateway (running on your machine or server) and each messaging app. The Gateway routes messages, keeps sessions, and shares a single memory system across all channels-so your AI agent has one consistent context whether you chat via Telegram, WhatsApp, or Discord.

  • One agent, many platforms: Add several channels to the same OpenClaw instance; the same agent and skills are available everywhere.
  • Unified memory: Conversations and context persist across channels, so the agent can reference earlier chats no matter where they happened.
  • Platform-specific credentials: Each channel needs its own tokens or API keys (e.g. Telegram BotFather token, Discord bot token). See each guide below for details.

Supported Messaging Platforms

Choose a platform to open its setup guide. We recommend Telegram for the fastest path to your first working bot.

  • Telegram - BotFather bot + token. Easiest first channel; great for testing. Recommended for beginners.
  • WhatsApp - Connect via WhatsApp Business API or compatible bridge. High user reach.
  • Discord - Create a Discord application and bot; ideal for devs and communities.
  • Slack - Slack app and OAuth; fit for team and workplace automation.
  • Signal - Privacy-focused messaging; setup via Signal bridge or compatible adapter.
  • iMessage - Apple iMessage integration (macOS); for personal or family use.
  • Microsoft Teams - Teams bot registration; suited for enterprise and M365 environments.
  • Multi-channel management - Run and manage multiple channels at once with unified memory and config.

Which Channel Should I Set Up First?

For most users, Telegram is the best first channel: you get a bot token from BotFather in under a minute, paste it into OpenClaw’s config or Web UI, and start chatting. After that, add WhatsApp or Discord depending on where your contacts or community are. For business and teams, Slack and Microsoft Teams are the natural next step. See multi-channel management for running several platforms at the same time.

Prerequisites

  • OpenClaw installed and running - Follow the Quick Start or a platform guide (macOS, Windows, Linux, Docker).
  • Gateway and Web UI - Ensure the Gateway is started and, if you use it, the Web Control UI is available (e.g. http://127.0.0.1:18789/).
  • Account and credentials for the app - Each channel needs its own token or API keys (Telegram bot token, Discord bot token, Slack app credentials, etc.). The individual guides below explain how to obtain them.

General Setup Flow

  1. Obtain the required token or credentials for the messaging platform (see the specific channel guide).
  2. Add the channel in OpenClaw: edit your config file (openclaw config edit) or use the Web UI to add a channel of the correct type and paste the credentials.
  3. Restart or reload the Gateway if needed, then send a test message from the messaging app to confirm the agent responds.
  4. Harden security: keep the Gateway bound to localhost, use a VPN or tunnel for remote access, and follow our security best practices.

Detailed steps, screenshots, and platform-specific gotchas are in each guide: Telegram, WhatsApp, Discord, Slack, Signal, iMessage, Teams, and multi-channel.

Common Channel Issues

Issue What to check
Connection failed / bot not responding Correct token and bot permissions; firewall and network; Gateway logs.
Authentication or token error Verify API keys and tokens in config; no extra spaces; correct env vars if used.
Messages out of order or duplicates Session and routing config; see channel troubleshooting.

For more fixes, see the Troubleshooting hub and the channel errors section.

Security and Best Practices

  • Store tokens and API keys in environment variables or a secrets manager-avoid hardcoding in config files committed to git.
  • Follow our security best practices and credential management guide.
  • Keep the Gateway bound to localhost; use Tailscale, SSH tunneling, or a VPN for secure remote access.
  • Review the security checklist before exposing any channel to untrusted users.

Next Steps

Related Resources