Automations

If / Else Condition Node

4 min readnode-condition

Branch the automation based on whether a field or variable matches a condition.

Evaluates a condition against any lead field or {{variables}} value and routes to one of two branches: True or False.

When to use it

---

Required fields

Field	Type	Required	Description
field	string	Yes	Dot-notation path: `lead.email`, `variables.score`, etc.
operator	enum	Yes	`equals`, `not_equals`, `contains`, `not_contains`, `gt`, `lt`, `exists`, `not_exists`
value	string	No	The value to compare against (not needed for `exists`/`not_exists`)

---

Optional fields

None.

---

Variables available

This node does not produce output variables, but downstream nodes receive the same variable context.

---

Operators explained

Operator	Meaning
`equals`	Strict equality (case-sensitive)
`not_equals`	Not equal
`contains`	String contains substring
`not_contains`	String does not contain substring
`gt`	Numeric greater than
`lt`	Numeric less than
`exists`	Field/variable is set and non-empty
`not_exists`	Field/variable is missing or empty

---

Step-by-step setup

Add an If/Else node to the canvas.
Set Field — e.g. lead.phone.
Set Operator — e.g. exists.
Leave Value empty (not needed for exists).
Connect the True handle to your WhatsApp node and the False handle to an email fallback.

---

Example config

json { "field": "variables.score", "operator": "gt", "value": "75" }

---

Tips & gotchas

All comparisons are string-based unless the value looks numeric and the operator is gt/lt.
exists is the safest way to gate nodes that need a field — always wrap WhatsApp/SMS nodes with an exists check on the phone field.
You can chain multiple If/Else nodes to create multi-branch logic.