Types of conditions
Trigger conditions
Filter when the workflow fires:- Workflow only runs when conditions are met
- Applied to the trigger node
- Prevents unnecessary workflow runs
Branch conditions
Split into multiple paths:- Different actions for different scenarios
- Each branch can have its own conditions
- Workflow follows the matching branch
Filter actions
Stop the workflow mid-execution:- Evaluate conditions after earlier actions
- Stop if criteria aren’t met
- Continue if criteria are met
Add trigger conditions
1
Select the trigger
Click on the trigger node in the builder.
2
Find conditions
Look for Conditions or Filters in the properties panel.
3
Add a condition
Click Add condition.
4
Configure
Select:
- Field — What to evaluate
- Operator — How to compare
- Value — What to compare against
5
Add more
Add additional conditions as needed.
Condition operators
| Operator | Use for | Example |
|---|---|---|
| Equals | Exact match | Tier = A |
| Not equals | Exclude specific values | Status ≠ Archived |
| Contains | Text search | Name contains “Smith” |
| Starts with | Text prefix | Email starts with “john” |
| Greater than | Numbers, dates | AUM > 500000 |
| Less than | Numbers, dates | Age < 65 |
| Greater or equal | Numbers, dates | Days since contact ≥ 30 |
| Less or equal | Numbers, dates | Priority ≤ 2 |
| Is empty | Missing values | Phone is empty |
| Is not empty | Has value | Email is not empty |
| Is true | Booleans | Active is true |
| Is false | Booleans | Archived is false |
Combining conditions
AND logic
All conditions must be true:OR logic
Any condition can be true:Complex logic
Combine AND and OR:1
Add condition group
Click Add group to create nested conditions.
2
Set group logic
Choose AND or OR for the group.
3
Add conditions to group
Add conditions within the group.
Branch actions
Use branches to take different paths based on conditions:1
Add Branch action
Click + and select Branch.
2
Configure first branch
Set conditions for the first path.
3
Add actions to branch
Add actions that execute when conditions are met.
4
Add more branches
Click Add branch for additional paths.
5
Set default
Optionally set a default path if no conditions match.
Example branch
Filter actions
Stop the workflow if conditions aren’t met:1
Add Filter action
Click + and select Filter.
2
Set conditions
Define when the workflow should continue.
3
Choose behavior
- Continue if met — Proceed when conditions are true
- Stop if not met — Halt when conditions are false
Example filter
Available fields
Fields available in conditions depend on the trigger and record type:Household fields
| Field | Type | Example |
|---|---|---|
name | Text | ”Smith Family” |
tier | Select | A, B, C, D |
status | Select | Active, Inactive |
aum | Number | 500000 |
created_at | Date | 2024-01-15 |
Person fields
| Field | Type | Example |
|---|---|---|
first_name | Text | ”John” |
last_name | Text | ”Smith” |
email | Text | ”[email protected]” |
date_of_birth | Date | 1960-05-15 |
Task fields
| Field | Type | Example |
|---|---|---|
title | Text | ”Follow up call” |
priority | Select | High, Medium, Low |
due_date | Date | 2024-02-01 |
status | Select | Pending, Complete |
Opportunity fields
| Field | Type | Example |
|---|---|---|
name | Text | ”Smith retirement” |
value | Number | 500000 |
probability | Number | 60 |
stage | Select | Qualified |
Date conditions
Work with dates in conditions:Relative dates
| Expression | Meaning |
|---|---|
| Today | Current date |
| Tomorrow | Next day |
| Next week | 7 days from now |
| Last month | 30 days ago |
Date calculations
| Condition | Meaning |
|---|---|
| Due date < Today | Overdue |
| Created > Last week | Created in past 7 days |
| Birthday = Today + 7 days | Birthday in 1 week |
Best practices
- Keep conditions simple — Complex logic is hard to debug
- Test edge cases — Verify behavior for all scenarios
- Use meaningful names — Document what conditions check
- Consider defaults — Always have a fallback path
- Don’t over-filter — Too many conditions can block legitimate runs