The film lives on a dark, dot-gridded automation canvas: nodes, bezier cables, glowing packets that hop one node per beat and status rings (grey idle · teal running · green done · coral exception). Teal carries the flow; coral is reserved for the single exception branch that needs a human — which makes the agent look auditable, not magical.
Nodes pop in from the corners every two beats, then red dashed cables draw across each other and fall loose with × ends; on bar 3’s downbeat every status ring flips to coral “!” at once and the cables shiver.
On the drop the red tangle snaps straight — all cables turn teal in one frame and route into a single port; packets race to the hub, it flashes white, the wordmark unmasks and the coral “You decide” node plugs into the bottom port on the sting.
The camera dives into the pipeline; packets hop Deploy → Checkout → Metrics one node per beat while a dashed audit link wakes Pulse below; on the bar-9 downbeat Checkout’s ring turns coral and one packet peels off down the coral branch to the exception card and the Roll back node.
The camera pulls back until the flow is a minimap; the hub grows at centre, the tagline sets, and on the sting downbeat the coral Start free node drops in and a packet travels the cable into it.
Engineers and ops buyers already think in pipelines, and a canvas shows exactly where the agent sits and where the human stays in control. Risk: spaghetti — more than seven nodes or more than one coral branch and the frame becomes a diagram nobody reads.
Adapt to your product: Draw your customer’s real process as 4–6 nodes, place your product as a node or an audit link, and give the single exception path its own colour ending in a human action.
References: https://docs.n8n.io/courses/level-one/chapter-1/ (node-canvas editor conventions (ports, nodes, execution state)) · https://docs.n8n.io/build/understand-workflows/workflow-components/canvas-groups (grouping nodes on a canvas)