Condition nodes are the decision-making centers of your workflows. They evaluate data and create branching paths, allowing your automation to respond dynamically to different scenarios and inputs.

​
How Conditions Work

Every condition node follows the same basic pattern:
  1. Input: Takes a value from your workflow (like user data, API responses, or previous step outputs)
  2. Evaluation: Compares that value using a specific operator
  3. Output: Produces a boolean result (true or false)
  4. Branching: Routes your workflow down different paths based on the result
Here’s a simple example of how this works in practice: You can connect the true and false output handles to different downstream actions, creating separate execution paths that respond intelligently to your data.

​
Available Condition Types

Choose the appropriate condition type based on your data. Each condition type is optimized for specific data formats and use cases.

​
String Condition

Compares text values. Ideal for checking status fields, user inputs, or any other string-based data.

​
Configuration

​
input
variable
required
A reference to the string value to check.
​
operator
string
required
The comparison to perform. Options: equals, not_equals, contains, not_contains, starts_with, ends_with, regex.
​
value
string
required
The value to compare against.
For the regex operator, you must provide a full, valid regular expression pattern including delimiters (e.g., /pattern/i).

​
Number Condition

Compares numerical values. Use this for checking counts, amounts, IDs, or any other numeric data.

​
Configuration

​
input
variable
required
A reference to the number to check.
​
operator
string
required
The comparison to perform. Options: equals, not_equals, greater_than, less_than, greater_than_or_equal, less_than_or_equal.
​
value
number
required
The number to compare against.

​
Date Condition

Compares dates and times. Useful for checking if an event is in the past, if a deadline is approaching, or comparing two timestamps.

​
Configuration

​
input_date
string or variable
required
The date/time value to check.
​
operator
string
required
The comparison to perform. Options: is_past, is_future, is_today, is_weekend, is_weekday, is_before, is_after, is_same_day, is_within, is_not_within.
​
comparison_date
string or variable
Required for is_before, is_after, is_same_day.
​
value
integer
Required for is_within and is_not_within (e.g., 7).
​
unit
string
Required for is_within and is_not_within. Options: days, weeks, months, etc.

​
Boolean Condition

Checks if a value is true or false. It intelligently handles various representations of truthiness, such as the boolean true, the number 1, or the string "true".

​
Configuration

​
input
variable
required
A reference to the value to check.
​
operator
string
required
The comparison to perform. Options: is_true, is_false.

​
Array Condition

Performs checks on arrays (lists) of items. This is useful for verifying if a list of users was found, checking if a specific value exists in a list, or iterating to see if any item meets certain criteria.

​
Configuration

​
input_array
variable
required
A reference to the array to check.
​
operator
string
required
The comparison to perform. Options: is_empty, is_not_empty, count_equals, count_not_equals, count_greater_than, count_less_than, contains_value, does_not_contain_value, any_item_matches.
​
value
any
Required for count and contains checks.
​
conditions
array of conditions
Required only for any_item_matches. This allows you to define a set of conditions that will be tested against each item in the array. If any single item satisfies all the nested conditions, the node returns true.

​
Logical Group Condition

A powerful node that allows you to combine multiple conditions with AND/OR logic, including nested groups. This enables the creation of highly complex decision-making rules in a single step.

​
Configuration

This node has a nested structure. The top-level group defines the primary logic (AND or OR) and contains a list of rules. Each rule can be either a simple condition or another nested logical group.
​
logic
string
required
The logic for the group. Options: AND, OR.
​
rules
array
required
An array of rules. Each rule is an object that is either a Condition or another Logical Group.

​
Switch Condition

Evaluates a series of conditions in order and routes the workflow down the path of the first one that matches. This is more efficient than a long chain of if/else if condition nodes.

​
Configuration

The Switch node is configured with a list of “cases”.
​
cases
array
required
An ordered list of cases to evaluate.

​
Behavior

  • The cases are evaluated from top to bottom.
  • The first case where all of its internal conditions are true is considered a match.
  • The workflow then proceeds down the path connected to that case’s unique handle.
  • If no cases match, the workflow proceeds down the default path.