Skip to Content
Raydo

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.

NeedChooseVerify before you run
Record contextGoal / Brief, a media input, or a canvas noteUse 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 appA dedicated node or capability stepChoose a supported capability, bind the intended route and resource, and check permissions and required inputs.
Transform structured dataData transformSet the source and a declared operation such as pick, dedupe, or csv_parse. Inspect the result before connecting a write.
Route executionCondition or Flow OperationDefine the condition on each edge and test both paths.
Pause for a decisionReview gatePass the proposed content, destination, and any proof the reviewer needs. Place the gate ahead of the external action.
Save an artifactDelivery choiceSelect 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.

On this page

Choose and connect workflow nodes