Integrations / Telegram
Telegram (OpenClaw)
Alongside the web dashboard, CloudyBot supports Telegram through the OpenClaw gateway and on-disk openclaw.json channel configuration—not the Twilio WhatsApp webhook stack.
What this covers
- Config:
channels.telegramand related OpenClaw settings viaopenclaw-channels.js(path fromOPENCLAW_CONFIG_PATHor repo config discovery). - API / UI:
openclaw-channels-routes.jsmounts/api/openclaw/channels(and related) for pairing, models, and cron wiring next to OpenClaw. - Runtime: Gateway process and tokens per
.env.example(e.g.OPENCLAW_GATEWAY_URL,OPENCLAW_GATEWAY_TOKEN).
FAQ
Is Telegram the same integration as WhatsApp?
No. WhatsApp uses Twilio webhooks under /webhooks/whatsapp. Telegram is configured through the OpenClaw gateway and the channels.telegram block in openclaw.json, with dashboard/API surfaces under /api/openclaw/channels and related routes.
Where is configuration stored?
The channels feature reads and writes the channels.telegram section via openclaw-channels.js using OPENCLAW_CONFIG_PATH or discovered openclaw config directories as documented in the channels README.
What should I configure in the environment?
Operators set OpenClaw-related variables such as OPENCLAW_CONFIG_PATH, OPENCLAW_GATEWAY_URL, and OPENCLAW_GATEWAY_TOKEN as listed in api/.env.example and the channels README—exact values depend on your deployment topology.
Where do I manage Telegram in the product?
Use the dashboard and API routes mounted for OpenClaw channels (pairing, models, cron wiring next to OpenClaw). Details vary by release; see openclaw-channels-routes.js and the channels feature README in the repository.
Open the dashboard to configure channels when your deployment exposes them.
Open dashboard