For AI agents: the complete documentation index is available at https://docs.clickmax.io/en/llms.txt, the full documentation bundle is available at https://docs.clickmax.io/en/llms-full.txt, and this page is available as Markdown at https://docs.clickmax.io/en/features/messaging/connect-telegram.md.
  • English

      • Connect Telegram

      Create a bot with @BotFather, copy the token and paste it into the Connect Telegram wizard under Settings → Account Center → Telegram. Clickmax validates the token and connects the bot immediately, opening it up for the LiveChat and for automations.

      Role: any workspace member with access to Settings can connect a bot.

      Before you start

      • A Telegram account to talk to @BotFather.
      • A bot already created with /newbot in @BotFather, and the access token it gives you (get a fresh one with /token).

      Steps

      1. In Telegram, open @BotFather, send /newbot and follow the instructions until it hands you the bot token.
      2. In Clickmax, open Settings and, under Account Center in the sidebar, click Telegram.
      3. Start the Connect Telegram wizard. On the prerequisites step, review the list and start.
      4. On the token step, paste the token into the bot token field and connect. Clickmax validates the token and provisions the bot immediately — there is no external authorisation step.
      5. Once connected, the bot is ready. Go to the LiveChat to reply, or to the flows builder to create automations.

      If the bot is already connected to another Clickmax account, or delivering messages to another platform (ManyChat, Take Blip or similar), the wizard asks you to confirm before moving delivery here — a Telegram bot only delivers to one place at a time.

      If it didn't work

      • The token is rejected as invalid — generate a new one with /token in @BotFather and paste it again.
      • The bot is already connected on another active connection, or is in use by another platform — disconnect it there, or confirm the move in the wizard.
      • Another connection is being provisioned right now — wait a few seconds and try connecting again.