> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stchat.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Flow Editor

> Build a flow with blocks: choose the trigger, connect the blocks, test, publish, and pause.

## What it is for

In the editor you draw the flow's path: when it starts, what it sends, and what it does with the contact.

It appears if the agency enabled the Flows module for the organization.

## Who can use it

* **Owner and Admins** edit, activate, deactivate, and publish.
* **Supervisors** open it read-only and can use **Test** and **Run for a contact**.
* Other roles don't edit.

## Where to click

In **Flows › My flows**, click the flow, or **Create flow** for a new blank one. The editor has two tabs: **Canvas** (the drawing) and **Trigger** (when it starts).

## Step by step

**1. Choose the trigger**

On the **Trigger** tab, open the **Trigger catalog** and search in **Search trigger…**. Triggers are grouped into **MESSAGES**, **CONTACT**, **CALENDAR**, **TASKS**, **KANBAN**, **SLA**, **FORMS**, **PAYMENTS**, **CALLS**, and **INTEGRATIONS**. Examples: **Message received**, **Tag added**, **Webhook**, **Manual**. Also choose which connections it applies to. A flow can have more than one trigger; any of them starts the flow.

**2. Add blocks**

On the **Canvas** tab, open the **Add node** panel (Tab shortcut) and drag a block onto the drawing. Connect one block to another and click it to adjust. There are categories such as **WhatsApp sending**, **Actions**, **Calendar**, **Tasks**, **Kanban**, and **Flow control**.

**3. Use the main blocks**

**Send message**, **Send media**, **Buttons**, **Send template** (approved template, for outside 24 h), **Condition** (yes or no), **Wait** (pause for some time), **Wait for reply**, **Add tag**, **Create task**, **Create card**, **Hand over to a person**, and **Call webhook**.

**4. Adjust the flow options**

There are the sections **When the contact replies** (**Stop when the contact replies**) and **Goal** (**End when the goal happens**), which make people who are waiting finish right away.

**5. Check before publishing**

Reread the blocks and messages. If the screen shows "Test is under maintenance.", testing is not available right now. **Run for a contact** sends real messages and warns: "This sends messages and creates records FOR REAL to the contact." Use it only with a contact of your own.

**6. Publish**

Click **Publish**. The window shows what changes since the live version and accepts a note under **What changed (optional, shown in the history)**. Confirm with **Publish v…**.

**7. Activate or pause**

The on/off switch next to **Active** / **Inactive** activates or pauses the flow. In **My flows**, the card of a deactivated flow shows "paused".

## What happens next

* The badge shows **Published · v1 — all live** or "unpublished changes". Without publishing, the editor keeps **Draft saved**.
* Running executions stay on the old version until they finish. Anyone who enters afterward already uses the new one.
* Under **Versions**, **Restore** copies an old version into the draft. Nothing goes live until you publish.

## Common errors

* **Choose at least one connection in the Trigger tab to activate the flow.**
* **The chosen connections left the organization or are off.** Choose another on the **Trigger** tab.
* **This trigger does not fire in the Flows engine yet** or **depends on the Call Center**. Choose another to activate.
* **The Payments module is off in this organization** and **Connect the company's Stripe in Settings › Payments** (payment triggers).
* **This automation is linked to a connection that no longer exists.** Use **Choose connection**.
* **Fields that don't exist in this flow.** Change or delete the fields; or use **Publish anyway** (they go out empty in the message).
* **Publishing failed — v… is still live.** Try again.
* **Test is under maintenance.** Message on the screen: testing is not available while it appears.

## Next step

* [Flow runs and errors](https://docs.stchat.app/en/subcontas/flows-execucoes-e-erros.md)
* [How to create a flow from a recipe](https://docs.stchat.app/en/subcontas/criar-flow-por-receita.md)
* [Flows: overview](https://docs.stchat.app/en/subcontas/flows.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.