Chatbot
A flow made of builder blocks: messages, buttons, phone request, payments, AI agent. It creates lists for the bot and fills them with samples.
The AI understands from your request what to build and connects the right tools. One thing or several at once — in one chat.
A flow made of builder blocks: messages, buttons, phone request, payments, AI agent. It creates lists for the bot and fills them with samples.
Screens, windows and transitions between them, a catalog with ordering, booking, forms. Before saying “done”, it walks through the app as a customer would.
Pages made of blocks: texts, images by link, messenger buttons, a lead form, an SEO title. When editing, it keeps your own styling.
Buttons to messengers and pages, a banner, colors, domains — and ready code for your site. It can also turn on a chat with your bot right in the widget.
A branch, services with price and duration, staff and their schedules — by weekday or in shifts. At the end it checks that booking actually works.
Sections and lessons with full text, YouTube videos, quizzes, access packages. Packages are created off sale — you turn sales on yourself.
Saves what you ask: delivery terms, a price list from an email, a good answer. It deletes a document only after your confirmation.
The AI connects building itself, reads the builder blocks, proposes a flow and waits for your “Apply”. The canvas opens to the right of the chat — it is the real builder, not a picture, so you can edit it by hand too.
Four steps from an empty chat to a finished result.
The project’s “AI chat” section. For bots there is also the “AI help” button in the bot builder — the chat opens already on your flow. Nothing to turn on.
In plain words: what to build and how it should work. The AI understands which builder is needed and connects it itself — a chip appears by the input.
The AI shows what it is about to do: create an app, write a flow, add a page. You press “Apply” or “Reject”.
The result appears next to the conversation. Apps, landing pages and courses are published with a button in the chat, the bot is checked with “Test the bot”, and messengers you connect yourself.
Building happens in the AI chat of your dashboard — with dozens of models, files and search. More on the AI chat page
In the “Ask first” mode every change arrives as a card: what exactly the AI wants to do and where — in which bot or app, how many blocks it affects. Nothing runs until you press “Apply”.
Once you trust it, switch the mode in the builder chip by the input or press “Apply and don’t ask again” — the AI will build and edit without stopping. The mode is remembered for each chat separately.
“Set up booking for the salon and build a booking app” — the AI connects both builders at once, and the chip shows “Building: booking and mini app”. First it creates a branch with services and schedules, then builds an app that takes them from the project.
The builders share one mode, and you can turn each off separately. Pairs like “bot and knowledge base” or “bot and school” work the same way.
The AI doesn’t touch the flow your customers are going through: a bot build lands as a separate version in the “AI drafts” folder, and the AI connects the finished version with a “Flow” block — you can go back by pointing the block to the old flow.
Mini apps, landing pages and course lessons are edited as drafts and released only through the “Publish” card — even automatic mode doesn’t skip it. A widget and booking setup change at once, so keep “Ask first” for them.
“Ask for the name after the phone”, “make the buttons green”, “Anna is off on Wednesday” — the AI changes only what’s involved, and the rest stays as it was.
In a bot flow and in an app, changed blocks are highlighted on the canvas, and a card in the chat shows the result: how many were added, changed and deleted.
The “AI help” button on the canvas opens a chat already pointed at this flow: building is already connected, the canvas is open. You can ask for a change or a question right away.
The AI reads the flow and walks through it as a customer would: it explains why the bot goes silent after a button, where a branch leads and which block is connected to nothing.
If the bot needs a menu or a catalog, the AI creates a list, adds columns and fills it with sample rows you later replace with your own. It doesn’t make up prices, addresses or phone numbers: it asks or clearly marks the values as samples.
Keys and credentials are never invented either: payment and integration blocks are filled as far as possible, and the AI names them and gives a link straight to each so you can finish them yourself.
It walks through the bot and the app as a customer would, checks that booking works and reviews the course after every change.
An app, landing page or course goes live only with your confirmation — even automatic mode doesn’t skip it.
Prices, addresses and phone numbers come from you. If they’re missing, it asks or marks the values as samples for you to replace.
The AI doesn’t delete bots, apps, landing pages or lessons. A knowledge base document is deleted only after your confirmation.
Banners, covers and pictures come by link from the web. Files attached to the chat are not placed into the project.
A complex flow, app or course is built in stages: the base first, then the details. You see every part right away.
An “AI Agent” block in the flow, on a model connected in the project: the bot will answer open-ended questions.
Bot texts, pages and lessons come in the language you described the task in. The building interface is available in English, German, Russian and Ukrainian.
Claude Sonnet 5 by default. You can pick another strong model; if the chosen one can’t cope, the chat suggests a suitable one and tells you so.
“Reading the flow”, “Building the flow”, “Flow walked” — the progress shows in the chat, without technical details.
If the AI started building by mistake, turn it off in the chip by the input: while it is on, requests use more tokens.
The AI can do exactly what you are allowed to: a team member who can’t edit a flow can’t change it through the chat either.
For those who know what the result should be and don’t want to start from a blank canvas.
No need to learn the builders: describe the task, get a working base of a bot, app or landing page and learn on it.
A new bot branch, an app screen or a landing page is prepared as a draft while customers still see the old version.
Studios and freelancers show a bot, app or landing page at the very first meeting, not a week later.
Inherited a bot from a previous contractor? Ask the AI how it works and where branches break off.
Services and staff schedules, a course with lessons and quizzes — routine data entry is easy to hand over to the AI.
Rewrite the greeting, even out the tone, update prices and buttons — edits that are easier to ask for in words.
Building is open to everyone: the AI is billed per token from your AI balance. The Pro plan is needed for mini apps and when you release what you built to customers.
There is no separate fee for building: you pay for the tokens of the selected model from your AI balance, which is topped up from your account balance in the dashboard. How much it takes depends on the model and the size of the task; every charge is visible in the logs. No Pro plan is needed to build, except mini apps. Later you’ll need it to connect the bot to messengers and to publish a landing page.
Claude Sonnet 5 by default. You can choose another model with tool calling and a large context window; if the chosen one can’t cope, the chat suggests a suitable one and tells you so.
It doesn’t rewrite the bot’s live flow: building happens in a separate version in the “AI drafts” folder, and traffic is switched to it with a “Flow” block. Apps, landing pages and course lessons are edited as drafts and published only on your click. A widget and booking setup change at once — keep the “Ask first” mode for them. There is no “Undo” button.
Not to build — describing the task is enough. But the result is a regular bot, app or landing page of the platform: you can open it in the builder and edit it with the mouse, just like one built by hand. Combining both is the most convenient.
Yes, but in parts: in a bot it places up to 20 blocks per write, in a list up to 50 rows, and finishes a large project in several steps. The more detailed the description, the fewer edits later. We don’t promise a perfect result from the first message — details are usually refined in the conversation.
The result appears next to the conversation: the bot and app canvas in the same builder, the landing page in a phone frame, the widget live. You can walk through the bot yourself: “Open in builder” → “Test the bot”. The AI also walks through the bot and the app before saying everything is ready.
In all you connect: Telegram, Viber and the chat on your website. The AI builds a regular platform flow, so it doesn’t depend on the channel; the exception is blocks that exist in one messenger only, such as Telegram inline mode.
There is nothing to turn on: open the project’s “AI chat” and describe the task — the AI connects the right builder itself. A chip appears by the input, for example “Mini app builder” or “Building: bot and mini app”: there you change the mode, or turn building off if the AI took it up by mistake. From the bot builder — the “AI help” button: the chat opens already on your flow.