Introduction
An Agentforce agent is an AI-powered assistant built on Salesforce’s Agentforce platform that can help users by handling questions and tasks without needing constant guidance. It is designed to help teams work faster and more efficiently by combining generative AI with Salesforce data, automation, and decision-making capabilities.
This guide will explain how to successfully deploy Agentforce Agents via Gearset.
Prerequisites
In both source and target orgs, Agentforce / Einstein Generative AI must be enabled through Setup.
Your Metadata API version must be 60.0 or higher because the Agentforce (GenAI) metadata types (like GenAiPlanner, GenAiFunction, GenAiPlugin, etc.) were introduced starting in API version 60.
Please, ensure that you have the necessary permission set licenses to retrieve Agentforce metadata types.
The required licenses include:
Agentforce (Default)
Agentforce Service Agent Builder
Einstein Prompt Templates
Prompt Template Manager
What metadata is needed in the filter?
To move an Agentforce agent from one org to another, you generally need to deploy the metadata that covers the core agent definition and its version, the planning or reasoning configuration, and the associated topics, actions, and prompt templates that power the agent’s functionality.
It is recommended to select Default Agentforce comparison filter to include all the required dependencies in the comparison.
How to deploy an Agent with Gearset
If the agent was created using the Agent Script editor, you need to select the Agent Script (AiAuthoringBundle) metadata type in the filter. Check out this document on how to deploy Agent Scripts.
If the Agent was created using a Template or the standard UI, select the Agent planner bundle metadata type.
You can see the dependencies under Depends on section. Make sure that all dependencies already exist on the target org. If they don't, then you'll need to deploy them alongside the Agent.
If any dependencies are missing, the Problem Analyzer will provide suggested fixes. Review and include these flagged components before proceeding to the Pre-deployment summary.
Gearset will then display a summary of the deployment package. Review it thoroughly to confirm all desired components are included and click Validate deployment.
Activate the Agent
Gearset allows you to automatically activate the Bots and Agents post-deployment.
On the summary page, enable the Activate Bots and Agents after deployment option to automatically activate the Agents in the target org.
Once you have enabled the activation, click Deploy. Gearset will then begin the deployment process deploying the Agentforce Agents and their dependencies to your target.
Check out this short demo of deploying Agents, and please reach out to the in-app chat with any follow up questions.
Check out these related documents on deploying Agentforce metadata types: