Playbooks
Canvas reference
The canvas is the visual editor for playbooks. Drag, connect, and configure nodes to build flows that go beyond linear chat.
Canvas anatomy
The canvas has three zones: the node palette on the left (drag nodes into the canvas), the main canvas area (connect nodes with edges), and the properties panel on the right (configure the selected node). Every playbook has exactly one Trigger node — the entry point.
Node types at a glance
| Node | Icon | What it does |
|---|---|---|
| Trigger | ⚡ | Starts the playbook — either from chat or on a schedule |
| Action | ▶ | Runs a capability step (deploy, DNS write, secret rotate, etc.) |
| Condition | ◇ | Branches the flow based on a previous step's output |
| Wait | ⏸ | Pauses until a condition is met or a timeout expires |
| Approval | ✅ | Explicit human approval gate — always shown as a confirm card |
See Node types for the full reference including all available Action step keys.
Connecting nodes
Drag from an output port on one node to an input port on another. Condition nodes have two outputs: one for the true branch and one for false. You can chain as many steps as you need — there's no limit.
Note
The canvas auto-saves as you edit. There's no save button — changes persist immediately.
Canvas tips
Start from chat
Create the playbook in chat first (describe the flow, say 'Save as playbook'), then open the canvas to add conditions or parallel branches. Chat creation handles the linear path; the canvas handles the branching.