Telegram bot quickstart
Five steps from BotFather token to a paired OpenClaw assistant on Telegram
Five steps from BotFather token to a paired OpenClaw assistant on Telegram
This is the fast path. For groups, media, grammY details, and advanced options, use the full Telegram channel guide. Config keys drift—confirm exact JSON fields in official docs.
Time: about 10–15 minutes if OpenClaw is already installed.
/newbot, choose a display name and a username ending in bot.Optional: /setprivacy if you plan to add the bot to groups later (see full Telegram guide).
New machine:
npm install -g openclaw@latest
openclaw onboard
Existing install: upgrading guide (latest stable listed on releases).
During onboarding, enable the Telegram channel and paste the token when prompted. Or edit ~/.openclaw/openclaw.json following the configuration and Telegram pages.
Keep dmPolicy on pairing (default)—do not open DMs to the world until you understand security basics.
openclaw gateway start
openclaw doctor
doctor should show Telegram connected. If not, see troubleshooting below or main troubleshooting.
hello).openclaw pairing list telegram
openclaw pairing approve telegram <code>
Full pairing flow: pairing guide. After approval, send another message—the agent should respond using your configured model.
| Symptom | Likely cause | Fix |
|---|---|---|
| Bot never replies | Gateway stopped or wrong token | Restart Gateway; re-copy token from BotFather |
| Pairing code only, no chat | Not approved yet | pairing approve with exact code |
| 401 / unauthorized | Revoked or typo in token | Regenerate token in BotFather, update config, restart |
| Slow replies | Model latency or cold start | Try faster model; check provider status |