➿Connections

➿ A connection links one step to the next and determines execution order: the step at the arrowhead runs after the step at its tail.

How connections work

After a step runs, downstream steps can read its output through a reference. Connecting steps draws the data path and defines which steps depend on which.

Fan-out

The output of one step can feed several steps, distributing data into multiple paths without repeating the original step.

Wkil example

• Trigger (WhatsApp message) → Knowledge step (RAG search) → Agent (draft response) → Condition (does it require escalation?) → App (send response / open CRM ticket).

💡 Rule: if a step needs to read a value, the step that produces it must appear earlier in the path and be connected to it.