Pipelines (flows)
Run any process as a kanban flow over an object — with stage rules, overdue flags and history.
A flow turns records into cards on a board. Renewals, claims, onboarding, telecalling, complaints: any process with stages can be a flow. Flows sit on top of an object, so the records stay where they are and the flow adds the process.
Creating a flow#
Go to Settings → Flows → New flow, name it, choose the object and add stages. The flows list shows each flow's stage count and a switch to turn it on or off. The demo brokerage runs 33 flows; its longest, Claims, has 22 stages.
Each flow has its own schema: fields that only matter to this process. A telecalling flow might track call outcome and callback time, fields the underlying Lead object doesn't need.
Working the board#
Open a flow from the sidebar to see it as a board (or switch to a table).
- Columns show their stage and how many cards are in it.
- Cards show the fields that matter and the owner's avatar.
- A card that's slipped past its due date turns red and says so — Overdue 1d.
- Drag a card to move it, use + Add at the foot of a column, or Filter the board to one owner before stand-up.
- Import / Export loads a backlog into the flow or takes it out.
Stage rules#
A stage can require fields before a card may enter it. A renewal can't reach Plan selected until the premium and insurer are filled in; the card stays where it is and tells you what's missing. Stages can also mark a win or a loss, so reports count outcomes honestly.
History#
Every move is written to the record: which stage, who moved it and when, and whether it was a person or a workflow. Workflows can open cards ahead of a date and close the ones that have gone quiet, so the board matches reality without a Friday clean-up.
Two examples#
| Flow | Stages |
|---|---|
| Policy Renewal | Renewal trigger (90-day) → Follow-up cascade → Quote discussion → Plan selected → … |
| Telecalling | Lead Allocation → Calling Queue → Contact Attempt → Callback → … |
On the telecalling board, each card carries the last call's outcome — Busy, Connected, Wrong Number, No Answer, Switched Off — and a workflow raises a callback task when one is due.
Through the API#
Flows live under /docs/api/flows. A record on a board is a flow item, which the API calls a state.
Add a record to a flow, optionally at a stage and with flow-specific fields:
POST /api/v1/flows/{flowId}/states{ "record": "RECORD_ID", "stage": "STAGE", "data": { "call_outcome": "Busy" }}Move an item to another stage:
POST /api/v1/flows/states/{id}/transition{ "toStage": "STAGE" }The endpoint also accepts stage. Stage rules apply to API moves exactly as they do on the board. Reading flows needs flows:view, moving items flows:use, and creating or editing flows flows:manage. GET /flows/{id} returns a flow's definition; the reference has the exact identifiers it uses for stages.