A workflow field may be absent, empty, or contain a value that cannot be compared as expected. Use the Condition node to check data before a later action depends on it. The node resolves the selected field from the trigger payload and earlier node outputs, then evaluates conditions in their listed order.
Configure a data check
- In the workflow editor, add or select the Condition node.
- In the node configuration, add a condition and enter a descriptive Label.
- Use Value to check to select or enter the variable path you want to evaluate.
- Choose a Comparison operator. Operators such as Exist, Does not exist, Is empty, and Is not empty do not need a comparison value.
- For operators that require it, enter the comparison text in Compare to.
- Choose the next step in Then run. Add another condition if needed.
Screenshot to add: Condition node configuration with Value to check and Comparison
Supported comparisons
- Basic operators: Exist; Does not exist; Is empty; Is not empty.
- Text operators: Equal to; Equal to (case insensitive); Not equal to; Not equal to (case insensitive); Contains; Contains (case insensitive); Does not contain; Does not contain (case insensitive); Starts with; Starts with (case insensitive); Ends with; Ends with (case insensitive); Matches regex; Matches regex (case insensitive); Does not match regex; Does not match regex (case insensitive).
- Number operators: Is equal to; Is not equal to; Is greater than; Is less than; Is greater than or equal to; Is less than or equal to.
- Date & time operators: Is equal to; Is not equal to; Is after; Is before; Is after or equal to; Is before or equal to.
- Boolean operators: Is true; Is false; Is equal to; Is not equal to.
How missing and empty values behave
The condition evaluator treats a resolved null, Boolean false, or an empty scalar string as having no value for the basic existence checks. Numeric zero is converted to the text 0, so it is not treated as an empty string. Non-scalar values are not converted to a readable text value for ordinary text comparisons.
Numeric comparisons return false when either side cannot be parsed as a number. Date comparisons return false when a date cannot be parsed. Boolean checks recognize Boolean values, numbers, and common text values such as true, false, yes, no, on, and off; an unrecognized Boolean value does not produce a successful Boolean comparison.
Do not assume the node inserts a default value or skips an action automatically. Configure a matching branch and, when appropriate, a No Condition Matched target. See Configure Workflow Fallback Paths.
Test both outcomes
- Use a test payload with the field present and a value that should match.
- Run the workflow using the editor’s available test or run control, and check which connected step executes.
- Repeat with the field omitted or empty, as appropriate for the trigger payload.
- Check the node output and run log to confirm the condition result. Do not treat a non-matching condition as a node error.
Screenshot to add: Workflow run showing the Condition result and selected branch