Create a Telegram Bot with BotFather
Open Telegram's @BotFather and send /newbot to register a bot and obtain its token. Put that token in the intended OpenClaw instance, then verify that your own Telegram account can pair and receive a reply.
Choose which OpenClaw instance owns the bot
Before opening BotFather, decide which OpenClaw instance will use the new bot and which Telegram account will test it. If you run both a trial instance and a live one, give each its own bot. Use a display name that helps operators tell the two apart, and keep the intended bot handle and instance name together in your deployment notes.
In Telegram, open the official @BotFather chat and send /newbot. Follow its prompts for the display name and username. Prepare a username ending in bot and keep a second candidate ready in case the first is taken. This step succeeds when BotFather issues a token and you can identify the bot handle it created.
Record an alias for the registration and the identity shown on the test reply. Never paste the bot token into a shared onboarding log.
From BotFather to 'Hello World'Put the token in one place
Open the Telegram channel setup for the OpenClaw instance you chose and set the bot token there. Copy the complete value directly from BotFather into that configuration. Keep deployment notes useful by recording the bot handle, instance name, and credential location while keeping the token itself in the intended secret store. That gives the next operator enough information to check the handoff without exposing the credential.
Verify the channel, then open the bot by its exact handle in Telegram and send a private message. With OpenClaw's default pairing policy, look for a pairing prompt from the intended bot. Approve the expected sender and send a second message that requests a distinctive reply. A reply to that second message confirms the handoff from BotFather through OpenClaw.
Verify the direct-reply step from the destination account. Seeing the bot identity at registration proves a different part of the path.
Telegram - OpenClawProve ownership with one private test
In this illustrative setup, the destination is an OpenClaw instance named Dispatch Trial, the proposed bot username is dispatch_trial_bot, and only the operator should be enrolled at first. If BotFather accepts the username, record the handle beside Dispatch Trial and put the issued token into that instance's Telegram setup. From the operator's own Telegram account, open that handle and send a DM.
Use pairing for the first test. If you later choose to identify that operator explicitly through channels.telegram.allowFrom, use the numeric ID of the human sender. OpenClaw documents a way to find it by sending a DM, running openclaw logs --follow, and reading from.id. After setting the intended access policy, ask the bot to reply with DISPATCH-TRIAL and verify the response in the same chat.
FAQ: providers, hardware, and hosting - OpenClawRotate an exposed token in place
If the token appears in a shared screenshot or pasted transcript, use BotFather to revoke it and obtain a replacement for the same bot. Update the intended OpenClaw instance with the replacement and repeat the private message test. Search your deployment notes for other locations where someone might have configured the old value, using the bot handle or instance name as the lookup key.
If the token stayed private and the first DM is silent, begin with reversible checks. Confirm the exact handle, compare the saved token with the value BotFather issued without displaying either in a shared window, and verify that the intended instance has Telegram configured. Revocation is appropriate when the credential has escaped your control. A silent first message alone leaves several configuration problems to check.
From BotFather to 'Hello World'