Least-privilege setup
- 1
Store the token
Prefer a secret-backed value or `TELEGRAM_BOT_TOKEN` for the default account; never commit it.
- 2
Set access policy
Use `dmPolicy: "pairing"` or an explicit numeric allowlist. Keep group policy allowlisted and require mentions where appropriate.
- 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
Probe the channel
Confirm the bot identity, network path, and configured group assumptions.
openclaw channels status --probe
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.