Editing a flow
The stage rail, the stage drawer, templates, flow settings, and why saving never blocks you.
01The stage rail
The edit view is the flow’s settings on the left and the rail of stages on the right. Add stage appends a column; drag a card to reorder; a stage’s automation rides beside it as its own card, tied with a line. Clicking a stage opens its drawer: name and accent, whether it ends the work, then its Checklist and Automation. Picking an automation offers Triggers, Actions and Controls; its outcomes that go somewhere else — “If it fails, go to…” — are set right under its settings. The same drawer opens from the pencil on any board column, without leaving the board.
02Starting from a template
New flow asks for nothing — a blank flow or a template, and the name lives in the editor. A template does not just draw the graph: it also creates any forms and offerings that graph refers to, as drafts, so you are editing a working shape rather than filling in blanks.
03Flow settings
The flow’s own switches live in the settings pane on the editor’s left, not on any stage: Manual entry, On the profile, Response targets, Timekeeping and its idle reminder, Assignee (and multiple assignees), notes, and how progress is measured. Turning a switch off never deletes what sits under it.
04Drafts are lenient
Save keeps whatever you have, including stages nothing reaches yet. Anything questionable comes back as a warning in the banner and never blocks the save — the wall is publish, not save.
05Test before you publish
Test runs the rail against a sample payload you type in. Conditions evaluate for real against it, so you can see which branch a value takes; actions only report what they would have done. Nothing is written and nothing sends.