Action connections

Connections between action cards define the execution path through a Workflow.

The current canvas shows connection points at the edges of cards and lines between connected steps. For a simple linear Workflow, following those connections across the canvas should make the main route easy to understand.

Connect the path, not just the picture

A line is meaningful because it determines which step can follow another. Moving cards for readability does not change execution; changing the connection can.

When extending a Workflow, either add a new action and connect it into the path, or use a connection point where the editor offers a direct way to add the next action.

Branching and flow control

Not every Workflow is linear. Flow-control actions can create alternative routes. In those cases, make the branch condition explicit and keep each outgoing path visually distinct enough to review.

Do not infer branch semantics from screen position alone. The action configuration and its outgoing connections determine the actual route.

Data flow and execution flow are related

Connections establish execution order, while variables and bindings determine what information a later action receives. A visually connected Workflow can still be wrong if a downstream action is bound to the wrong value.

Review both:

• path — did the right actions execute in the right route?

• data — did each action receive the right inputs and produce the expected outputs?

Before publishing

Run the draft with representative inputs and inspect the trace. A neat connected canvas is not proof that the Workflow behaves correctly in external systems.

For editor navigation see Canvas Controls. For the individual steps see Action Cards.