And Operator

Waits for all connected upstream tasks to complete, then merges their outputs into a single context for downstream tasks.

Purpose

Use the And Operator as a join point when a workflow splits into parallel branches and you need to bring those branches back together before continuing. It holds execution until every upstream task has finished, then combines all of their output variables into one unified set. Downstream tasks can then reference outputs from any of the preceding branches without needing to know which branch produced them.

Inputs

This task requires no configuration fields. Connect the output connectors from each upstream task to the And Operator's input to register them as dependencies.

Outputs

This task does not produce its own named output variables. After the merge, all variables produced by the upstream tasks are available to downstream tasks directly under their original names.

Examples

Merge two parallel data-fetch branches

Two tasks — one fetching customer details, one fetching order history — run in parallel. Both connect into an And Operator. After the And Operator completes, a downstream task can reference variables from both fetches in one place.

[FetchCustomer] ──(Completed)──┐
                               ▼
                         [And Operator] ──(Completed)──▶ [BuildReport]
                               ▲
[FetchOrders]   ──(Completed)──┘

No fields need to be set on the And Operator itself.