A flow is a drawing of connected boxes. Each box is a step, and they run in order, from top to bottom: when something happens, do this, then that.
Example: fetch data from the ERP, update the sales dashboard and send an email saying it's ready, with the number of rows that arrived.
Difference from an agent: in the design of an agent, connecting a box grants a permission to it. In a flow, the connection is order — the lower box runs after the upper one and can use what it produced.
The list#
Where it is: menu AI → Flows.
Each row shows the name, whether the flow has been published (and which version runs) and how the last run went — Succeeded, Failed, Running or Never ran.
To create one, choose a ready-made template — Refresh the data and notify by email, Notify when a pipeline fails, Refresh the data every morning, Check and ask for approval before notifying, Daily report on WhatsApp, Weekly AI summary by email — or Start from scratch. The flow opens in the editor for you to finish.
How a flow starts#
Every flow has one start box (the trigger). Choosing another from the list replaces the current one without losing the connections.
| Trigger | When the flow starts |
|---|---|
| When I click Run | when someone clicks Run now |
| On a schedule | on its own, every hour, every day, Monday–Friday, once a week or once a month — always in Brasília time, in 15-minute increments |
| When something happens | when a pipeline finishes successfully or fails, a dashboard is updated (or fails) or a dashboard alert fires — from a chosen item or from any. Starts within 15 minutes |
| When another system calls | when an external system calls the flow's secret address (webhook) |
Automatic triggers (schedule, event and webhook) only work with the flow published and on. When you publish, the flow becomes On; the button Pause stops automatic triggers (manual runs remain possible) and Turn on re-enables it from now on — anything that would have fired while paused does not run retroactively.
The webhook address
In the When another system calls box, the Generate address button shows the
address and a secret one time only — save both. Generate another address
immediately deactivates the previous one. The other system calls the address with POST; what it sends becomes available to later boxes in "what the system sent"
(for example {{no:inicio.corpo.pedido}} for the field pedido).
For whoever programs the other system:
- check Require signature to reject calls without the header
x-ingestia-assinatura: sha256=<HMAC-SHA256 of the body with the secret>; - send
Idempotency-Keyso repeated identical calls never run twice; - responses: 202 accepted, 401 bad signature, 404 unknown address or paused flow, 413 body over 256 KB, 429 more than 60 calls per minute.
The editor#
Boxes are on the left, grouped (How it starts, Pipelines and dashboards, Notify someone…). Click one (or drag it) to add it to the flow; it enters already connected to the last box. To connect manually, drag the bottom dot of one box to the top dot of the next. The Tidy up button arranges the layout into a column without changing what the flow does.
Click a box to fill in what it needs:
| Box | What you choose |
|---|---|
| On a schedule | the frequency, the day and the time (Brasília) |
| When something happens | the event and which pipeline or dashboard |
| Run pipeline | which pipeline, and whether to wait for it to finish before continuing |
| Refresh dashboard | which dashboard |
| Send email | to whom, the subject and the message |
| Query data | the table, up to 3 filters (button Add filter), the order and how many rows — without writing SQL. Read-only; columns with sensitive personal data don't appear |
| Ask the AI | what the AI should do and with which data — it summarizes, analyzes, writes a message or classifies into one of the categories you list. Has AI cost |
| AI agent | which published agent and the question; the answer passes to the next boxes. Actions the agent proposes wait in Agents → Approvals |
| Send WhatsApp | the numbers and the message. People who opted out won't receive it |
| Call another system | the https address, the method and what to send; the response becomes data for the next boxes |
Decide, repeat and wait
| Box | What it does |
|---|---|
| If / then | compares a value ("is greater than", "contains", "is empty"…) and follows Yes or No. Numbers can be written in the Brazilian style (1.234,56). A path with no connection ends the flow there |
| For each row | repeats whatever is connected in For each once per row of a list (up to 500); whatever is in After runs once, at the end. Inside, "the current row" brings the row's fields |
| Wait | waits minutes, hours or days (up to 7) before continuing — without occupying anything |
| Merge paths | meeting point: waits for the paths that are in use (for example, the Yes and No of an If) and continues once |
| Ask for approval | stops and waits for someone to decide. Continues by Approved or Rejected; if no decision is made in time, it counts as refused |
When a flow requests approval, the Flows list shows "flow waiting for approval" and the box turns yellow in the diagram. Click it, write a comment if you want and use Approve or Reject. Workspace admins can decide; the Notify by email field sends the link to whoever needs to decide.
In text fields, the Insert data button lists what previous boxes produced — for example "Bring in the data → rows that arrived". The data is inserted into the text, and right below you see how the sentence will look.
Save, publish and run#
- The draft is saved automatically with every change.
- Publish validates the diagram and turns it into the version that runs. While something is missing, the screen lists what it is — "Run pipeline: choose which pipeline to run." — and the button waits.
- Run now runs the published version. Edited the diagram afterward? The screen warns that changes only take effect after publishing again.
During a run, each box gets a color for the result: Running…, Succeeded, Failed or Didn't need to run. Click a box to see what it produced or the error.
If a flow fails 5 times in a row, it is paused automatically, and the reason appears at the top of the editor. The same happens if the person who created the flow loses permission to run flows: it stops starting automatically on that person's behalf.
Runs#
The Runs button lists the 100 most recent: when, how it started, the result, the duration and the version. View in the drawing opens the editor with that run painted over the boxes.
Who can do what#
| Role | Can |
|---|---|
| Visualizador e membro | view the flows and the runs |
| Administrador e dono | create, edit, publish and execute |
Test environment#
Outside production nothing is actually sent: email, WhatsApp and calls to other systems appear in the box output as simulated, and data queries may return demo data — always labeled in the output, never disguised as real.