Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nedzo.ai/llms.txt

Use this file to discover all available pages before exploring further.

Split your workflow into different paths based on conditions. The workflow evaluates each path’s conditions and follows the first one that matches.

Configuration

A condition node has two or more paths. Each path has:
FieldRequiredDescription
LabelYesA name for this path (e.g., “Interested”, “No answer”)
ConditionsYesOne or more rules to evaluate
DefaultOne path must be marked as the default fallback
The default path runs when no other path’s conditions match.

Condition rules

Each condition evaluates a field against a value using an operator.
FieldRequiredDescription
FieldYesThe data field to check (contact field, trigger data, or previous step output)
OperatorYesHow to compare
ValueYesThe value to compare against

Available fields

  • Contact fieldsfirstName, lastName, email, phone, businessName
  • Trigger datatagName, 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)

Operators

OperatorDescriptionExample
EqualsExact matchoutcome equals “completed”
Not equalsDoes not matchoutcome not equals “voicemail”
ContainsText includes valuemessage contains “pricing”
Not containsText excludes valueemail not contains “spam”
Greater thanNumeric comparisondurationSeconds greater than 60
Less thanNumeric comparisondurationSeconds less than 10
Starts withText begins withphone starts with “+1”
Ends withText ends withemail ends with “@gmail.com”
Is emptyField has no valueemail is empty
Is not emptyField has a valuephone is not empty

Date operators

Date-typed custom fields (see Contacts → Custom fields) support a separate operator set that compares calendar dates rather than string values.
OperatorDescriptionExample
BeforeThe field’s date is earlier than the valuerenewalDate before 2026-06-01
AfterThe field’s date is later than the valuerenewalDate after 2026-01-01
EqualsThe field’s date is exactly the valuebirthday equals 2026-05-02
In BetweenThe field’s date is within an inclusive rangerenewalDate in between 2026-04-01 and 2026-04-30
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
PathConditionThen
Interestedoutcome equals “completed”Send follow-up email
Voicemailoutcome equals “voicemail”Wait 4 hours → Retry call
No answeroutcome equals “no_answer”Send SMS
DefaultAdd “needs-review” tag
Route by channel: Trigger: Contact replied
PathConditionThen
SMS replychannel equals “sms”Slack message to #sms-replies
Instagram DMchannel equals “instagram”Slack message to #social
DefaultSlack message to #general