> For the complete documentation index, see [llms.txt](https://help.novatalks.com.ua/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novatalks.com.ua/en/get-started/a-i-and-bots/flow-bots/flow-bot-editor.md).

# Flow Bot editor

### Flow Editor

The Flow editor opens in full screen. A Start node is automatically added to the canvas – the starting point of the scenario. It cannot be deleted.

<figure><img src="https://2498134934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5yF7NRiGknx3Bqj4OgYA%2Fuploads%2FUuTpMq707VxcGyBq3c82%2Fimage.png?alt=media&amp;token=b8b9fbe4-b921-439f-a612-e0d6142fda82" alt=""><figcaption></figcaption></figure>

1. Collapse / Expand menu – arrow icon at the top left; shows or hides the left system menu.
2. Back – return to the Flow bots list.
3. Flow name.
4. Settings (slider icon) – opens the launch settings panel.
5. Save as Draft – saves the Flow with the Draft status. The button is active (green) only if the Flow is filled in correctly.
6. Launch – saves the Flow with the Active status and returns to the list. After that, the Flow runs when the trigger occurs. The button is active (green) only if the Flow is filled in correctly.
7. Arrange – automatically arranges the nodes on the canvas following the direction of the connections from the Start node.
8. Fit – scales the canvas so that all nodes fit on the screen.
9. Export – downloads the Flow as a .json file.
10. Import – adds to the canvas the nodes from a .json file obtained via Export.
11. \+ (green button at the bottom right) – opens the node selection panel.

{% hint style="info" %}
If the Save as Draft and Launch buttons are inactive, hover over them – a tooltip will remind you what setup still needs to be completed. Required fields that are not filled in are highlighted with a red border.
{% endhint %}

***

### Working with Blocks

Each block consists of a header (name and icon), configuration fields, and connection points: on the left – the input, on the right – the output (or several outputs).

* **Add a block** – click “+” at the bottom right and select a block in the panel. The block will appear on the canvas. To close the panel, click “×”.
* **Connect blocks** – drag a line from the right point (output) of one block to the left point (input) of the next one.
* **Move a block** – drag it with the mouse.
* **Rename a block** – click the block’s header and enter a new name.
* **Delete a block** – hover over the block and click “×” in the top right corner. All of the block’s connections are deleted along with it.

Blocks are divided into two groups: **MESSAGES** – blocks that send messages to the customer, and **ACTIONS** – dialog actions and utility blocks. A description of each block can be found in the “Block Descriptions” section.

***

### Block Availability for Different Channels

The set of available blocks depends on the channel types selected in the Flow launch settings:

| Channel type | Unavailable blocks                                                                       |
| ------------ | ---------------------------------------------------------------------------------------- |
| Email        | Buttons, CSAT rating                                                                     |
| Calls        | All blocks in the MESSAGES group: Message, Buttons, Question, CSAT rating, CSAT feedback |

If multiple channel types are selected, a block is unavailable if at least one of them does not support it. Unavailable blocks are shown as inactive in the panel – they cannot be added to the canvas.

<figure><img src="https://2498134934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5yF7NRiGknx3Bqj4OgYA%2Fuploads%2FECNovCGGkcuQlipJEqoc%2Fimage.png?alt=media&amp;token=e352f9a1-2614-48e9-bd3b-43804e8efd97" alt=""><figcaption></figcaption></figure>

If you add Email or Calls to an already configured Flow, a warning icon will appear next to the blocks that these channels do not support. The icon will also appear next to the “Launch another flow” block if the selected Flow contains such blocks.

{% hint style="danger" %}
As long as there are blocks with a warning icon on the canvas, you cannot save or launch the Flow. Delete these blocks or replace them with supported ones.
{% endhint %}

***

### Flow Types: Interactive and Background

After saving or launching, the system automatically determines the Flow type based on its set of blocks:

* **Interactive** – the Flow contains at least one block that interacts with the customer or waits: Message, Buttons, Question, CSAT rating, CSAT feedback, Wait.
* **Background** – the Flow contains only action blocks (tags, assignment, status change, HTTP request, etc.). A background Flow works invisibly to the customer.

If a Flow contains the “Launch another flow” block, the blocks of the called Flow are also taken into account when determining the type. The Comment block does not affect the Flow type.

The Flow type is displayed in the Type column of the bot Flow list.

***

### How Flows are launched

When a trigger fires, the system finds all active Flows that match the trigger, conditions, and the conversation’s channel type, and then:

1. All matching background Flows are launched simultaneously.
2. Among interactive Flows, only one is launched:
   * if another interactive Flow is already running in the conversation, the new one is not launched;
   * if a simple chatbot connected to the channel is active in the conversation, it continues to work;
   * in all other cases, the first interactive Flow in the group list is launched.

{% hint style="info" %}
Background Flows can run simultaneously with any other Flows. Only one interactive Flow or simple chatbot can run in a conversation at a time.
{% endhint %}

***

### Completing and stopping a Flow

* A Flow is completed when execution reaches a block that has no outgoing connections.
* If an agent replies manually in a conversation where an unfinished Flow is running, the Flow stops and the conversation moves to the Open status.
* If a Flow is switched to Draft, edited, or deleted while running, scenarios that have already started finish according to the previous logic, while new launches follow the new one.
