Condition Node
Branch automation execution on field conditions, routing records to Match or No Match outputs
Last updated 8 Oct 2026
The Condition node evaluates one or more conditions against each record and routes it to one of two outputs: true (conditions met) or false (conditions not met).
When to Use
Use Condition when you need to split your automation into two paths based on field values — for example, sending records with a score above a threshold down one path and others down another.
Ports
The node has two outputs:
- true — records that match the conditions.
- false — records that do not.
Configuration
| Field | Type | Description |
|---|---|---|
conditions | array | List of { field, operator, value } conditions to evaluate |
operator | AND | OR | How to combine conditions: AND requires all to match, OR requires any (default: AND) |
Operators
| Operator | Description |
|---|---|
equals | Strict equality |
notEquals | Not equal |
contains | String contains substring |
notContains | String does not contain |
startsWith | String prefix match |
endsWith | String suffix match |
greaterThan | Numeric greater than |
lessThan | Numeric less than |
greaterOrEqual | Numeric ≥ |
lessOrEqual | Numeric ≤ |
isEmpty | Field is null, undefined, or empty string |
isNotEmpty | Field has a non-empty value |
inList | Value matches one in a comma-separated list |
notInList | Value does not match any in the list |
Example
Route high-value leads to an enrichment path:
conditions:
- field: lead_score
operator: greaterOrEqual
value: 75
- field: company_size
operator: inList
value: "enterprise,mid-market"
operator: AND
Records matching both conditions go to the true output; others go to the false output.
Notes
- The true and false outputs can each connect to different downstream nodes.
- Records are not duplicated — each record exits through exactly one output.
- With no conditions configured, every record is routed to true.
- String comparison operators (
contains,startsWith,endsWith) are case-insensitive. - For more than two branches, use Switch instead.
- Empty/null fields evaluated against numeric operators route to false (the comparison is not satisfied).
Related articles
Still stuck? Browse the FAQ or contact us.