Skip to content

Flows

A flow is a multi-step process that runs on a record and can wait: for example, request an approval by email, wait up to 3 days for the answer and, depending on it, change the state and notify.

Available steps: Notify · Comment on the record · Post to a channel · Send request · Cancel request · Change values · Pause (a duration or until a record date) · Wait for event (answer, change or comment, with a timeout) · Condition (yes or no) · Script · Integration (with retries) · Sub-flow · Reply to the site.

  1. Go to Settings → Collections → the collection → Flows (Flujos) → New flow.
  2. Build the steps on the canvas and connect their outputs with arrows.
  3. Start it from the record page, with the «Start flow» action of an automation or from a site action.
  4. The record page shows executions: Running, Waiting, Finished, Failed or Canceled, with the current step.
  • Up to 30 flows per collection. The flow’s version goes up whenever what it does changes.
  • Steps run as the flow’s author.
  • A record has a single running execution per flow.
  • Canceling an execution does not undo what its steps already did and it cannot be resumed.
  • The step log is kept for 30 days after finishing.
  • Permissions: flows:view, flows:edit, flows:run, flows:cancel.
  • get_automation_guide (flows section) before creating one; they are created with patch_schema_draft (upsert_flow).
  • list_flows, list_flow_executions, get_flow_execution to follow them.
  • start_flow (one record or up to 50) and cancel_flow_execution.