Messaging and email

Telegram Bot

Connect a Telegram bot token from BotFather to start workflows from bot conversations and route operator messages into durable workflow runs.

01 / Workflows

What you can automate.

The Telegram Bot connection is registered for channel-triggered conversations. It stores a Bot API token from BotFather so Runtara can receive and route Telegram-based workflow interactions.

  1. Start workflows from Telegram bot conversations.
  2. Route operator messages into a durable workflow run.
  3. Keep the bot token managed as a reusable platform connection.

02 / Capabilities

What it covers.

The full reference, with connection types, is in the Telegram Bot docs.

Capabilities

  • Bot token authentication
  • Conversational channel triggers
  • Workflow event routing

Data handled

  • Chat messages
  • Trigger metadata
  • Conversation context

03 / Availability

In every edition.

Telegram Bot is a standard integration, included in Cloud, Enterprise and the open-source engine. Compare plans

  • Open-source engineAGPL-3.0, run and operate it yourself.Included
  • CloudWe host and manage your instance.Included
  • EnterpriseYour cloud or on-premises, supported by our team.Included

04 / Questions

Common questions.

Is Telegram Bot included in my plan?

Yes. Telegram Bot is a standard integration, included in Cloud, Enterprise and the open-source engine.

How is it set up?

A connection stores the Telegram Bot credentials once for your instance. Workflow steps that use it declare that connection, and the runtime denies anything else.

Can a person approve before anything is written?

Yes. A workflow holds an exception for approval and continues only after the person decides. The run keeps the source, the decision, who made it, and the response together.

More in Messaging and email

Put Telegram Bot to work.

Start with a paid pilot of one real process. Our team builds and runs it, live in two weeks once access is in place.

Discuss your process

All product names, logos and brands are the property of their respective owners and are used here in good faith, only to identify the systems Runtara connects to. Their use does not imply any affiliation with, or endorsement or sponsorship by, those owners.