Clawdguy
Telegram setup

Get your Telegram Bot Token in 5 minutes

If you are connecting Telegram to Clawdguy, the only thing you need first is a valid bot token from @BotFather. This guide shows the fastest path for both new and existing bots, plus how to recover safely if a token is exposed.

Step 1: Create a new Telegram bot with BotFather

Open Telegram, search for `@BotFather` (verified), and start the chat.

Send `/newbot`, then follow the prompts for bot name and username. The username must end with `bot`.

Typical BotFather flow

/newbot
My Support Bot
my_support_helper_bot

Step 2: Get the token for an existing bot

If your bot already exists, you do not need to create a new one.

In @BotFather, send `/mybots`, select the bot, then choose `API Token` to reveal and copy the current token.

Existing bot path

/mybots
Select your bot
API Token

Step 3: Confirm token format and bot ID

Most valid tokens follow this structure: `123456789:AA...` with a colon in the middle.

Many tools refer to the numeric part before the colon as the "bot ID". If a platform asks for bot ID, it is usually that first numeric segment.

Use the full token in Clawdguy

Clawdguy's Telegram setup expects the complete bot token, not just the bot ID.

Step 4: Add the token in Clawdguy

Open your deployment in Clawdguy and go to the Telegram channel settings.

Paste the full token into the `Telegram bot token` field and save. If configuration is applied successfully, the integration is ready to receive messages.

Troubleshooting

  • Token rejected: make sure there are no extra spaces before or after the token
  • Wrong bot connected: regenerate and re-copy from the correct bot under `/mybots`
  • Integration suddenly stopped working: rotate the token with `/revoke` and update Clawdguy
  • Cannot find BotFather menu actions: type `/mybots` manually in chat

Security checklist (do this every time)

  • Treat bot token like a password
  • Do not commit token to Git or share it in screenshots
  • Store token in secure config/secrets storage
  • Rotate token immediately if exposed (`/revoke` in BotFather)