Conditions (If/Then Branches)

Required Permission

Workflow - You must have the Workflow permission to access this setting.

Conditions allow your workflow to make decisions and take different paths based on field values. Use conditions to create branching logic that handles different scenarios.

What Conditions Do

A condition node evaluates field values and directs the workflow down one of two paths:

• Yes (true) - When conditions are met
• No (false) - When conditions are not met

Conditions don't stop enrollment

A condition node runs after a record is already enrolled - the workflow has triggered and shows in execution history no matter which branch is taken. Conditions choose between actions; they don't keep a workflow from running.

If your goal is to keep the workflow from running at all for certain records, add enrollment criteria to the trigger (or narrow the trigger's change condition) instead. That filters records out before they enroll, which keeps execution history clean. Use conditions only to pick different actions for records that should run.

Adding a Condition

1. Click the + button on an edge
2. Select If/Then Branch
3. Configure the conditions
4. Click Save

The condition node appears with two outgoing edges:

• Yes branch (left or top)
• No branch (right or bottom)

Configuring Conditions

Single Condition

1. Click on the condition node
2. Click Add Condition
3. Select the Field to evaluate
4. Choose the Operator
5. Enter the Value to compare
6. Click Save

Multiple Conditions

Add multiple conditions to create complex logic:

1. Add your first condition
2. Click Add Condition again
3. Configure the second condition
4. Choose the logic:
   • All (AND) - All conditions must be true
   • Any (OR) - At least one condition must be true

Available Operators

Operator	Description	Field Types
Equals	Exact match	All types
Does not equal	Not an exact match	All types
Greater than	Value is higher	Number, Date, Money
Less than	Value is lower	Number, Date, Money
Greater than or equal	Value is higher or same	Number, Date, Money
Less than or equal	Value is lower or same	Number, Date, Money
Contains	Text includes value	Text fields
Does not contain	Text excludes value	Text fields
Starts with	Text begins with value	Text fields
Ends with	Text ends with value	Text fields
Is any of	Value matches one of selected	Dropdown, User
Is none of	Value doesn't match any	Dropdown, User
Is known	Field has a value	All types
Is unknown	Field is empty	All types
Between	Value is within range	Number, Date, Money

Condition Logic

All Conditions (AND)

All conditions must be true for the "Yes" path:

Field A = X AND Field B = Y
→ Both must be true for "Yes"
→ If either is false, take "No" path

Example:

Sale Stage equals "Proposal Sent" AND Sold Amount greater than $50,000

Yes path: Both conditions met No path: Either condition not met

Any Condition (OR)

At least one condition must be true for the "Yes" path:

Field A = X OR Field B = Y
→ If either is true, take "Yes" path
→ Only take "No" if both are false

Example:

Source is any of (Website, Referral) OR Lead Score greater than 80

Yes path: Either condition met No path: Neither condition met

Building Each Branch

After adding a condition, build out each branch:

Yes Branch

1. Click the + on the Yes edge
2. Add actions, delays, or more conditions
3. End with an End node or connect to existing path

No Branch

1. Click the + on the No edge
2. Build the alternative flow
3. End with an End node or connect to existing path

Converging Branches

Branches can lead to the same destination:

Nested Conditions

Create complex decision trees with nested conditions:

To create nested conditions:

1. Build the first condition
2. On the Yes or No branch, add another condition
3. Continue nesting as needed

Complexity Limit

Avoid excessive nesting. If your workflow has more than 3-4 levels of conditions, consider splitting into multiple workflows.

Condition Examples

High-Value Lead Routing

Source-Based Processing

Stage-Based Actions

Geographic Routing

Custom Labels

Make your conditions readable:

1. Click on the condition node
2. Enter a Custom Label
3. Example labels:
   • "High Value Check"
   • "Is Enterprise?"
   • "West Coast?"
   • "Contract Signed?"

The label appears on the node, making the workflow easier to understand.

Skipped Branches

When a workflow executes, one branch is taken and the other is skipped:

• Executed branch - Conditions were met, actions run
• Skipped branch - Conditions not met, actions ignored

In the execution history, skipped branches show as "Skipped" status.

Best Practices

Keep Conditions Simple

• Focus on one decision per condition
• Use clear, specific comparisons
• Avoid complex nested logic when possible

Name Conditions Clearly

Use custom labels that describe the decision:

• "Is VIP Customer?"
• "Amount > $50k?"
• "New vs Returning?"

Consider All Paths

Ensure both Yes and No branches lead somewhere meaningful:

• Add actions to both branches, or
• Let one branch end immediately

Test Both Branches

Before publishing:

1. Create test records that match Yes criteria
2. Create test records that match No criteria
3. Verify each path works correctly

Document Complex Logic

For workflows with multiple conditions:

• Add notes explaining the business logic
• Use descriptive labels
• Consider a separate process diagram

Troubleshooting

Wrong Branch Taken

1. Check field values at execution time
2. Verify operator selection
3. Review AND vs OR logic
4. Check for empty/null field values

Condition Always False

• Verify the field has a value
• Check if field type matches operator
• Ensure dropdown values match exactly
• Look for leading/trailing spaces in text

Condition Always True

• Review if "Is known" or "Is any of" is too broad
• Check if OR logic is being used unintentionally
• Verify value comparisons are correct

Next Steps

• Delays - Add timing to branches
• Actions - What happens on each branch
• Execution History - See which branches were taken