Review-ready recipe · Independent guidance

Set up an OpenClaw Telegram assistant

Create a Telegram bot token with BotFather, store it as a secret or token file, keep DM access on pairing or an explicit numeric allowlist, then start the Gateway and approve the first request. Telegram does not use `openclaw channels login telegram`.

Live retest required · noindexUpdated 2026-08-24Documentation-reproduced checklist · retest required before production credentials
01

Least-privilege setup

  1. 1

    Store the token

    Prefer a secret-backed value or `TELEGRAM_BOT_TOKEN` for the default account; never commit it.

  2. 2

    Set access policy

    Use `dmPolicy: "pairing"` or an explicit numeric allowlist. Keep group policy allowlisted and require mentions where appropriate.

  3. 3

    Start and pair

    Start the Gateway, message the bot, then approve the one-hour pairing code.

    openclaw pairing list telegram
    openclaw pairing approve telegram <CODE>
  4. 4

    Probe the channel

    Confirm the bot identity, network path, and configured group assumptions.

    openclaw channels status --probe
02

Failure and rollback

  • A 401 from `getMe` means Telegram rejected the configured token; replace or regenerate it.
  • Network errors usually mean DNS/HTTPS access to `api.telegram.org` is unavailable.
  • To stop access, disable the channel, restart the Gateway, revoke the BotFather token if exposed, and remove obsolete pairing/allowlist entries.

Common questions

Before you act

Should I paste a bot token into this site?

No. The recipe uses placeholders only; configure the token on your own OpenClaw host.

Primary sources

Verify against the owner.

Content snapshot follows official docs main at the recorded commit; the current package metadata reported 2026.8.1 when verified. Your installed release and live CLI schema remain authoritative.