Documentation / Flows
The flow builder
A flow is a graph: triggers start it, nodes shape what happens, and connections decide the path each subscriber takes. Open any bot in the console and choose Builder to edit its flow on the canvas.
Building on the canvas
Drag nodes from the palette onto the canvas and connect them by dragging from one node's handle to another. Selecting a node opens its settings — every node type has its own form (a keyword trigger asks for the match mode, a schedule trigger for the interval and time, an HTTP node for the URL and method).
The draft you edit is private: subscribers only ever experience the published flow. That separation means you can rework a live bot safely — nothing changes for your audience until you press Publish.
Node families
| Family | Nodes | What it's for |
|---|---|---|
| Triggers | Command (/start…) · Keyword (contains / exact / regex) · Button tap · Inline query · Member joins · Schedule (hourly → annual, custom intervals) · Incoming webhook · Order paid | Where a flow starts. Every flow needs at least one trigger. |
| Messages | Text · Media (photo / video / document / audio) · Inline keyboard · Reply keyboard · Poll · Location · Edit message · Delete message · Typing indicator | What the bot sends. Buttons carry values that can re-enter flows as Button-tap triggers. |
| Logic | Condition · Switch (many-way branch) · A/B split · Delay · Gate · Jump (to another node) · Set variable · End | Branching and pacing. A/B splits divide the audience into labelled groups so later flows can target each arm. |
| Data | HTTP request · Question (collect an answer) · RSS feed · Set attribute · Notify webhook | Talk to the outside world: fetch APIs, store subscriber attributes, push events out. |
| Growth | Deep link · Drip campaign · Segment membership · Live handoff | Acquisition and nurturing. Drip sends a timed sequence; segments feed broadcasts. |
| Shop | Catalog · Product · Cart · Checkout · Orders | Sell physical or digital goods directly in the chat, with an order history per subscriber. |
| AI | AI reply | Generate a reply from the conversation context. Available on products marked AI-enabled. |
| Booking | Confirm booking · Cancel booking · List bookings | Appointment-style flows: reserve slots and manage them from the chat. |
| Media | QR code | Generate QR codes inline, e.g. tickets and payment references. |
Which nodes your line unlocks
Locked nodes appear in the palette with a badge and a one-click explanation of what's needed. If you attempt to use a locked node type through the API you get a clear error, never a silent no-op.
| Capability | Availability |
|---|---|
| Core nodes (triggers, messages, basic logic, data) | All lines |
| Advanced nodes — A/B split, Switch, HTTP request, Drip, Segment, Incoming webhook, Schedule, Inline query, Poll | Professional line and above |
| Shop nodes — catalog, product, cart, checkout, orders | Professional line and above |
| Live handoff to a human agent | Enterprise line |
| AI reply | Products marked AI-enabled (Core and above on Startup) |
Preview, logs, publish, rollback
Preview. The Preview panel walks the flow as a subscriber would — send the trigger input and watch which path is taken. It exercises the same graph the runtime uses, so what you preview is what runs.
Logs. The bot's Logs page shows real conversations and delivery results as they happen — useful when a published flow doesn't behave the way the preview suggested.
Publish and versions. Publishing snapshots the draft as a new numbered version and puts it live. The Versions page lists every published version with who published it and when, and one click rolls the bot back to any earlier version — a bad release is never more than a click from undone.
New here? The quickstart walks through a first bot end to end in about ten minutes.