Condition
Overview
Compares the item to check against the configured condition numeric value and continues only when the comparison is true. If value is missing or cannot be parsed as a number, the comparison is treated as false and the flow stops at this node.
Use it when a downstream branch should continue only after a numeric comparison passes. For example you can use it after evaluation or sampling nodes when the next step should run only if a numeric result passes a threshold.
How it works
FAQ
What happens when the comparison is false?
The flow stops at this node, so nodes connected after it do not run. Work already finished upstream is kept.
Can it compare text values?
No. Both sides are read as numbers. A value that is missing or cannot be parsed as a number counts as false, and the flow stops.
Where does the checked item come from?
Usually from an upstream output wired into Item to Check, such as a metric or a count produced earlier in the flow.
Inputs
Value being tested. Usually wired from an earlier node’s output, such as a count or a score. Key: ITEM_TO_CHECK.
How the item is compared with the value below. Key: COMPARISON_OPERATOR.
Options:
- Equal to (
equal_to) - Greater than (
greater_than) - Less than (
less_than) - Greater or equal to (
greater_than_or_equal_to) - Less or equal to (
less_than_or_equal_to) - Not equal to (
not_equal_to)
Number the item is compared against. Flow continues while the comparison holds, and stops when it does not. Key: CONDITION_VALUE.
JSON config
Machine-readable node interface for automation and advanced usage.