---
schema_version: "1"
id: 9a75f8220b881d27b62b65f44a94b19169df14cbafd99649f21b5bb097335e8f
title: Configure Conditional Branching in Agentforce Operations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_afsc_blueprints_conditional_branching_configure.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_conditional_branching_configure.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 5492a0b97979bc7aed7f4c5bb4984bb9ba99bda6bb787d8edd20e3526ff3aef7
description: Set up conditional branching so stages in a workflow start only when specific conditions are met in Agentforce Operations.
products:
  - Cross Cloud
release: "264"
---
# 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.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="1" style="text-align:left;vertical-align:top;" id="d11587e39">License Required</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d11587e39 ">
              <p>This feature is a workspace that’s external to your Salesforce org and requires
                an Agentforce Operations license. </p>
              <p style="margin-bottom:0;">To purchase an Agentforce Operations license, contact your Salesforce account
                executive.</p>
            </td>

          </tr>
        </tbody>
      </table> <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:left;vertical-align:top;" id="d11587e73">Role or Access Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d11587e73 ">To edit a blueprint in Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d11587e73 ">Admin role, Creator role, or a user with Edit access for the blueprint</td>

          </tr>
        </tbody>
      </table>

1. [Create a blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_create_blueprint.htm&release=264.0.0&type=5 "Use AI to generate a blueprint by describing your process and optionally uploading supporting documents. You can also build a blueprint from scratch or import one from another workspace. Anyone with the Creator role can generate blueprints in Agentforce Operations.") or [edit an existing blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_edit.htm&release=264.0.0&type=5 "Open an existing blueprint for editing to add stages, tasks, automations, or other changes.").
2. In the blueprint, click **\+ Add stage**.
3. Enter a stage name.
4. For Start, select **Based on specific workflow conditions** or **Based on specific stage conditions**. With these options, you can use values from earlier fields to control when the stage starts.
5. If you selected **Based on specific stage conditions**, select a previous stage to tie the condition to.
6. Add your first condition.
    
    1. Select a field from a prior stage.
    2. Select an operator. For example, **Is equal to**.
    3. If applicable, enter or select the value needed for the condition to be met.
    
    The operators available depend on the field type. For example, number and currency fields support `greater than or equal to`, `less than or equal to`, and `equal to`.
    
    ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-agentforce_operations-264-0-0-production-enus/dce314e6-0a31-4a8b-98f7-3d2a3fd02ee2/images/icon_tip.png)
    
    Tip
    
    Use `is empty` to create a branch that runs only when a field has no value. For example, when an optional field wasn't filled out by the user.
7. Select if the new condition must also be true or if the new condition can be true instead of the previous condition.
    1. If the new condition must also be true, select **and**.
    2. If the new condition can be true instead of the previous condition, select **or**.
8. To add a nested layer of conditions, click **\+ Add condition group** and add the nested conditions.
    
    Condition groups make it possible to build more complex logic by grouping conditions together. You can't add a condition group inside another condition group.

When the workflow runs, Agentforce Operations uses the data from earlier inputs to determine what happens:

- Stages where conditions are met start automatically after the selected previous stage.
- Stages where conditions aren't met are skipped.