Learn how blueprints work as reusable templates for automated workflows in Agentforce Operations.
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. |
Getting Started with Blueprints
Blueprints are reusable templates for automated workflows. They're a structured process with a defined beginning and end. Create a blueprint first, and then start workflows from it to run your process. To learn about how blueprints relate to workflows, fields, and tasks, see How Blueprints, Workflows, and Tasks Connect in Agentforce Operations.
Creating a Blueprint
Start by creating a blueprint that defines your process. Give it a name and description, and configure basic settings. Learn more in Create an Automation Template with a Blueprint in Agentforce Operations.
Adding Stages
Organize your blueprint into logical phases by adding stages. Stages group related tasks together and control when each part of the workflow runs. Learn more in Stages in Agentforce Operations.
Configuring Tasks
Add tasks to your stages to define the work people or AI agents need to complete. Configure task details such as assignees, due dates, and required information. Learn more in Tasks in Agentforce Operations.
Working with Fields and Forms
Define the data that your blueprint collects by adding fields. Create forms to organize how users see and complete those fields. Fields can be required or optional, and you can create custom field types to match your data needs. Learn more in Collect Information from Users in Agentforce Operations.
Organizing with Tags
Use tags to categorize and filter blueprints and workflows. Tags help teams find related work and organize processes by department, product line, or any other criteria. Learn more in Organize Workflows with Tags and Tag Categories in Agentforce Operations.
Publishing Your Blueprint
After you configure your blueprint, publish it to make it available for creating workflows. Publishing creates the first version. Learn more in Publish a Blueprint in Agentforce Operations.
Linking Multiple Blueprints
A linked blueprint nests a child blueprint inside a parent as a sub-process. The linked blueprint doesn't run independently. The parent tracks the child's progress and can receive output fields back from it. At run time, both appear on the Home page as independent workflows. Access levels don't inherit between parent and child. A blueprint can contain up to four linked blueprints. Learn more in Build Complex Processes with Linked Blueprints in Agentforce Operations.
Blueprint Versions
Every time you publish a blueprint, Agentforce Operations creates a new version of the blueprint and updates the change log to include the new version. Admins and editors can add version notes when publishing a new version and restore any previous version. There's no limit on the number of versions a blueprint can have, so teams can evolve and improve their processes over time. Learn more in Manage Blueprint Versions in Agentforce Operations.
Blueprint Variants
Blueprints can include multiple variants to support different scenarios, such as regions, product lines, or customer types. Variants are alternate versions of a standard blueprint that run different stages and tasks based on conditions you define, such as a single-select field value. Every variant collects the same data as the standard blueprint but routes the work differently. When a workflow starts, it evaluates the conditions. Each variant has its own version history and Blueprint ID. Learn more in Customize How a Blueprint Runs Based on Criteria with Variants in Agentforce Operations.
Conditional Branching
Blueprints support conditional logic that routes work down different paths based on field values, dates, or other criteria. For example, route high-value orders through an additional approval stage, or send international orders through customs documentation tasks. With conditional branching, you create flexible processes that adapt to different scenarios without creating separate blueprints. Learn more in Split a Blueprint's Path in Agentforce Operations.
Locked Workflows
Lock published blueprints to prevent changes to workflows after they start running. Locked workflows can't have their stages, tasks, or structure modified while the workflow is in progress. Locking ensures process consistency and prevents accidental changes to in-progress work. Admins can still make changes to locked workflows. Learn more in What You Can and Can't Do in Locked Workflows in Agentforce Operations.
Additional Blueprint Features
Blueprints include several features that help you organize, track, and manage your automated processes:
- Workflow reference IDs: Assign unique identifiers to workflows created from a blueprint. See Manage Workflow Reference IDs in Agentforce Operations.
- Autogenerate workflow names: Create dynamic workflow names by using field values. See Autogenerate Workflow Names with Merge Fields in Agentforce Operations.
- Collaborative editing: Multiple people can work on the same draft blueprint at the same time. See Collaborative Blueprint Editing in Agentforce Operations.
- Dynamic due dates: Automatically adjust task due dates when upstream tasks complete early or late. See Set Up Dynamic Due Dates in Agentforce Operations.
To learn more, explore these links.
- Create an Automation Template with a Blueprint in Agentforce Operations
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. - Stages in Agentforce Operations
Stages organize the tasks in a blueprint into logical phases. Use stages to break a process into manageable milestones and control when each part of the workflow runs. - Tasks in Agentforce Operations
Tasks are the individual units of work in a blueprint. Configure tasks to collect the right information, route work to the right people, and shape how each step behaves at run time. - Collect Information from Users in Agentforce Operations
Use fields and forms to request, collect, and pass information through tasks and workflows in Agentforce Operations. - Set Up Dynamic Due Dates in Agentforce Operations
Configure a blueprint to automatically shift downstream task due dates when upstream tasks complete late or early in Agentforce Operations. - Import a Blueprint from Another Workspace
Export a published blueprint from one workspace and import it into another workspace in Agentforce Operations. During import, review and map the blueprint's dependencies to your workspace. - Organize Workflows with Tags and Tag Categories in Agentforce Operations
Use tags to classify blueprints and workflows in Agentforce Operations. Use tag categories to organize your tags in the list of tags. You can filter workflows by tags in the Home page workflow list view. - Autogenerate Workflow Names with Merge Fields in Agentforce Operations
Create a naming convention for workflows so each workflow started from a blueprint gets a consistent, descriptive name based on field values in Agentforce Operations. - 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. - Customize How a Blueprint Runs Based on Criteria with Variants in Agentforce Operations
Use variants to adapt a published blueprint for different teams, regions, or scenarios while preserving the original blueprint. - Manage Workflow Reference IDs in Agentforce Operations
Set up unique reference IDs so Agentforce Operations automatically assigns a trackable identifier to every workflow created from a blueprint, or turn off reference IDs when you no longer need them. - Customize Blueprint Behavior in Agentforce Operations
Customize how a blueprint behaves at run time. Configure naming conventions, reference IDs, variants, and other settings to standardize and control the workflows that run from a blueprint. - Build Complex Processes with Linked Blueprints in Agentforce Operations
Build complex, multi-stage processes by linking multiple blueprints together in Agentforce Operations. Reuse existing blueprints as building blocks so one workflow can automatically trigger and track another as part of a larger operation. - Publish a Blueprint in Agentforce Operations
Publish a blueprint to make it available for others to use in Agentforce Operations. - Blueprint Limits in Agentforce Operations
Blueprints have limits on the number of tasks, fields, and form items they can contain. These limits help you avoid the performance issues that come with oversized blueprints.