Telegram Trigger

The Telegram Trigger node starts a workflow each time your Telegram bot receives a message. It passes the text of the message, and any photo, video or audio file in it, to the nodes after it. A bot can, for example, turn every message it receives into an image. The trigger itself is free.

When to use it

• Build a bot that generates an image or a video from every text message.
• Answer messages with a Generate Text - Any LLM node and send the answer back with Telegram Post.
• Receive the photos, videos and audio files that people send to the bot.
• Collect the posts of a group or a channel where your bot is a member, and process each one.

Quick start

Settings

The status at the top of the panel shows the state of the trigger:

What the node passes on

The node has one output, Message. When a run starts, Nodaro passes the message to the connected nodes according to what it contains:

The message also carries its chat ID and message ID. Nodaro downloads any photo, video or audio file to storage before the run starts.

Several triggers on one bot

A Telegram bot sends its messages to exactly one address, so every trigger on the same bot shares one registration. You can point as many workflows at one bot as you want. Each incoming message is checked against the Chat ID Filter and Message Types of every trigger, and each matching trigger starts its own run.

Removing one trigger never stops the others. Deactivating or deleting a trigger removes it on the next save. When no active trigger is left on the bot, Nodaro removes the bot's registration from Telegram.

What a triggered run executes

A trigger that is connected to nodes runs only its branch: the nodes after the trigger, and every node that they need as input. A trigger that is connected to nothing runs the whole workflow. Each Telegram Trigger that you set up in the editor runs its own branch. Two triggers on the same bot with different chat filters therefore start two separate runs for a message that matches both. A manual run from the editor, a run from the API and a run of a published app are never limited to a trigger's branch.

See the run on the canvas

When the workflow is open in the editor, a run that a message starts shows on the canvas, the same way as a run that you start yourself.

• The Telegram Trigger node reads Working on a message… while the run goes on.
• The nodes that the run reaches show their progress, and their results stay on them when the run ends. The message itself stays in Executions.
• The editor looks for new message runs about every 10 seconds.
• The run bar shows the run, and its stop menu works as for any run. See Stop a run.

When you open the workflow later, the nodes show the newest message run that ended, unless you ran something in the editor after it. A run that was stopped or discarded is not shown, and neither is a result that you cleared after the run.

Only message runs show on the canvas. Runs that a schedule, a webhook or the API starts are only in Executions.

Credits

The Telegram Trigger is free. Each run pays for the nodes it runs.

Troubleshooting

• The save warns that the trigger could not be registered. Telegram refused the registration, and the warning says why. One usual cause is a bot token that was revoked after you connected the bot. Another is a self-hosted install whose PUBLIC_URL is not an HTTPS address that Telegram can reach. No trigger is created when the registration fails.
• Nothing happens for messages in a group. A bot receives only the group messages addressed to it, unless group privacy mode is turned off for the bot in BotFather.
• The media is missing from the run. Telegram lets bots download files of up to 20 MB. A larger file arrives as a message without media.