How to Connect OpenClaw with Telegram from the CLI

Add the Telegram bot token from the shell, probe the channel, and use logs to read sender IDs before you build allowlists.

1 min readPublished Mar 31, 2026Updated Mar 31, 2026
MilanLast updated Mar 31, 2026Article metadata, reading time, and JSON-LD are generated directly from the Sanity post record.

If you want a terminal-first Telegram setup, keep the whole flow in the CLI: add the bot, probe the channel, inspect logs for IDs, then decide whether you want pairing or an explicit allowlist.

Quick answer

Use openclaw channels add --channel telegram --token ..., then verify with openclaw channels status --probe and openclaw logs --follow.

Command line steps

1. Add the Telegram bot token

This is the cleanest CLI-only way to attach Telegram.

BASH
$openclaw channels add --channel telegram --token "$TELEGRAM_BOT_TOKEN"

2. Probe the channel and follow the logs

Logs are the fastest way to confirm that Telegram traffic is reaching the gateway.

BASH
$openclaw channels status --probe openclaw logs --follow

3. Read your Telegram user ID before you build allowlists

Use the live logs or the Bot API to avoid guessing.

BASH
$curl "https://api.telegram.org/bot$TELEGRAM_BOT_TOKEN/getUpdates"

What to check if it still fails

  • If you prefer not to rely on pairing, move to allowFrom once you know your numeric Telegram ID.
  • If the bot sees DMs but not groups, revisit privacy mode or admin permissions in Telegram itself.
  • If the probe passes but replies still fail, the problem is probably the model layer, not Telegram.

Continue Reading

Related OpenClaw guides