The dev loop lives on the canvas
Pin test data, run from any node, read every step's payload. Building an automation should feel like debugging code — because it is.
The worst way to build an automation is to wire up ten steps, fire the whole thing, and squint at whatever comes out the end. You can't tell which step misbehaved, and you can't test the middle without triggering the front.
Pin data, run from here
Pin sample data onto a node and downstream steps have something real to work with — so you can build and test the back half of a flow without firing the trigger. Then run from any node on the canvas, or fire a single node in isolation. The dev loop is tight, local, and on the canvas.
Every step keeps its receipts
Each run stores a per-step record — the exact input a step received, the output it produced, its status, timing, and any error. When a flow does something surprising, you don't guess; you open the run and read what actually happened at each hop.
- Pin test data on any node.
- Run from any point, or fire one node alone.
- Inspect per-step input/output/error for every run.
- Replay a run from any step with pinned or modified data.
If you can't see what a step received, you're not building — you're guessing.
Expressions make the wiring explicit — reference any field from any prior step and watch it resolve against the live data. Building an automation should feel like writing and debugging code. On OpFlow, it does.