Condition¶
Condition routes data down one of two branches after comparing string values. Use it to choose what happens next based on the incoming content, such as whether a field is empty or matches a pattern.
- Category: Processing
- Purpose: Compares two values and splits the workflow into two paths
- Inputs:
input- Value to evaluate - Outputs:
true_output- Path taken when the condition holdsfalse_output- Path taken when it does not- Configuration:
- Data Type:
stringonly. Numeric comparison is not supported — use a regular expression or a Code Node for that - Value 1: The value to test. Leave empty to use the connected node's output, or write
${{node_name.field}}to reach a specific field - Operation:
contains,ends_with,equal,not_contains,not_equal,regex,starts_with,is_empty,not_empty. Defaultequal - Value 2: The value to compare against. Unused for
is_emptyandnot_empty - Case Sensitive: Default off, which is usually correct for user input
- Usage: The comparison is literal text matching, not meaning. Synonyms will not match — use
regexwith alternatives, or an agent, when meaning matters.