Agentforce metadata overview
Gearset’s Agentforce metadata deployment solution streamlines the process of deploying AI-powered configurations within Salesforce.
Agentforce is an AI-powered suite of virtual agents that make life easier for all teams using and building on Salesforce.
This guide will explain how you can successfully deploy these GenAi metadata types using Gearset:
Agentforce AI Agents (GenAiPlanner)
Topics associated with Agents (GenAiPlugin)
Agent Actions (GenAiFunction)
Prompt Templates (GenAiPromptTemplate)
Learn more about Gearset’s Agentforce deployment capabilities.
License requirements
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
Supported metadata types
This table shows the Agentforce metadata types that Gearset supports.
Note: the metadata names in Salesforce differ slightly to the naming convention used in Gearset.
For easy comparisons and deployments, Agentforce metadata types are a part of our Default Agentforce comparison metadata filter.
Salesforce metadata type | Agentforce term | Gearset metadata filter term | Gearset's how to deploy guides |
Prompt Template | Prompt template | ||
Agent Action | Agent action | ||
Topic | Agent topic | ||
AI Agent | Agent |
Prerequisites
The Agentforce (GenAi) metadata types were introduced in the Salesforce metadata API version 60.
This means that when running a comparison in Gearset you must use the API version 60 or higher for these GenAi metadata types to be retrieved in the comparison.
The default comparison API version for most customers is Default (highest common version) which will take the version from your SFDX project JSON file from both source and target and will use the lower of the two.
If you're using a VCS branch as the source or target then updating your SFDX project JSON file in your VCS branch to use at least API version 60 (or higher) will allow the comparison without manually changing the API version on your filter.
{
"packageDirectories": [
{
"path": "force-app",
"default": true
}
],
"namespace": "",
"sfdcLoginUrl": "https://login.salesforce.com",
"sourceApiVersion": "60.0"
}
You can manually change the API version by editing your filter settings.
Read this article for guidelines on how to amend the API version for either manual source > target comparisons via Compare & Deploy, or in your CI jobs:
Other useful resources:
How to deploy Agentforce: A simple guide for effective implementation