---
schema_version: "1"
id: 25a080f9b7b5e5d56ed5c21e2a50bab3ee76862e14c25af35bb61c1d6ec38c06
title: Build a Blueprint with Conditional Branching in Agentforce Operations Example
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_example.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_conditional_branching_example.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c29ed1560a2bdafc9db2fd6e2e3c9e10fbf438a92012135b9b1d2eb07ce96c5f
description: 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.
products:
  - Cross Cloud
release: "264"
---
# 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.

### 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="d27798e37">License Required</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e37 ">
              <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="d27798e71">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="d27798e71 ">To edit a blueprint in Agentforce Operations:</td>

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

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

## The Scenario

A procurement team onboards new suppliers. Every supplier goes through an initial intake, but what happens next depends on the contract value.

- Suppliers with a contract value of $100,000 or less go through a streamlined review.
- Suppliers with a contract value over $100,000 go through a compliance review and executive approval.

Both paths end at the same place: a final onboarding stage that sends the welcome packet and adds the supplier to the vendor system.

## Blueprint Structure

The blueprint has five stages. Stages 2 and 3 are conditional branches. Only one of them runs for a given workflow.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
          <colgroup>
            <col>
            <col>
            <col>
          </colgroup>
          <thead class="slds-text-title_caps ">
            <tr class="">
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d27798e156"><strong>Stage</strong></th>
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d27798e160"><strong>Start Condition</strong></th>
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d27798e164">
                <p style="margin-bottom:0;"><strong>Tasks</strong></p>
              </th>
            </tr>
          </thead>
          <tbody>
            <tr class="">
              <td data-label="Stage" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e156 ">1. Supplier Intake</td>

              <td data-label="Start Condition" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e160 ">When the workflow starts</td>

              <td data-label="Tasks" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e164 ">Collect supplier details: Company Name, Contact Email, Contract Value,
                Region</td>

            </tr>
            <tr class="">
              <td data-label="Stage" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e156 ">2. Streamlined Review</td>

              <td data-label="Start Condition" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e160 ">Based on specific workflow conditions: Contract Value is less than or equal
                to 100,000</td>

              <td data-label="Tasks" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e164 ">Procurement team reviews and approves</td>

            </tr>
            <tr class="">
              <td data-label="Stage" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e156 ">3. Compliance Review</td>

              <td data-label="Start Condition" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e160 ">Based on specific workflow conditions: Contract Value is greater than or
                equal to 100,000</td>

              <td data-label="Tasks" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e164 ">Compliance team reviews certifications and risk profile</td>

            </tr>
            <tr class="">
              <td data-label="Stage" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e156 ">4. Executive Approval</td>

              <td data-label="Start Condition" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e160 ">After the previous stage completes</td>

              <td data-label="Tasks" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e164 ">VP of Procurement approves or rejects</td>

            </tr>
            <tr class="">
              <td data-label="Stage" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e156 ">5. Onboarding Complete</td>

              <td data-label="Start Condition" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e160 ">After specific stages: Stage 2, Stage 4</td>

              <td data-label="Tasks" class="slds-cell-wrap" style="vertical-align:top;" headers="d27798e164 ">Send welcome packet and add supplier to vendor system</td>

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

## How It Works at Run Time

When someone starts a workflow from this blueprint and enters the supplier details in Stage 1, Agentforce Operations evaluates the conditions on Stages 2 and 3.

- Standard supplier with a Contract Value of $50,000: Agentforce Operations starts Stage 2 (Streamlined Review), and skips Stages 3 and 4. After Stage 2 completes, Stage 5 starts.
- High-value supplier with a Contract Value of $150,000: Agentforce Operations skips Stage 2, starts Stage 3 (Compliance Review), then Stage 4 (Executive Approval). After Stage 4 completes, Stage 5 starts.

## Build the Blueprint

These steps create the stages for a supplier onboarding blueprint:

1. Create a blueprint and name it **Supplier Onboarding**.
2. Add **Stage 1: Supplier Intake**. Set Start to **When the workflow starts**. Add a task that requests a Contract Value currency field.
3. Add **Stage 2: Streamlined Review**. Set Start to **Based on specific workflow conditions**. Add a condition: Contract Value **is less than or equal to** 100,000.
4. Add **Stage 3: Compliance Review**. Set Start to **Based on specific workflow conditions**. Add a condition: Contract Value **is greater than** 100,000.
5. Add **Stage 4: Executive Approval**. Set Start to **After the previous stage completes**.
6. Add **Stage 5: Onboarding Complete**. Set Start to **After specific stages** and select both **Streamlined Review** and **Compliance Review**. This merges the two branches so Stage 5 runs regardless of which path the workflow took.
7. Test the blueprint by starting a workflow with a contract value under $100,000 and another with a contract value over $100,000. Confirm that each workflow follows the correct path.
8. Publish the blueprint when both paths work as expected.