Skip to content

Wiring data and nesting

Drag from a port on one step to a port on another to connect them.

A run-after edge sets the order. The second step waits for the first and nothing passes between them. Run-after ports only connect to each other.

A data edge connects one step’s output to another’s input. The second step waits for the first and gets the output as an argument.

Both look the same on the canvas. You can’t connect a step to itself or make a loop.

A port carries a parameter (a string) or an artifact (a file or directory). You can only connect matching kinds, and the canvas tells you why if you try otherwise.

To work on a repo, connect git-checkout’s repo output to the repo input of a run-script or run-container step. That step runs against the checked-out code in /work.

Any step with a result, such as http-request or a run-container with a result file, has a result output. Connect it to an input you added under Inputs from other steps, or use it in a loop or condition.

Imported steps get ports from the inputs and outputs their templates declare. To add an output to one, select it and use Outputs this step produces.

The values an imported step passes to its template are under Arguments, and you can change them there. A value set there wins over the input’s default. A step that calls a WorkflowTemplate Dagweave doesn’t have still shows what it calls and what it passes, just not that template’s settings.

A workflow that runs another DAG or steps template shows it as one subflow step. Double-click to open and edit it. The breadcrumb takes you back out with your changes. Subflows can nest.

Inside a subflow, click empty canvas to see the inputs it takes. Its steps can use them as {{inputs.parameters.<name>}}.

A template that calls itself imports as a read-only step.

A step can also reference a WorkflowTemplate by name without copying its steps. Your team’s published WorkflowTemplates are under My WorkflowTemplates in the step picker, and the WorkflowTemplate catalog has more.

Nested steps templates compile to dag, the same as top-level ones. Import and round-trip lists what else import changes.