Configuration
A condition node has two or more paths. Each path has:
The default path runs when no other path’s conditions match.
Condition rules
Each condition evaluates a field against a value using an operator.
The value can hold variables, the same ones you use in actions. For example,
{{contact.email}}, {{custom.Plan}}, {{nodeId.outcome}} or {{trigger.webhook.body.orderId}}. Nedzo fills them in before it compares. {{trigger.contact.x}} reads the same contact record as {{contact.x}}, so both give the same value in a condition and in an action. If a variable in the value has no data, the condition does not match. Is empty and Is not empty ignore the value.
Available fields
- Contact fields —
firstName,lastName,email,phone,businessName,dnc - Trigger data —
tagName,channel,outcome,message, or any webhook payload field - Custom fields — Any custom field on the contact
- Previous step outputs — Reference outputs from earlier actions using dot notation (e.g.,
nodeId.outcome)
Do Not Disturb (DND)
dnc is the Do Not Disturb (DND) field on every contact. It is set to true when the contact has opted out (STOP keyword on SMS, unsubscribe link on email, a conversation with the Do not disturb outcome on any channel, or the DND switch in the contact panel), and while it is on, nothing is sent to the contact on any channel. Branching on DND lets you log or alert on opted-out contacts while the workflow continues down a “log only” path.
Typical pattern:
Operators
Date operators
Date-typed custom fields (see Contacts → Custom fields) support a separate operator set that compares calendar dates rather than string values.
Dates are compared in
YYYY-MM-DD form. The same operators are also available in the Contacts page filter bar.
Example
Route by call outcome: Trigger: Conversation ended → Agent Type: voice
Route by channel:
Trigger: Contact replied