Build on the canvas

The canvas is where the Workflow takes shape. You add nodes, connect one's output to another's input and configure each one in the side panel.

Every runnable flow starts at an Input node and ends at an Output node.

Add and connect nodes

The add button opens the palette, with nodes grouped by purpose and search by name. Nodes can also be dragged straight onto the canvas.

Each node has input and output handles. Dragging from an output handle to an input handle creates the connection and sets the execution order.

Clicking a node opens the side panel with its configuration. That is where you choose an LLM node's model, a vector node's Collections, an HTTP request's URL.

Input and output

The Input node defines the form the person fills in when running the flow. Each field declared here becomes a field in that form.

The Output node defines what the person gets at the end. Anything that doesn't go through it stays in the run log, but isn't shown as a result.

Reference what came before

Nodes consume what earlier nodes produced. An LLM node builds its prompt from earlier outputs; a condition node evaluates those same values.

Since the connection sets the order, a node only reaches what is upstream of it. Nodes in parallel branches don't see each other until an aggregation node brings them together.

Draft and publishing

Like Agents, Workflows have a draft and a published version. Only the published one is available for other people to run, in the Chat Agents area.

Editing and republishing replaces the version in use. Runs already recorded stay as they are.

Test before publishing

Run the flow from the studio itself before publishing, with real input. The run log shows what each node received and returned, which is the fastest way to find a misconfigured node.

A flow that always fails at the same node is almost never a connection problem: it is that node's configuration, visible in the side panel.

Next steps

• Choose the right nodes in Node catalog.
• Investigate the result in Runs.