Configure Telegram Access in OpenClaw

Connect the Telegram bot token to OpenClaw and approve a first direct message under the default pairing policy. If the bot will serve a group, configure and test group access separately.

Connect the bot and probe the gateway

Create the bot in Telegram via BotFather and keep the issued token in a secret store. Use your deployment's Telegram setup screen if it offers one, or use the documented CLI syntax openclaw channels add --channel telegram --token <bot-token> on the gateway host. Substitute the real token privately and keep it out of shared terminals, shell transcripts, and screenshots.

Run openclaw channels status --probe and inspect the Telegram account that corresponds to your bot. Continue to the chat test once the channel probe succeeds. If status reports a blocked lifecycle and a plugin error, run openclaw doctor, address the plugin error, and restart the gateway before probing again.

Use a permitted test account and a separate intentionally unapproved account. A successful authorized DM alone cannot show that unauthorized messages are withheld.

Channels - OpenClaw

Verify both sides of direct-message pairing

Keep Telegram's default pairing policy for a private bot. Open the bot's direct chat from the intended Telegram account and send a harmless first message. Approve the pending pairing request in your deployment's pairing controls after confirming it belongs to the intended account. Then send a second message to verify that the paired account receives the expected agent reply.

For an illustrative test, suppose Dana is the operator and Lee is an unapproved tester. Ask each to request the sum of 14 and 29 in a separate DM. Dana should receive 43 after approval. Lee should encounter pairing without receiving an agent answer. If both accounts receive answers, inspect the DM policy and prior grants before using the bot for private work.

Keep timestamps for pending and approved snapshots. A sender appearing in both can reflect a state transition and should prompt a fresh test.

Telegram - OpenClaw

Test group mentions against your access rules

For a shared bot, add it to the intended Telegram group, review the OpenClaw group allowlist, and enable mention gating if members should explicitly summon it. Confirm the sender and group rules match the participants you intend to serve. Use a harmless test prompt before letting the group send material the agent would process with its tools.

In the approved group, send one message that mentions the bot and a comparable message without the mention. For a mention-gated policy, expect an agent reply only to the explicit mention. If a paired DM works but the mentioned group message is silent, check the group allowlist and sender rules, then inspect BotFather privacy settings and the bot's group permissions.

Telegram - OpenClaw

Trace silence from the channel to the model

When Telegram stays silent, use openclaw channels status --probe to check the running channel and openclaw channels logs --channel all to inspect events around a single test message. Record the test time, the target chat, and whether the message was a DM or a group mention. A blocked channel points you to the gateway or plugin. A healthy channel with silence limited to one chat points you to that chat's access and visibility settings.

If logs show an authorized message reaching OpenClaw and the bot still fails to answer, test a harmless prompt in the gateway's own chat interface. If that fails too, inspect model access before rotating the Telegram token. If it succeeds, return to the channel logs and check reply delivery for the original test.

Channels - OpenClaw

Sources