The editor and its nodes

You can see what the answer is made of

Five cards sit on the canvas: the customer's question, the document search, the model's answer, the conversation memory and the delivery. Setting each one up is plain words in a field, not code.

Support on the site and in Telegramdraft · v13BuildTry in chatPublish
Find a node

All nodes · 128

  • Input / Output3
  • AI33
  • Logic & Flow9
  • Data31
  • Integrations52
Customer question
Search the documents▶
Answer to the customer▶▦
Conversation memory▶S
Send to the customer▶

Answer to the customer

AI agent

Prompt

You answer customers of an online shop. Keep it short and stay inside the company documents. If the answer is not in them, say so and offer to take a contact.

Model

GPT-6 Lunaplatform catalogue
2 remarksThe «Answer to the customer» node has its failure branch switched off: if the model does not answer, the customer gets nothing.

The «Answer to the customer» node is open on the right: the Prompt field holds the bot's instruction, written in words. The validation strip below names two remarks, and you see them before publishing.

Build your first scenario

300 quarks a month once your address is confirmed, no card needed. Five drafts live on the free plan, and one of them answers customers.

Once the bot is answering customers

«What if I build it wrong?»

You catch the mistake, not your customer

You can ask the draft anything right in the editor, the way a customer would. The answer arrives with a line beside it: how many fragments were found, how long it took and what it cost.

Separately from that, the editor keeps checking the scenario itself and writes its remarks along the bottom. A remark can be left alone, it does not stop the work, and publishing will tell you if the scenario cannot run.

Try in chatdraft v13

How much is delivery to Kazan?

Delivery to Kazan is 390 ₽ for orders up to 5 kg, and takes 2–3 working days.

3 fragments·1.4 s·0.74 quarksopen the run →

«What if I break the one already answering customers?»

An edit does not go live by itself

Customers are answered by the version you published. You can break the draft as much as you like: until you press Publish, nothing changed for the customer. Every publication gets a number, and the previous version is one button away.

Versions

  • v13draft · your editsjust now
  • v12answering customersyesterday, 18:40
  • v11was published12 August

Next

A second scenario does not disturb the first

The palette holds 128 nodes, and today you need none of them: a first bot is five. Later, from that same palette, people take email, the calendar, tables and a CRM.

Some nodes go anywhere by address and ask for no keys: a request to any service, reading a page, searching the web. The rest need access to the system they call, and that access is set up once as a connection.

Palette · 128 nodes

  • Input / Output3
  • AI33
  • Logic & Flow9
  • Data31
  • Integrations52

Build one scenario and ask it yourself

Five nodes and an uploaded price list is an evening. Trying it in chat shows whether it is good enough before the first customer sees it.

Build your first scenario