Skip to main content
Conditions add decision-making to workflows. Use them to filter when workflows run, branch into different paths, or control execution with AI.

​
Types of conditions

​
Trigger conditions

Filter when the workflow fires:
  • Applied to the trigger node
  • Workflow only runs when conditions are met
  • Prevents unnecessary workflow runs

​
Branch conditions

Split the workflow into multiple paths:
  • Different actions for different scenarios
  • Each branch has named conditions evaluated in order
  • A default path runs if no conditions match (required)

​
AI filter

Use AI to decide if the workflow should continue:
  • Evaluates contextual criteria using AI reasoning
  • Stops or continues the workflow based on the result
  • Useful when conditions are too complex for simple field comparisons

​
Add trigger conditions

1

Select the trigger

Click on the trigger node in the builder.
2

Find conditions

Open the Conditions section 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

OperatorUse forExample
EqualsExact matchTier = A
Not equalsExclude specific valuesStatus is not Archived
ContainsText searchName contains “Smith”
Starts withText prefixEmail starts with “john”
Greater thanNumbers, datesAUM greater than 500,000
Less thanNumbers, datesAge less than 65
Greater or equalNumbers, datesAUM at least 1,000,000
Less or equalNumbers, datesPriority at most 2
Is blankMissing valuesPhone is blank
Is not blankHas valueEmail is not blank
InOne of several valuesTier in [A, B]
Not inNot one of several valuesStatus not in [Archived, Deleted]
BetweenRange of valuesAUM between 500,000 and 1,000,000

​
Combining conditions

​
AND logic

All conditions must be true: 
Tier = A AND AUM > 1,000,000
The workflow only runs for tier A clients with over $1M AUM.

​
OR logic

Any condition can be true: 
Tier = A OR Tier = B
The workflow runs for either tier A or tier B clients.

​
Condition groups

Set the combinator (AND/OR) on a condition group to control how conditions within that group are evaluated.

​
Branch actions

Use branches to take different paths based on conditions:
1

Add a branch action

Click + and select Branch.
2

Configure the first branch

Name the branch and set its conditions.
3

Add actions to the branch

Add actions that execute when conditions are met. Each branch points to a target action.
4

Add more branches

Add additional branch conditions as needed. Branches are evaluated in order.
5

Configure the default path

The default path runs if no branch conditions match. Every branch has a default path.

​
Example branch

Branch: Client tier
  If Tier = A  ->  Create urgent task
  If Tier = B  ->  Create normal task
  Default      ->  Create low-priority task

​
AI filter actions

Use an AI filter when conditions are too complex for field comparisons:
1

Add an AI filter action

Click + and select Filter (under AI actions).
2

Set criteria

Describe the conditions the AI should evaluate.
The AI filter evaluates the criteria against the current record and context, then decides whether the workflow should continue.

​
Condition field types

Conditions support several field types, each with their own set of operators:
Field typeSupported operators
Text (string)Equals, not equals, contains, starts with, ends with, is blank, is not blank
Number (integer/decimal)Equals, not equals, greater than, less than, greater or equal, less or equal, between, is blank, is not blank
Date/timeEquals, greater than, less than, greater or equal, less or equal, between, is blank, is not blank
Select (enum)Equals, not equals, in, not in, is blank, is not blank
BooleanEquals
ArrayIncludes, excludes, contains all, is blank, is not blank

​
Best practices

  • Keep conditions clear — Complex logic is harder to debug
  • Test with real data — Verify behavior for different record values
  • Use the default branch — Always have a fallback path for unexpected values
  • Prefer trigger conditions — Filter early to avoid unnecessary workflow runs
  • Use AI filter for nuance — When rules require contextual understanding, use an AI filter instead of complex branching

​
Common patterns

​
VIP treatment

Condition: Tier = A OR AUM > 1,000,000
Action: Send priority notification

​
Tier-based routing

Branch: Client tier
  If Tier = A  ->  Assign to senior advisor
  If Tier = B  ->  Assign to associate
  Default      ->  Assign to CSA

​
Prospect vs client

Branch: Household type
  If type = Client   ->  Client-specific actions
  If type = Prospect ->  Prospect-specific actions
  Default            ->  General actions

​
Next steps

Triggers

Filter at the trigger level

Actions

What actions are available

Creating workflows

Build your first workflow

Troubleshooting

Debug condition issues