#Telegram managed bot

1 messages · Page 1 of 1 (latest)

viral iris
#

Hello
How should I configure openclaw to make my agent that manages my profile in Telegram work?

tacit hemlockBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

worn valeBOT
#

For Telegram, OpenClaw uses a Telegram bot token — there’s no openclaw channels login telegram flow.

First quick check: what does openclaw --version show? Version mismatches cause a lot of weird channel behavior.

Minimal one-owner Telegram setup in ~/.openclaw/openclaw.json:

{
  channels: {
    telegram: {
      enabled: true,
      botToken: "123:abc-from-BotFather",
      dmPolicy: "allowlist",
      allowFrom: ["123456789"], // your numeric Telegram user ID
      groups: {
        "*": { requireMention: true }
#
      }
    }
  }
}

Then restart/start the gateway:

openclaw gateway restart
# or, if running from source:
pnpm openclaw gateway restart

How to get the pieces:

  • Create the bot with Telegram’s @BotFather and copy the token.
#
  • Get your numeric Telegram user ID by DMing your bot, then run openclaw logs --follow and look for from.id.
  • If you prefer pairing instead of allowlist, use dmPolicy: "pairing", DM the bot, then run:
openclaw pairing list telegram
openclaw pairing approve telegram <CODE>

If you mean a separate OpenClaw agent/profile just for Telegram, add an agent + binding:

{
  agents: {
    list: [
      { id: "telegram", name: "Telegram", workspace: "~/.openclaw/workspace-telegram" }
    ]