Using the editor
Adding and connecting steps
The Steps panel, drag or tap to add, forgiving connections, exits, cancel handles, and tidying the canvas.
Adding
- Search the Steps panel: it matches labels, descriptions and the help text.
- Drag a card onto the canvas; it lands where you drop it.
- Tap or press + on a card to add it at the centre of the view (the only way on touch screens).
- The Integration action step appears only when the hub has reported integration services.
- The ? on a card opens the step's help: what it does, an example chain, and the outcome.
Connecting
- Drag from a step's exit handle (right side) and release anywhere over the target step; the whole card is a drop zone, so you do not have to hit the small handle.
- Triggers (When steps) have no incoming handle.
- Two-exit steps show two handles. The secondary exit (otherwise, inactive) draws dashed and labelled. Day parts shows one handle per period plus No period and Away.
- Wait and Wait until have two incoming handles: the normal one and cancel.
- Several connections out of one exit run in parallel; a step may receive connections from many steps.
Click a connection to select it; Delete / Backspace removes selected steps and connections.
Arranging
- Tidy layout (header menu) auto-arranges the whole graph; it is disabled when the canvas is already tidy.
- Select several steps by dragging on empty canvas (or the select tool), then move them together.
- Ctrl/Cmd+C / X / V copy, cut and paste steps with their connections, including between flows and tabs; Ctrl/Cmd+A selects all; Ctrl/Cmd+Z / Shift+Ctrl/Cmd+Z undo and redo.
What the issues strip is telling you
| Message | Meaning |
|---|---|
| This step is not connected to anything | an orphan; connect or delete it |
| Nothing leads to this step, so it will never run | reachable only from nowhere |
| Add a "When" step — this flow has no trigger | nothing can start the flow |
| A trigger cannot be a step — incoming connections are ignored | you connected something into a When step |
| An "otherwise" connection only makes sense from a condition | a dashed connection from a non-And step is treated as normal |
| Loop detected | fine to leave; each step runs at most once per run |
| "…" is not a state this device reports — use one of: … | a typed state matched neither a raw token nor a label for that device; pick one of the listed values |
The complete list, with which ones block publishing, is on Validation messages.