The Flow Engine is currently in beta. For most onboarding scenarios, start with standard KYC Templates — they are faster to configure and cover the majority of use cases. Use flows when you need conditional branching, multi-step automation, or partner-level iteration that a static template cannot express.
Key concepts
Every flow is made up of nodes connected by edges. Each node does one thing. The edges define the path between them, optionally with conditions that route execution differently based on what a source returned.| Node type | Icon | Purpose |
|---|---|---|
| Start | 🟢 | Entry point of the flow. Every flow has exactly one Start node. Configure the trigger: manual, on document entry, on onboarding completion, or via external API. |
| Source | 🔵 | Runs a single bureau data source check. Select the source from the catalog; the node shows the provider, estimated run time, and the checks it returns. Drag a source from the right panel to create one automatically. |
| Condition | 🟡 | An explicit branching node that makes the logic visually clear on the canvas. Conditions can also be configured directly on the edges leaving a Source node — use a Condition node when you want to group several decision branches in one place. |
| Loop | 🔵↺ | Iterates over a list returned by a previous source (e.g., the list of QSA partners from receita_federal_cnpj) and runs a sub-flow for each item in parallel. Outputs include any_rejected, all_approved, and counts. |
| Manual Review | 🟠 | Pauses the flow and sends an email notification to every analyst in your tenant. The flow resumes when an analyst clicks Approve or Reject — or when the optional timeout expires. |
| Subflow | ⧉ | Calls another published flow for a single document extracted from a previous result (e.g., run the PF flow on the CPF of a company’s registered agent). Use this for one-to-one hand-offs; use Loop for one-to-many. |
| End | 🔴🟢🟡 | Terminates the flow with a final decision: Approved, Rejected, or Manual Review. Every path in a valid flow must reach an End node — the engine prevents publishing if any path has no exit. |
- Frame — a semi-transparent rectangle you can use to group related nodes visually. Create one by selecting multiple nodes and pressing
Ctrl+G. - Sticky Note — a colour-coded post-it for annotations, context, or reminders. Press
Non the canvas to create one.
Creating a flow
Open the flow builder
Go to Bureau → Flows → New Flow. Set a name, choose whether this flow applies to PF, PJ, or both, and select the default trigger.
Build your node graph on the canvas
Drag node types from the left panel onto the canvas. To add a Source node, drag a specific source directly from the source catalog in the right panel — it appears pre-configured with that source selected.
Connect the nodes
Draw edges by clicking and dragging from the output port of one node to the input port of another. You can draw multiple edges from the same node to create branches.
Configure each node and edge
Click any node to open its settings panel: select the source, write the manual review message, or set the loop’s iteration limit. Click any edge to configure its condition — choose a check (e.g., “Mandados de Prisão Ativos”), an operator (“is”), and a value (“INVALID”). Mark one edge per node as the default path so that unmatched results always have somewhere to go.
Validate the flow
Click Validate to run the engine’s pre-publish checks. It will flag dead ends (paths with no End node), disconnected nodes, missing conditions, and cycle errors. Fix any issues before proceeding.
AI-assisted flow building
If you prefer to describe your compliance logic in plain language rather than building it node by node, open the Chat IA panel (the tab next to the source catalog on the right side of the canvas). Describe the flow you want in Portuguese, for example:“Se o CPF estiver em sanções internacionais, bloquear imediatamente. Se for PEP, enviar para revisão manual com prazo de 24 horas. Caso contrário, aprovar.”The AI generates a preview of the resulting flow with a text description of what it created. Click Aplicar ao canvas to place the nodes and edges on your canvas, then review, adjust, and publish. You can also continue the conversation to refine an existing flow:
“Adicione uma verificação de antecedentes criminais antes da decisão final para clientes de alto risco.”The AI will not suggest sources that are disabled for your tenant, and it will alert you if your flow is missing verification steps required for BCB 3.978 compliance.
BCB 3.978 compliance checklist
The Flow Engine includes a built-in BCB 3.978 compliance checklist that evaluates your flow against the mandatory verification steps for individual (PF) and corporate (PJ) customers. The checklist runs automatically during validation and highlights any gaps — for example, if you have not included a PEP check in a PF flow, or if your PJ flow does not verify partners with participation above 25%. The AI assistant also monitors for these gaps during the chat session and proactively flags them before you publish.Keyboard shortcuts
| Shortcut | Action |
|---|---|
Ctrl+S | Save as draft |
Ctrl+Z | Undo |
Ctrl+Y | Redo |
Ctrl+D | Duplicate selected node |
Ctrl+G | Group selected nodes into a Frame |
Ctrl+F | Search for a node by name |
Ctrl+Enter | Publish the flow (if valid) |
Ctrl+Shift+F | Fit all nodes into view |
Delete | Remove the selected node or edge |
N | Create a new Sticky Note |
Space (hold) | Activate pan mode temporarily |
Escape | Deselect all / close side panel |
Related pages
- Templates — simpler phase-based configuration without conditional branching
- Runs — view and manage flow run results
- Data Sources — full catalog of sources available as Source nodes