DialNexa Workflow Condition Nodes - DialNexa Documentation

Condition Node Operators

Condition configs support common comparison operators.

Operator	Use case
equals	Route when a value matches exactly.
not_equals	Route when a value differs.
exists	Route when the field is present.
contains	Route when text contains a phrase or value.
greater_than	Route numeric values above a threshold.
less_than	Route numeric values below a threshold.

Good Fields To Branch On

Conditions work best on values that are consistently available.

Lead variables

Values uploaded or created for the workflow lead.

Values captured from call outcomes and analysis.

Success, failure, or response data from an application node.

Execution status or call outcome values when available.

Condition Review Questions

Is the field always present?

Use exists checks or defaults when a field may be missing.

Should logic be AND or OR?

AND requires all conditions. OR requires any one condition.

Are true and false paths wired?

Both outcomes should lead somewhere intentional.

Can a text value vary?

Use contains or normalized selector fields when exact text is unreliable.

Understand fields used in conditions.

Create reliable call attributes.

Debug actual branch choices.