The Condition node checks one or more rules against your flow's data and routes execution down one of two paths: True or False. Everything connected to the True side only runs if the condition passes; everything on the False side only runs if it doesn't.
This is the node to use whenever you need your flow to behave differently depending on the data — for example, only sending a Slack alert for high-value orders, or skipping a step if a field is missing.
Use a Condition node whenever your flow needs to branch, such as:
Only continue if an order total is above a certain amount
Skip a step if a customer field is empty
Send different follow-ups depending on a tag, status, or category
Filter out records that don't match certain criteria before they reach the next step
Field Required Description Step name Yes A name for this step, used to reference its result later in your flow. Must start with a letter or underscore (no spaces or special characters). Rules Yes (at least 1) One or more comparisons to evaluate. Each rule has a Value, a Condition (the operator), and, for most conditions, a Compare to value. AND / OR Only shown with 2+ rules Choose AND if every rule must pass, or OR if at least one rule passing is enough.
Value — the data you're checking. Usually a variable from an earlier step, e.g. {{order.total}}.
Condition — the comparison to apply. Options include equals, not equals, greater/less than (and or-equal variants), contains, does not contain, starts with, ends with, is empty, and is not empty.
Compare to — what you're comparing the value against. Can be plain text, a number, or another variable, e.g. 500, "VIP", or {{customer.tag}}. This field is hidden for is empty / is not empty, since those don't need a comparison value.
If both sides of a rule look like numbers, they're compared numerically (so 9 is correctly greater than 7). Otherwise they're compared as text.
Text comparisons (equals, contains, starts with, ends with) are case-insensitive.
With multiple rules, AND requires all of them to be true; OR requires only one.
Anything connected to the branch that didn't match (True or False) is automatically skipped for this run — you don't need to add extra logic to prevent it from executing.
The result is stored under the Step name you chose, with a passed field that's true or false.
Example:
Setting Value Step name checkOrderValue Rule {{order.total}} greater than 500
Later steps can reference the result as: {{checkOrderValue.passed}}
In most cases you won't need to reference this directly — just connect your next steps to the True or False side of the node, and Syncaut handles the routing.
Make sure every rule's Value field actually resolves to something — if the variable referenced doesn't exist yet at that point in the flow, the comparison may evaluate unexpectedly (e.g. against an empty string).
For is empty / is not empty checks, a value is treated as empty if it's a blank string, or literally undefined or null.
If you're comparing numbers but the comparison isn't behaving as expected, double-check the source field is actually a number and not text with extra characters (like a currency symbol), since that can prevent the numeric comparison from kicking in.
Navigate