Choose and connect workflow nodes
Build a runnable path with explicit inputs, data transforms, approvals, and delivery.
Open a flow in Flow Library or create a blank one from Start delivery. Add nodes from the node palette, then draw connections between their handles. Select a node to configure its inputs, capability, and settings. Connections establish execution order or branch conditions. Use the step’s input mapping to pass values.
| Need | Choose | Verify before you run |
|---|---|---|
| Record context | Goal / Brief, a media input, or a canvas note | Use a media input when the next step needs the file reference. A sticky note stays on the canvas. |
| Call a model, knowledge base, browser, or connected app | A dedicated node or capability step | Choose a supported capability, bind the intended route and resource, and check permissions and required inputs. |
| Transform structured data | Data transform | Set the source and a declared operation such as pick, dedupe, or csv_parse. Inspect the result before connecting a write. |
| Route execution | Condition or Flow Operation | Define the condition on each edge and test both paths. |
| Pause for a decision | Review gate | Pass the proposed content, destination, and any proof the reviewer needs. Place the gate ahead of the external action. |
| Save an artifact | Delivery choice | Select the project when starting the run. Map the artifact explicitly if more than one upstream result is eligible. |
Connect data explicitly
For example, map a step’s query to $.run.input.query. A later step can read citations with $.nodes.<actual-node-id>.output.citations. Use the reference picker or the actual saved ID from the canvas. Check the output in run details when a value is nested or an input expects an array, object, or file reference.
Check whether a node can execute
A capability or route displayed in the editor can still require binding, plugin preflight, a grant, or a compatible runtime. A browser projection from an import is a plan until you configure a supported route. Static and review-only placeholders indicate work to resolve before relying on the branch. For imported custom code, prefer an explicit Data transform or follow the editor’s controlled code review path where available.
See workflow patterns for small graphs and runs and approvals for the execution checks.