Learn · Services

Flows

The four-step pipeline every job runs — watch it live.

Checked against the product on 2026-08-30 · written for everyone

A flow is the path one event takes: taken in, weighed, responded to, written down. Every event runs the same four steps, and the Flows screen shows where yours are spending their time.

The four steps, and what can go wrong at each.
Step	What happens	What a stall looks like
Taken in	The event arrives and is filed under a watched thing.	Events land under one watched thing, so the key field is missing.
Weighed	Installed rule packs decide which warning labels apply.	No label ever applies, so no pack covers this domain.
Responded to	Matching rules propose their actions.	Labels apply and nothing happens, so no rule names them.
Written down	Every step above becomes a logbook entry.	Always runs.

Note. Events about one watched thing are grouped into a story before a rule reads them. The grouping depends on the watched-thing type: a chat groups by session, a sensor by time window, a ticket by stage.

Ask the assistant to wire this in →Open your organization