Merge If Branches¶
Merges results from multiple conditional branches into a single output. It selects the first input that is present (non-null), prioritizing lower-numbered inputs when more than one branch produced a value. Supports any data type passed from upstream nodes.
Usage¶
Use this node to rejoin workflow paths after an If (or other conditional) split. Connect the final output of each branch (e.g., true/false) to the corresponding inputs on this node. Downstream nodes can then consume a single merged result regardless of which branch executed.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| branch_1 | False | * | Result from the first conditional branch (e.g., the 'true' path). If provided and non-null, it has priority over branch_2. | Output from the True branch of an If node (e.g., 42) |
| branch_2 | False | * | Result from the second conditional branch (e.g., the 'false' path). Used if branch_1 is not provided or is null. | Output from the False branch of an If node (e.g., "fallback result") |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| merged_result | * | The selected result from the connected branches. Returns the first non-null value among the inputs, or null if neither branch provided a value. | 42 |
Important Notes¶
- Selection priority: If multiple branch inputs are present, the node returns the value from branch_1 before branch_2.
- Optional inputs: Both inputs are optional—only the branch(es) that executed need to be connected.
- Type flexibility: Accepts and outputs any data type; ensure downstream nodes can handle the merged type.
- Null behavior: If no branch produces a value, the node outputs null.
- Typical wiring: Connect outputs from an If node (e.g., index 0 to branch_1, index 1 to branch_2) to this node.
Troubleshooting¶
- Output is null: Ensure at least one branch is connected and produces a non-null value. Verify the condition routing upstream.
- Unexpected branch chosen: Remember branch_1 has priority. Swap connections if you need branch_2 to take precedence when both are present.
- Downstream type errors: Confirm the downstream node supports the type produced by the executing branch. Consider normalizing types across branches.
- Unconnected inputs warnings: It's safe to leave an input unconnected if that branch may not execute, but ensure at least one branch will provide a value at runtime.