Token
Runtime token path is wrong
The token was configured once, but the running service still cannot resolve it.
Privacy mode hides messages
The bot is healthy, but Telegram is not exposing the messages you expected it to see.
OpenClaw Telegram
Telegram setup step by step
Use this page when you want OpenClaw connected to Telegram with a setup that separates DM approval, group behavior, and privacy-mode confusion.
Core ideaA healthy Telegram bot can still look silent in groups because privacy mode or group policy is the real blocker.
Setup order
Use the repeated channel ladder, then add Telegram specifics
- create the bot with BotFather
- store the bot token in a runtime-readable path
- choose DM and group policy separately
- test DMs first
- test group behavior second
- only then widen access intentionally
Common failures
Most Telegram confusion comes from visibility and ID assumptions
Groups
IDs
User and group IDs are mixed up
The wrong identifier type is sitting in the wrong allowlist field.