Skip to the operations

Messaging

Telegram in a decision flow.

4 Telegram operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
Messaging
Type
Integration
Authentication
API key
Test environment
Production host only

Who they are

A messaging app with an open bot API.

Telegram is a consumer messaging service whose Bot API lets a program post into a chat or channel with nothing but a bot token. That makes it a practical alerting channel for a team already using it, with no procurement between the flow and the message.

What a flow can call

4 operations, each one a step you can place on the canvas.

  1. POST/sendMessage

    Send a text message

    Sends text to a chat, group, supergroup, or channel.

  2. POST/editMessageText

    Edit a sent text message

    Replaces text in a message the bot can edit. Supply the target chat_id and message_id from an earlier send; Telegram restricts which business messages can be edited and when.

  3. GET/getMe

    Verify bot token

    Verifies the bot token and returns the bot's basic profile.

  4. GET/getUpdates

    Get pending bot updates

    Retrieves queued updates such as incoming messages and callback queries.

Where it sits in the decision

Messaging calls have a natural place in a flow.

Notifying a person is part of the decision rather than an afterthought to it: the message goes out from the flow, at the point the flow decided it was warranted, carrying the same version and trace as the outcome that triggered it.

Whatever Telegram returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Telegram as a connection authenticating with an API key.
  • 02Telegram has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Send a text message” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Telegram in a flow.

How do I connect Telegram to a decision flow?

Add Telegram as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Telegram in a decision without ever seeing the secret.

Can I test Telegram without touching production?

Telegram exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.

What can a flow call on Telegram?

4 operations, including “Send a text message”, “Edit a sent text message”, “Verify bot token”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Send a text message”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should Telegram be called?

Notifying a person is part of the decision rather than an afterthought to it: the message goes out from the flow, at the point the flow decided it was warranted, carrying the same version and trace as the outcome that triggered it.

Also in Messaging

Ready when you are

Wire Telegram into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs