Build Complex Processes with Linked Blueprints in Agentforce Operations

What Linked Blueprints Are

With linked blueprints, you can nest one blueprint inside another to create parent-child workflow relationships. The parent blueprint acts as a coordinator that triggers one or more child blueprints at specific points in the process. Each child blueprint runs as a separate workflow with its own tasks, assignees, and completion criteria.

Use linked blueprints to break complex processes into manageable, reusable components. Instead of building one large blueprint with dozens of tasks, you can create smaller blueprints for distinct subprocesses and link them together. This modular approach makes blueprints easier to maintain, test, and reuse across different parent processes.

When a parent workflow reaches the linked blueprint task, Agentforce Operations automatically creates and starts the child workflow. The parent workflow tracks the child's progress and waits for it to complete before moving to the next task. You can pass field values from parent to child at the start, and receive output fields back from the child when it completes.

Note Child workflows can have their own child workflows. You can nest linked workflows to any depth needed for your process.

How Linked Blueprints Work

To link blueprints, add a child blueprint as a task in the parent blueprint. Configure when you want the child workflow to start: when the stage starts, after a specific task completes, or on a specific date. You can link multiple child blueprints within a single parent, either in sequence or in parallel.

Both parent and child blueprints must be in the same workspace. You can't link workflows across different workspaces.

Passing Information Between Workflows

To pass field values from parent to child, the child blueprint must have input fields configured in its Intake section. When you add the linked blueprint task in the parent, map parent fields to the child's input fields. Fields must have matching data types. For example, you can't pass a text field to a date field. These mapped fields become workflow-level fields in the child workflow and are available to all tasks in the child.

To receive information back from the child, select output fields from the child blueprint. At run time, when the child workflow completes, Agentforce Operations passes the selected output fields to the parent workflow. You can use these fields in downstream tasks and approvals in the parent.

Blueprint and Workflow Access

Access levels aren't inherited between parent and child blueprints. Users need appropriate access to both the parent and child blueprints to publish the parent or start workflows from it. If someone can view the parent workflow but not the child, they can't see the child workflow details.

Tracking and Managing Linked Workflows

Both parent and child workflows appear in your Home page workflow list. Child workflows appear after the linked task starts and Agentforce Operations creates them. To group related workflows together, add the Top Workflow ID column to your Home page view. Parent and child workflows share the same Top Workflow ID.

In the parent workflow, the linked task shows the child workflow's completion percentage as it progresses. To view detailed information about the child workflow, click Open workflow from the task card.

When you pause the parent workflow, Agentforce Operations automatically pauses all child workflows. When you resume the parent, the system resumes any child workflows it paused. If you end the parent workflow, the system stops all child workflows.

Blueprint Versions and Updates

When you create a parent workflow, Agentforce Operations locks the version of the child blueprint. If you publish a new version of the child blueprint, existing parent workflows continue to use the version they started with. New parent workflows use the latest published version of the child blueprint.

If you update a child blueprint to add or change input fields, you must update the parent blueprint to map values to the new fields. If you don't update the parent, new parent workflows get stuck at the linked task until you provide the missing field mappings.

Setting Up and Managing Linked Blueprints

Add a linked blueprint to a parent blueprint by inserting it as a task. Configure the child's start condition, map input and output fields, and publish the parent. To learn more, see Add a Linked Blueprint in Agentforce Operations.

After a linked workflow starts, monitor its progress from the parent workflow. View completion status, open the child workflow for details, or check the Top Workflow ID to find related workflows. To learn more, see Track a Linked Child Workflow in Agentforce Operations.

If you need to disconnect a child workflow from its parent after the workflow starts, you can unlink it. The child workflow continues running independently but no longer reports status to the parent. To learn more, see Remove a Linked Workflow in Agentforce Operations.

Understand how linked workflows interact at run time, including access inheritance, pausing behavior, and how ending a parent affects its children. To learn more, see Linked Workflow Behavior and Access in Agentforce Operations.

To learn more, explore these links.