What Flow is
Flow is a visual environment for building workflows: a scenario in which a language model works with your tools and your data. Instead of code there is a graph — node cards and the wires between them.
The finished graph reaches users through one of five channels: a chat page, a widget on your site, a Telegram bot, an HTTP call, or a schedule. The graph itself stays one.
A workflow is a graph
A graph has two mandatory boundaries. The entry node is where the user’s message — or the caller’s object — arrives. The exit node is what comes back as the answer.
- Execute + Data
- LLM
Look at the lower node: llm is not part of the execution chain. It is the model’s configuration, attached over its own wire — so one model can serve several consumers.
There is exactly one entry: the engine hands every entry node the same input value, so a second one would only duplicate the work. There can be several exits, but only on mutually exclusive branches — otherwise one branch’s result overwrites the other’s.
Nodes
A node is a unit of work: a model call, an API request, a branch, a file read. Each has settings and ports — named points that wires attach to. The editor’s palette holds more than 120 nodes across five sections.
Support — first line
Nodes
Drag onto the canvas to add
| Palette section | Example nodes |
|---|---|
| Input / Output | Entry, Exit |
| AI | AI Agent, LLM, Window memory, RAG query |
| Logic & Flow | If / Else, Switch, Wait for all |
| Data | Template, Variable, JavaScript, DB find |
| Integrations | HTTP request, Send email, Telegram |
The palette section names are the same in the Russian and the English interface — the app does not translate them, and the documentation repeats them verbatim.
Wires
An edge between ports carries more than “what follows what”. The wire decides what actually travels along it:
| Wire | What it does |
|---|---|
execute |
Order only: triggers the next node, carries no value. |
data |
Value only: the node reads it, but the edge does not trigger it. |
execute_data |
Trigger and value on one edge — the most common wire in a graph. |
link_llm, link_memory, link_extension |
Attach a model, memory and tools to their consumer. They do not affect execution order. |
The wire type follows from the ports you connected: you cannot attach a model’s output to a
Message port — the editor will not let you.
Delivery channels
Publishing pushes a chosen version of the graph into one or more channels on the Deploy tab:
- Public chat — a hosted chat page behind a public link.
- Widget — an embeddable chat for any site; published separately, on the same token.
- Telegram — answers in Telegram through your bot.
- Webhook — an HTTP call with an API key.
- Schedule — an automatic run on cron.
What people build
- A support bot that answers from your knowledge base and can open a ticket in a CRM.
- A form handler: a webhook takes JSON, the model extracts the fields, the result goes out by email.
- A nightly report on a schedule: a database export, a model summary, a Telegram message.
- An agent with tools that decides for itself when to search the web and when to read a file.