Configure OpenClaw Channels

Connect Telegram or Slack through XO Setup and restart the OpenClaw Gateway.

This guide documents the OpenClaw-style channel flow shown in XO Setup. It connects an OpenClaw agent to Telegram or Slack so your team can interact with it from the tools they already use.

Using XO Cowork or another agent? Check the Agent Compatibility Guide first. Its channel flow and restart controls may differ from the screenshots below.

The flow is the same for both — open Setup → Channels, add the channel, paste your token(s), save, and restart the OpenClaw Gateway.

What You'll Need

  • An XO project that has finished provisioning
  • For Telegram: a bot token from @BotFather
  • For Slack: a Slack app with a Bot User OAuth Token (xoxb-...) and an App-Level Token (xapp-...). See the Slack app deep-dive for creating the app and finding the tokens.

Connect a Channel

Open Setup → Channels

From your project page, open the Setup tab and select Channels.

Open Setup → Channels

Add Your Channel

Click Add Telegram or Add Slack depending on which channel you want.

Add Slack

Paste Your Token(s)

Paste the credentials for the channel you picked:

  • Telegram: one bot token from @BotFather.
  • Slack: two tokens — a Bot User OAuth Token (xoxb-...) and an App-Level Token (xapp-...).

Paste the bot token

Paste the app token

Save Changes

Click Save changes to apply.

Click Save changes

Restart the OpenClaw Gateway

Channel changes only take effect after the Gateway restarts. Open the Launch tab.

Open the Launch tab

Click OpenClaw Restart.

Click OpenClaw Restart

Verify the Connection

Back on Setup → Channels, the Notifications widget shows how many channels are active. Right after saving (before the Gateway restart) you'll see 0/2:

0/2 channels active — click Refresh

Click Refresh once the Gateway has restarted. The widget flips to 2/2 channels active (or however many you've configured):

2/2 channels active

Send a test message to your agent on the channel you connected to confirm it responds.

If your agent isn't responding on a newly-connected channel, double-check that the Gateway has actually restarted from the Launch tab.