Triggers and events

Choose the event¶

1. Message starts the branch for text and commands.
2. Button handles callback clicks.
3. Reaction provides a reaction change and a message reference.
4. Poll answer and poll results are separate events.
5. Member, bot status and join request report chat changes.

The author and message fields depend on the event. Open the icon beside an output for its exact structure. Data from another output does not appear automatically.

Schedules¶

Choose Schedule in the add menu to run without an incoming message. Set the time and time zone. Specify the message recipient explicitly or check the bot's configured target chat.

Connecting blocks →

Messenger events¶

Starts the flow when the bot receives an event: a message, a button click, a reaction or another update.

1. Enable the outputs you need and connect each to the first step of its branch. Check commands such as /start in a separate condition.
2. Each output supplies different data. Use the icon beside its name to see its fields. For runs without a message, use a schedule and specify the destination chat explicitly.

Schedule¶

Starts a new flow run at a scheduled time without an incoming message.

1. Choose the frequency, time and time zone. Connect the output to the first action.
2. Set the destination chat explicitly or check the bot's configured target chat. Do not use incoming message fields: there is no incoming message in this run.

Webhook¶

Starts a flow from an external system's request.

1. Copy Webhook URL from the block settings and save the flow. Configure the external service to send a POST request to that address; opening the link only checks availability.
2. The URL contains a secret token: do not publish it. Request JSON is available as ${webhook.json}. There is no incoming Telegram message; set the response recipient explicitly.