Build

Flows

Connect forms into automated pipelines — write records and raise alerts when data changes, with branching and conditions.

A flow turns a set of forms into a pipeline. When a record is created or changes, a flow can write to another form or raise an alert — automatically, or as a one-click action. This is how a Lead becomes a Quote becomes a Sale, and how a shipped order decrements inventory.

Nodes#

A flow is a canvas of nodes connected by edges. There are three node types:

  • Form — a form on the canvas. Records flowing through the pipeline start here.
  • Action — writes to a target form. An action can set, increment or decrement fields on the target, using literal values or values pulled from the source record. It can run once per record, or once per line when the source has a Line Items field.
  • Alert — creates a notification. Give it a title and message (which can include values from the source record), a level of info, warning or critical, and a set of recipients — specific users, whole roles, or everyone.

Edges, triggers and conditions#

Edges connect nodes and decide when the next step runs:

  • An edge with no trigger fires every time a source record is created.
  • An edge with a trigger fires only when a field meets a condition — for example when status equals Won. Comparisons include equals, not-equals, and greater/less than (or equal).
  • Field mappings copy values from the source to the target on conversion, so turning a Quote into a Sale carries the customer and line items across.
  • Auto-run decides whether the step fires automatically or waits for a user to trigger it.

Action and alert nodes can carry their own condition too — an alert might only fire when qty_available drops below the reorder point.

A worked example#

The Healthcare Distributor template's Inventory Automation flow shows the pieces working together:

  1. A Sale record's status becomes Shipped.
  2. An action node iterates the order's line items and decrements the matching inventory record's available quantity (matched by SKU).
  3. An alert node checks each updated inventory record and, when stock falls below the reorder point, raises a warning notification: "Low stock: <sku>".

The result: shipping an order keeps inventory accurate and warns the warehouse — with no manual steps.

Where alerts show up#

Notifications raised by flows surface in the Alerts dashboard widget, where they can be filtered by level, kind and read state. See Dashboards for more.