How Conditional Branching Works in Agentforce Operations

How Conditional Branching Works

By default, stages in a blueprint run in sequence: Stage 1 completes, then Stage 2 starts. Conditional branching changes that. You add conditions to a stage so it starts only when it meets specific criteria. Stages where conditions aren't met are skipped.

Conditions evaluate field values from earlier stages by using operators such as equals, greater than, or is empty. You can combine multiple conditions with AND or OR logic, and group conditions together to create more complex rules.

When to Use Conditional Branching

• A process has different approval paths based on dollar amount, risk level, or region.
• Some stages only apply to certain product types, supplier tiers, or request categories.
• You want to skip optional stages when a field is blank or a checkbox is deselected.
• Different teams handle different parts of the same process based on the input data.

Supported Field Types

You can use all field types and data sources as conditions except Document fields.

Key Concepts

Mutually exclusive branches

When two stages have conditions that can't both be true at the same time. For example, Contract Value field greater than or equal to 100,000 and Contract Value field less than or equal to 100,000, only one branch runs.

Parallel branches

When two stages have conditions that can both be true, both stages run at the same time. Use overlapping criteria when separate teams work in parallel.

Merging branches

Use the After specific stages start condition to bring branches back together. Select all the stages that could be the last stage before the merge point. The merge stage waits for whichever branch actually ran to finish.