What a flow is

Nodes, events and waits — how the bot works without you

flowsautomation

Updated October 22, 2026

A flow is a chain of project actions. A button, payment or link starts the configured automation. For Telegram conversations, select the active flow for the specific bot.

What it's made of

Trigger — what starts it: a command, a link, a button, a payment, joining a channel.
Nodes — what happens: send a message, set a tag, grant access, write data, wait, check a condition.
Connections — where to go next, including different paths for different answers.

This is how a chain looks on the canvas: nodes joined by arrows, a condition with its two branches.

And this is how it reads step by step:

The person pressed Start

Hi! This is Zerno coffee

What's your name?

Set the "new" tag

Menu and a "Book a table" button

Waits

A flow can wait: for a reply, for a form on the site, or simply for time. "In two days, if they haven't bought, remind them" is one wait and one branch.

Delivering what was bought

There is a separate offer lifecycle node: it catches the payment and runs what the person must receive — an invite link, a message, access.

Lifecycle of the "Subscription" offer

paidLink into the private channel

order createdRemind in 5 minutes

failedTell the owner

A flow is one delivery path. A product purchase can also provide access to a published page or course on the site. Offer readiness blocks sales missing the required delivery path, but you still need to verify the result with a purchase.

Versions

A flow keeps history: snapshots are stored on change and can be rolled back to. Each Telegram bot has one selected active flow. This does not limit the whole project to one flow.