📄️ Overview
The flow editor is the visual canvas where you assemble, inspect, and troubleshoot your flows. Every block on the canvas is a step; every line between blocks is the path the execution takes.
📄️ Building flows
This page walks through every gesture the editor supports while you are authoring a flow: adding, editing, removing, and arranging steps. It applies to the editor embedded on the flow card and the large editor view – both are editable canvases whenever the flow is in draft state.
📄️ Viewing executions
When you open an execution, the flow editor switches into a read-only mode and becomes a live status view instead of an authoring surface. Use it to see exactly how a flow ran — which steps succeeded, which failed, and where execution is at right now.
📄️ SmartFields
SmartFields are named placeholders you drop into a step configuration, and AutoFlow resolves them when the step runs. A token like {{customer.no}} reads the customer's number out of the flow's context just before the step runs; the step itself sees the resolved text. They are how a Decision compares values from an upstream step, how an Insert Record fills field values, how a Sleep step picks its duration, and how an HTTP Request composes a URL or body.
📄️ Notes
Notes are post-it style annotations you can drop on the flow editor canvas to document a flow in place – why a branch exists, what a temporary step is for, who owns a section, anything that helps a future reader (or your future self) understand the flow at a glance. They are part of the flow's definition, so they version with the flow and follow the same draft / publish lifecycle as the steps themselves.