younifyd
Menu

Conditional Branch Connector

Model IF / ELSEIF / ELSE branching with branch-specific workflow steps — only the first matching branch's steps run.

Browse 1 Conditional Branch actions workflow
On this page

What this connector is for

Models IF / ELSEIF / ELSE branching directly on the workflow canvas: each branch has its own condition and its own nested steps, evaluated top-to-bottom, with only the first matching branch's steps actually running. Nothing external happens here; it's purely a structural control-flow point, so there's no request/response to configure.

All fields are listed in the action reference.

Conditional Branch

  • Branches are checked in order; the first branch whose condition is true wins, and later branches (even ones that would also match) never run. The optional ELSE branch runs only if no earlier branch matched. With no match and no ELSE, the step completes having run nothing.
  • Each condition is a left operand, operator and right operand, or nested AND/OR groups built by the condition-tree widget. Operands accept a literal or a {{...}} expression (step output, {{trigger...}}, {{runtimeVariables.x}}; see Step Reference). The operators exists, notExists, isTrue, isFalse, isEmpty and isNotEmpty ignore the right operand.
  • Steps inside a branch are normal steps: named, referenced by their own reference (e.g. {{applyDiscount.response.data.<field>}} regardless of which branch they live in), and with their own execution settings.
  • If a step inside the matched branch fails, the Conditional step is marked failed and carries that step's own error message, not a generic "branch failed" one.

Reading the response

This is the step's own output, distinct from what the branch's steps produced:

  • {{<stepReference>.response.data.matchedBranchId}} — id of the matched branch (null if none).
  • {{<stepReference>.response.data.matchedBranchLabel}} — its label (e.g. "IF", "ELSE").
  • {{<stepReference>.response.data.branchResult}} — the final result of the last step that ran inside the matched branch (null if no branch matched or it had no steps).

Example

text
Branches:
  - label: IF
    condition: {{trigger.body.total}} greaterThan 100
    steps: [Apply Free Shipping]
Includes Else branch: true
  - (ELSE) steps: [Charge Standard Shipping]

A branch commonly contains a For Loop or ends with a Break Loop to exit a loop conditionally.

Also applies here

Step Name

What it's for

Every step in a workflow gets a name — either one you set or a default based on the connector and action (e.g. "Get Order Details", "Send Welcome Email"). It's shown throughout the UI and in your execution history, and it's also the source for the step's Reference — a camelCase identifier auto-generated from the name (e.g. "Get Order Details" → getOrderDetails) — which is what you actually use in {{...}} expressions to read this step's output from later steps. See Step Reference.

Rules

  • Must be at least 2 characters, and 50 characters or fewer.
  • Must be unique within the workflow — reusing a name that's already taken will be rejected, with a suggested alternative (e.g. "Get Order Details 2").
  • Can't be empty.

Tips

  • Prefer a descriptive, human-readable name over a generic one — "Get Order Details" is easier to work with later than "HTTP Request 2", especially once a workflow has a dozen steps.
  • Renaming a step updates every reference to it elsewhere in the workflow automatically.

Step Reference

Syntax

Any input field can reference earlier data using {{expression}}. The expression is evaluated as JSONata — so simple dot-paths and more advanced queries (filters, functions) both work.

Referencing a step's output

Use the step's Reference — a camelCase identifier auto-generated from its Name (e.g. "Get Order Details" → getOrderDetails), shown read-only wherever the step's fields are configured — followed by the field path. Elsewhere in these docs this general pattern is written as {{<stepReference>.field.path}}:

text
{{getOrderDetails.response.data.id}}
{{getOrderDetails.response.status}}

The raw display name won't work here even though it's what you see in the UI — {{Get Order Details.response.data.id}} isn't valid, since a bare name containing spaces isn't a single JSONata identifier. Always use the camelCase Reference.

You can also reference steps by position instead of by reference:

text
{{steps[0].response.data.id}}

Referencing trigger data

text
{{trigger.headers.authorization}}
{{trigger.body.customerId}}
{{trigger.query.page}}
{{trigger.params.orderId}}
{{trigger.method}}
{{trigger.path}}

Referencing workflow variables

text
{{variables.myVariable}}

See Variables for the full list of variable types and more examples, including connection-type variables.

Referencing runtime variables

A separate, mutable namespace written by the Variable connector while a run is in progress — not the same as the workflow-level variables above:

text
{{runtimeVariables.myVariable}}

Notes

  • If an expression can't be resolved (a typo in a step name, a field that doesn't exist), it resolves to an empty string rather than failing the workflow — check your execution history if a value comes through blank.
  • Object values are automatically JSON-stringified when interpolated into a string field.
Was this page helpful?

Last updated 9 October 2026