You are here:
Split a Blueprint's Path in Agentforce Operations
Route workflows down different paths based on field values from earlier stages. Use conditional branching when different inputs lead to different stages, approvals, or outcomes.
Required Editions
| License Required |
|---|
This feature is a workspace that’s external to your Salesforce org and requires an Agentforce Operations license. To purchase an Agentforce Operations license, contact your Salesforce account executive. |
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. Learn more in How Conditional Branching Works in Agentforce Operations.
When to Use Conditional Branching
Use conditional branching when a process has different approval paths based on dollar amount, risk level, or region, when some stages only apply to certain product types or supplier tiers, or when you want to skip optional stages when a field is blank.
Setting Up and Using Conditional Branching
To add conditional branching to your blueprint, you define conditions on stages by using the Conditions tab in the blueprint. You can create simple conditions with a single rule or complex conditions that combine multiple rules with AND or OR logic. Learn the step-by-step process in Configure Conditional Branching in Agentforce Operations.
To see conditional branching in action, walk through a complete example that shows how to build a procurement blueprint with different approval paths based on purchase amount. This example demonstrates creating conditions, testing them, and understanding how workflows route through different stages at run time. See Build a Blueprint with Conditional Branching in Agentforce Operations Example.
For additional real-world scenarios, review examples that show how to route workflows based on region, skip optional stages when fields are empty, and handle multiple condition groups. See More Conditional Branching Examples in Agentforce Operations.
To learn more, explore these links.
- How Conditional Branching Works in Agentforce Operations
Learn how conditions on stages control which path a workflow follows and what happens when conditions are or aren't met. - Configure Conditional Branching in Agentforce Operations
Set up conditional branching so stages in a workflow start only when specific conditions are met in Agentforce Operations. - Build a Blueprint with Conditional Branching in Agentforce Operations Example
Walk through a supplier onboarding blueprint that routes work down different paths based on contract value. This example shows how to set up conditional branching so high-value suppliers go through a compliance review and executive approval while standard suppliers follow a streamlined path. - More Conditional Branching Examples in Agentforce Operations
Use these examples to see how different field types, operators, and values create branches in a blueprint. Each row shows a condition that you can set on a stage and explains what happens when that condition is met.
