The flow studio is the place where the customer dialog is assembled with the mouse, without programming. It opens from the bot’s card and works with the same scenario file that lies on disk: any edit in the studio is saved to the file, and an edit to the file is visible in the studio.
The canvas
The scenario is a canvas where dialog steps (nodes) are connected with arrows. Nodes are dragged with the mouse and linked together; the canvas moves and zooms. On the left is the palette with all step types. On top are the flow tabs: the main flow and the special ones (error, timeout, end). There is keyboard support, undo and redo, and a command palette — a quick search for an action by name.
Two views of one scenario
The same scenario can be viewed both as a canvas and as plain text (the text view). These are not two different copies but two windows into one file: edit on the canvas — the text changes; edit the text — the canvas changes. The node layout on the canvas is saved too. One important caveat: comments and unfamiliar lines you added in the text by hand will be lost on the next save from the studio — the interface warns about it. The workaround is simple: keep such notes separately or make them a separate “Note” node.
The inspector
Select a node — a form with the right fields opens on the right: the message text and buttons, answer validation and retry count, conditions, AI request parameters, the knowledge base, web requests, scripts, handoff to an operator. The bot’s settings and its trigger events are changed here too. For everyday work the text view is not needed — everything is done with forms.
Problem hints
While the scenario is being edited, unfinished links do not interfere with work: you can calmly delete a node and assemble everything anew. Problems are marked with icons right on the nodes, and a list is kept alongside — click a row and the canvas shows the node itself. Saving a knowingly invalid scenario is rejected, so a broken version never reaches live work.
The live preview
The preview panel shows the current dialog the way the client will see it in Telegram: message bubbles, buttons, the “typing” indicator, pictures and files. Variables are substituted with a sample, so the owner sees the finished picture before publishing. You can view a single selected node or a whole trial run.
Templates, versions and AI generation
The template gallery has ready-made drafts: pick a suitable one, name the bot — and it is created from the template and opened in the studio. The version history lets you compare the scenario with an earlier one and go back to it. And if you do not want to start from an empty canvas, describe the bot’s purpose in words and press “Generate” — AI will offer a draft that you can review, compare with the current one, and apply only on your confirmation.
Undo and autosave
Undo and redo work across the whole scenario — feel free to experiment. Edits save themselves about a second and a half after you stop: the studio goes through the same verified path as an explicit save — it creates a version snapshot and lets the bot re-read the file. An invalid scenario stays only on your screen, marked as erroneous, and is never written to disk. If you leave the page with unsaved edits, a question appears: leave or stay. You can force a save with the usual Ctrl+S shortcut.
What those steps actually are — in the Flow Nodes section. How to check what you assembled — in Testing & Debugging, and how to see the dialog without a real Telegram — in the Emulator section.