Flow nodes

A node is one step of a chain. Choose it by the action: send, ask, check, save data or wait for an event.

Trigger

Where the chain starts. A trigger sends nothing itself — it catches the event and hands over to the first message. Five kinds: a bot command, a keyword in a message, a button on the site, a system event, and an owner button. Details in "Triggers".

make a chain on /start: a welcome and two buttons

Message

The main node. Up to 4096 characters with formatting and variables, up to ten media items (photo, video, document, voice), buttons underneath.

Worth knowing.

• An album of two or more items is photos and videos only, and an album never has buttons: that's how Telegram works.
• Variables work in the text: {first_name} from Telegram, {name} and {phone} from the user profile, {flow.invite_link} after an invite node, {order.amount} inside payment chains.
• A message can go not to the person but to a group or a group topic — that's how lead cards for the owner are built.

after the welcome, add a message with the menu photo and an "Open catalogue" button

Input

The bot asks a question and waits for the answer. The answer is written into a collection field — usually the user profile: name, phone, e-mail, city.

Validation. The answer can be checked as a number, e-mail, phone or URL; a wrong one gets an error message and the question repeats.

Photos in the answer. Along with text, the node can take attachments — a photo or an album — into a separate field. That's how a support question "with a photo of the problem" is collected and shown to the owner in a group topic.

ask for name and phone, save to the profile, validate the phone

Condition

Checks a statement and takes one of two branches: "yes" or "no". You can check a profile field ("has an e-mail"), a tag, segment membership, a value in data.

The most common use is not asking what's already known: if the e-mail is there, go to payment; if not — input first.

before payment, check whether there's an e-mail and only ask if there isn't

Tag

Sets and removes tags in one step. Tags show on the user card, drive list filtering and build broadcast audiences.

after payment, tag as "client" and remove "lead"

Data record

One node for four actions on a collection: add a record, update, add-or-update, delete. Handles counters ("visits +1") and multiple records per person — each lead its own row.

When the record is missing. Update and delete have a choice: stop silently, or take a separate "not found" branch. For leads, approvals and payments the second is right: the person must hear "no active request", not silence.

save the lead into the "leads" collection with status "new" and a date

Invite link

Creates a personal link into a private channel or group: for one person, with a limit on uses and a lifetime. The link goes into a variable and the next message sends it.

after payment, make a single-use link into the private channel and send it

Wait

Pauses the chain: until the person replies, until a form is submitted on the site, or simply for a while. While the chain waits, you can remind — once, twice, ten times — and the wait doesn't close. Details in "Waits and payment".

if the person hasn't replied in an hour — remind; after a day — close the question

Offer lifecycle

A special node: it has no input and isn't placed "after" anything. It subscribes to offer events — order created, paid, failed, cancelled, refunded — and starts its own branch for each. This is where delivery lives. Details in "Waits and payment".