Skip to content
Zoan Docs

What flows are

A flow (Zoan Flow) is a complete business process that you draw once: the robot does its part, a person approves when needed, AI reads or classifies a document, and an API lets another system know. Zoan Cloud carries each case (an invoice, an order, a request) from start to finish and always knows which step it is on, who has it, and what to do if something goes wrong.

What you get

Section titled “What you get”
  • Fewer manual handoffs. Nobody has to remember to pass the work along: when the robot finishes, the task lands with the person who decides, and once they decide, the case moves on down the right path.
  • Every case traced. Each case keeps its step-by-step log, with dates, who stepped in, how long each step took and what data it carried. You find it by its business key (for example, the invoice number) without opening anything else.
  • Safe retries. If a step fails, the case stops right there and nothing already done is lost. Zoan Cloud only repeats on its own what certainly never ran; if the step may have done something, it warns you before repeating it so you do not record a payment or an entry twice.
  • Errors handled in bulk. Stopped cases show up in Incidentes (Incidents), grouped by step and reason, with a suggested action. If fifty cases failed for the same reason, you retry them all at once.
  • Changes without surprises. You publish versions: cases already running finish on the version they started with, and new ones use the latest.

An example

Section titled “An example”

A company receives supplier invoices. Today a robot reads them, someone reviews the large ones by email, and someone else enters them in the ERP. With a flow, that is all one process:

flowchart LR
  I((An invoice arrives)) --> R1["Robot: read the invoice"]
  R1 --> D{"Total above<br/>the limit?"}
  D -- "Yes" --> P["Person: approve"]
  D -- "No" --> R2["Robot: enter it in the ERP"]
  P -- "Approved" --> R2
  P -- "Rejected" --> F2((Rejected))
  R2 --> F1((Entered))

Each invoice is a case. In the monitor you see how many are at each step, which ones are waiting for an approval and since when, and which ones stopped and why.

The building blocks

Section titled “The building blocks”
BlockWhat it is
FlowThe process diagram, with a draft you edit and published versions. It lives in an environment.
StepEach box in the diagram: a robot, a person, AI or an integration. Gateways decide which way the case goes.
VariablesThe data that travels with each case (the invoice number, the total, the approver’s decision).
CaseOne run of the flow with its own data. It can last seconds or weeks.
IncidentA failed step that needs someone to decide what to do.

What each step can do

Section titled “What each step can do”
StepWhat it is for
RobotRuns a published process on an agent or a worker, with the case data, and keeps what it returns.
PersonCreates a task in the Tareas (Tasks) inbox for a person or a role to decide, with a form when needed; the case follows their decision.
AIExtracts data against a schema, classifies into categories or drafts a text with a model, optionally grounded in your knowledge bases.
IntegrationCalls an operation of an API connected in Centro › Recursos › Integraciones (Center › Resources › Integrations).

Where to find it in Zoan Cloud

Section titled “Where to find it in Zoan Cloud”

In the menu, the Flujos (Flows) capability works on the environment you pick at the top right:

  • Diseñar (Design): the list of flows and each one’s canvas.
  • Casos (Cases): every case, with its status and duration.
  • Incidentes (Incidents): the cases stopped by an error, grouped.
  • Monitoreo (Monitoring): how your flows are doing, where the time goes and what fails most.

In the menu rail, Flujos shows how many incidents are pending.

Next steps

Section titled “Next steps”