Workflow node reference

Condition

Branch based on conditions (if/else). Exact configuration, outputs, execution behavior, errors, limits, and examples for the Condition workflow node.

Automation buildersIntermediateAvailable

What this guide covers

Category: Logic.
Use it to route an execution through Yes or No based on one or more comparisons.
2 configuration fields and 2 documented outputs.
Comparisons use current execution values; they do not query historical executions.

What this node does

Branch based on conditions (if/else)

Use it to route an execution through Yes or No based on one or more comparisons.

When not to use it

Do not use it for random experiments; use A/B Split. Do not use it to classify natural language; use Classifier.

Prerequisites

At least one available variable or value
A comparison operator and expected value
Both required output paths connected

Check before configuration

At least one available variable or value. A comparison operator and expected value. Both required output paths connected

Inputs and configuration fields

Condition configuration fields
Field	Key	Control / type	Requirement	Default	Accepted values and behavior
`Conditions`	conditions	condition-builder	Required when shown	No default	Define your conditions. Value accepted by the displayed control
`Match`	match_type	select	Optional	all	All conditions (AND) (all), Any condition (OR) (any)

Configure the node

Drag Condition from Logic in the node palette.
Select the node to open its configuration drawer.
Complete every required field and any conditional field revealed by your choices.
Insert variables only from the current trigger or an earlier node on the same path.
Connect every required output handle to the intended next step.
Save and run Workflow Test with representative data before activation.

Outputs

Later nodes can use these values only after this node has run successfully on the same execution path.

Condition output variables
Variable	Type	Meaning
`{{nodes.condition.result}}`	boolean	true or false
`{{nodes.condition.matched_conditions}}`	array	Which conditions matched

Execution behavior

Evaluates all conditions with AND or any condition with OR.
Emits a boolean result and matched-condition details.
Continues only through the Yes or No handle.

Retries and usage

Do not assume a failed node is automatically retried. Review the execution result and the relevant service documentation before repeating an operation that could create a duplicate side effect.

Example use case

Send a priority alert when the extracted order total is greater than a business threshold.

Complete workflow pattern

text

Message Received → Extract Info → Condition → Notify Team / Send Text

Common errors

Condition common errors
Symptom	Resolution
`Wrong path runs`	Check variable type, operator, expected value, and All versus Any.
`Value is missing`	Confirm the producing node ran earlier on the same path.

Limitations

Comparisons use current execution values; they do not query historical executions.

Every intended handle must be connected.

Current product limits

Comparisons use current execution values; they do not query historical executions. Every intended handle must be connected.

Workflow variables and data mappingInsert system, context, contact, custom, and node outputs with Yanola's {{variable.path}} syntax.ClassifierSort messages into categories automatically. Exact configuration, outputs, execution behavior, errors, limits, and examples for the Classifier workflow node.Variables contain unexpected valuesCheck variable scope, exact path, trigger context, execution branch, preceding node output, and value type.

Related documentation