---
schema_version: "1"
id: 48d959db24c6cec220b2d487417d80ad02234af445c2c35e74e023a26c14e205
title: Add a Linked Blueprint 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_linked_add.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_linked_add.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f15ebaa55ae714108d33f9751036a8e118a00fdb85c7b42484b57bf38ee5fc8d
description: Nest a child blueprint inside a parent blueprint to trigger a subprocess and pass data between workflows at run time. You can only link blueprints that are in the same workspace.
products:
  - Cross Cloud
release: "264"
---
# Add a Linked Blueprint in Agentforce Operations

Nest a child blueprint inside a parent blueprint to trigger a subprocess and pass data between workflows at run time. You can only link blueprints that are in the same workspace.

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

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d29814e73 ">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 the **\+ Workflow** button.
3. Select the blueprint to use for the linked blueprint.
    
    You can select any existing blueprint or create one. To create one, scroll to the end of the blueprint list and click **\+ Create new blueprint**.
    
    If the child blueprint has input fields configured in its Intake section, those fields appear in the **Send info** section so you can map values from the parent to the child.
4. Select whether the linked blueprint starts when the stage starts, after a specific task ends, or on a specific date.
5. Send information from the parent to the child blueprint at run time by mapping parent fields to child input fields.
    
    To pass information from the parent to the child, the child blueprint must have input fields configured in its Intake section.
    
    These mapped fields become workflow-level fields in the child workflow.
    
    1. In the **Send info** section, for each required input field in the child blueprint, select a matching field from the parent.
        
        Fields must be the same data type. For example, you can't pass a checkbox field value to a date field. If the field names match exactly, Agentforce Operations automatically maps them. If you don't see a field to pass, verify that a field of the same type exists in an upstream task in the parent blueprint or check the child blueprint's Intake section to confirm that the child blueprint has input fields.
6. Select any output fields that you want to receive back from the linked blueprint at run time.
    
    1. In the **Receive info** section, click **Add fields**.
    2. Select the fields that you want to send back to the parent blueprint.
    3. Click **Apply**.
    
    At run time, when the child workflow running from the blueprint completes, Agentforce Operations returns the selected output fields to the parent workflow running from the blueprint. You can use these fields in downstream tasks and approvals.
7. Click **Add.**
    
    Agentforce Operations adds the child blueprint to the parent blueprint as a task in the stage.

When you publish the parent blueprint, Agentforce Operations automatically publishes any linked child blueprints that aren't published. However, before the linked child blueprint can be published, it must have version notes. If the child blueprint doesn't have version notes, add version notes on the child blueprint before publishing the parent.