Skip to main content
The Condition node asks a yes/no question and sends your workflow down different paths based on the answer. It’s like a fork in the road: “If this is true, go left. If not, go right.”
Condition node configuration form

Condition configuration — build the check with dropdowns or write an expression.

​
When to Use

  • Checking data - Make sure something looks right before continuing
  • Making decisions - Do different things based on what happened
  • Handling errors - Check if something worked, handle it if not
  • Filtering - Only process things that match certain criteria

​
Three Ways to Set Up Conditions

​
Manual Mode (Easiest - No Code)

Just pick from dropdown menus:
  1. Choose what to check (like the email subject)
  2. Choose how to check it (contains, equals, greater than, etc.)
  3. Enter what you’re looking for
Example: Check if an email subject contains “urgent”
What you can check for:

​
Expression Mode (More Flexible)

Type a formula. Useful when you need to check multiple things:
You can use:
  • Comparisons: == (equals), != (not equals), >, <, >=, <=
  • Logic: AND, OR, NOT
  • Parentheses: ( ) to group things

​
AI Mode (Let AI Decide)

Just describe what you’re looking for in plain English:
The AI reads the data and decides if your description matches.
AI mode takes 1-3 seconds to think. Use manual or expression mode when you can for faster results.

​
Example: Lead Qualification

Route leads based on score:
1

Score the lead

Use an Ask AI node to analyze lead data and return a score 0-100.
2

Add the condition

Add a Condition node:
  • Mode: expression
  • Expression: {{llm_1.response.score}} >= 70
3

Connect both paths

  • Met → External API (add to “Hot Leads” in CRM)
  • Unmet → External API (add to “Nurture” campaign)
Workflow:

​
Example: Error Handling

Check if an API call succeeded:
Configuration:
  • Mode: expression
  • Expression: {{http_request_1.statusCode}} == 200 AND {{http_request_1.success}} == true

​
Example: Content Filtering

Only process emails that meet criteria:
Manual mode configuration:
  • Group 1 (AND):
    • {{event_from_app_1.email.from}} NOT contains noreply
    • {{event_from_app_1.email.subject}} NOT starts with Re:
    • {{event_from_app_1.email.subject}} NOT starts with Fwd:

​
Combining Conditions

​
AND Logic (all must be true)

Manual mode: Add rules to the same group Expression mode:

​
OR Logic (any can be true)

Manual mode: Create multiple groups Expression mode:

​
Complex Logic

Use parentheses in expression mode:

​
Nested Conditions

Chain conditions for complex decision trees:
For more than 3-4 branches, consider using a Multi-Condition node instead of nested Conditions. It’s cleaner and easier to maintain.

​
Tips

Use descriptive condition names like “Is High Priority?” or “Has Valid Email” instead of “Condition 1”.
The unmet branch doesn’t need to connect to anything. If a condition is unmet and there’s no unmet path, that execution branch simply ends.
Be careful with type comparisons. "100" (string) is not equal to 100 (number). Use Execute Code to convert types if needed.

​
Settings

​
string
default:"Condition"
What to call this node (shown on the canvas).
​
string
default:"condition_1"
A short code to reference this node’s result.
​
string
default:"manual"
How to set up your condition:
  • manual - Choose from dropdowns (easiest, no code needed)
  • expression - Type a formula like {{score}} > 80
  • ai - Describe it in plain English and let AI figure it out
​
object
For manual mode: the rules you’ve set up.
​
string
For expression mode: your formula.
​
string
For AI mode: your plain English description.

​
Outputs

The Condition node has two outputs:
​
handle
Green (Yes) - Goes here when the condition is true.
​
handle
Red (No) - Goes here when the condition is false.
​
boolean
True or false - you can use this value in later nodes.

Multi-Condition

For multi-way branching with more than two paths.

Wait and Combine

Rejoin branches after conditional splits.