Condition Nodes
Condition nodes add decision logic to your workflow. They evaluate runtime values and route execution based on whether the configured rule matches.How To Use Condition Nodes
- Configure comparison inputs and operators.
- Connect explicit branch handles (
true/falseor case handles for switch). - Keep branch outcomes intentional (for example escalate vs continue).
- Test all branch paths before enabling in production.
Choosing The Right Condition Type
- String/Number/Date/Boolean for single-value checks.
- Array for list membership and count-based checks.
- Switch for multi-path routing based on ordered case matching.
- Logical Group for nested AND/OR expression trees.
Condition Types
String Condition
Check conditions on strings and text.View
Number Condition
Check conditions on numbers and numeric values.View
Date Condition
Check conditions on dates and times.View
Boolean Condition
Check conditions on boolean values.View
Array Condition
Check conditions on arrays and their elements.View
Switch
Create multiple branches based on different conditions.View
Logical Group (AND/OR)
Combine multiple conditions with complex AND/OR logic.View
Resource Has Tags
Check if a resource has specific tags or any tags at all.View
Condition Design Best Practices
- Align operand types before comparison (string vs number vs date).
- Prefer explicit thresholds and named handles for readability.
- Always connect every branch to avoid dead-end paths.
- Add observability actions on critical false/error branches.