Developer Platform: MCP server availableDeveloper Platform: MCP server available, App SDK from Q4 2026

[ Communication ]

Telegram Bot integration for your workflows.

Connect Telegram Bot to Collabase once and use 20 actions and 1 trigger in your workflows. No code needed, hosted in Switzerland.

Sign-inAn API key
CategoryCommunication
UpdatedOctober 2026
LicenceOpen source (MIT)
Back to the directory

Telegram Bot in Collabase

Connect Telegram Bot to Collabase once and use 20 actions and 1 trigger in your workflows. No code needed, hosted in Switzerland.

[ About the service ]

Build chatbots for Telegram

How to connect it

  1. Open the integrations in the workspace settings.
  2. Choose Telegram Bot and connect your account.
  3. Add a trigger or an action to the workflow.
  • Begin a conversation with the Botfather.
  • Type in "/newbot"
  • Choose a name for your bot
  • Choose a username for your bot.
  • Copy the token BotFather sends and paste it here.

[ Communication ]

Related integrations

All integrations

Tools that often share a workflow.

Questions about Telegram Bot

What can I automate with Telegram Bot in Collabase?

Telegram Bot brings 20 actions and 1 trigger, for example Send Text Message, Send Media, Send Document, Send Audio and 16 more. You combine them in a workflow without code and mix them with every other integration.

How do I connect Telegram Bot to Collabase?

You open the integrations in the workspace settings, choose Telegram Bot and connect your account once, using an API key. After that all triggers and actions are available in the workflow.

Can Telegram Bot start a workflow?

Yes. Telegram Bot provides 1 trigger, for example New Update. The workflow runs as soon as the event happens.

Does the Telegram Bot integration cost extra?

No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.

Test it against your own content. A proof of concept is ready within days.

We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.