Triggers vs actions

What starts a flow versus what a flow does.

Blocks come in two kinds: triggers (entry points) and actions (steps).

Triggers — where a flow starts

A trigger has no incoming arrow; it’s matched against an incoming Telegram update. If it matches, the flow runs from there. Triggers include:

• Command — /start, /help, with optional deep-link payload.
• Text — a text message by exact / contains / regex / any rule.
• Button pressed — an inline button callback.
• Media received, Mini App data, Group event, Bot blocked/unblocked, and (paid) Payment received.

When several triggers could match, the bot picks the most specific match.

Actions — what the flow does

Every other block is an action: send a message, ask a question, branch on a condition, call an API, set a variable, and so on. Actions run in the order the arrows connect them. Browse them all in the Blocks reference.

Blocks that wait

Most actions run instantly. A few pause the flow until the user responds — most notably Ask and save (waits for an answer) and Forced subscription (waits for the recheck). On the canvas these show a ⏸ marker.