Skip to content

Messaging integration

Telegram integration for AI workflows.

Message drivers, crews and customers from your own Telegram bot, and act on what they send it.

Beta

In short

Fluxo Flow connects to Telegram with an API key or credentials you provide; workflows can send a message, send a photo and send a document and more, and start from new message to the bot. The integration is in beta.

Beta means it works but hasn't been tested against every account setup yet; actions and fields may still change. Found a problem? Tell us.

What you can do

Actions and triggers for Telegram.

Actions

  • Send a message

    Sends a text message from your bot to a user, group or channel.

  • Send a photo

    Sends a photo from a public link (up to 5 MB) with an optional caption.

  • Send a document

    Sends a file (PDF, ZIP… up to 20 MB) from a public link with an optional caption.

  • Get chat info

    Reads a chat's title, type, username and description.

Triggers

  • New message to the bot (instant webhook)

    Starts a run within seconds for each message people send your bot (in private chats, or in groups the bot is in).

How to connect

Connect Telegram in a minute.

Connects with an API key or credentials, tested before they're saved and encrypted at rest.

  1. In Telegram, open @BotFather, send /newbot and follow the prompts.
  2. Copy the bot token BotFather gives you.
  3. In Fluxo Flow, open Settings → Integrations → Telegram and paste the token.
  4. People must start a chat with your bot (or add it to a group) before it can message them.

Permissions & limits

What it can access, and how fast it runs.

Permissions requested

  • Everything: a bot token can do whatever the bot is allowed to in the chats it's in

Limits and timing

  • Instant triggers arrive by webhook within seconds of the event.
  • If Telegram says to slow down (HTTP 429 or 503), requests wait as told and retry a limited number of times.

FAQ

Telegram questions, answered.

Why can't my bot message someone?

Telegram bots can only message people who have started a chat with them, and groups/channels they've been added to (channels need the bot as an admin).

Can two workflows listen to the same bot?

No — Telegram sends a bot's messages to one webhook. Use one bot per trigger, or one workflow that routes messages with a Switch step.

Does the bot see every message in a group?

Only if you turn off privacy mode in @BotFather (/setprivacy). Otherwise it sees commands and replies to it.

Is the Telegram integration finished?

It's in beta: it works, but it hasn't been tested against every account setup yet. Tell us if something doesn't behave as expected.

Can I use Telegram on the Free plan?

You can connect it, build with it and Dry Run on the Free plan. Running workflows live (triggers, schedules, webhooks) needs a paid plan.

Can I call Telegram endpoints the integration doesn't cover?

Yes, if Telegram has an API: save a key in the encrypted credential vault and call it with an HTTP Request step.

Can I test a workflow without touching my real data?

Yes. Dry Run walks through every step with simulated app calls, so nothing is sent until you run it for real or activate its trigger.

All integrations

Connect Telegram to your first workflow.

Build and Dry Run on the Free plan, no credit card. Run live on a paid plan, on your own AI key at cost.

Free to explore · No credit card · 30-day money-back guarantee on paid plans