Gearset's Agentforce metadata deployment solution simplifies the deployment of AI-powered configuration, such as Agent Scripts, in Salesforce. An Agent Script is the instruction manual for your AI. It tells the agent who it is, what it’s allowed to do, and how to use Salesforce tools to help customers while maintaining brand voice and security compliance.
This guide will explain how to successfully deploy the Agent Scripts (AiAuthoringBundle) metadata via Gearset.
What metadata is needed in the filter?
In your metadata filter, you will need to include Agent Script along with Agent Planner Bundle and Einstein Bot metadata types.
How to deploy AiAuthoringBundle with Gearset
Agent Scripts utilize a specific versioning logic when handled via the Metadata API. Scripts are automatically generated with a numerical suffix (e.g., _1, _2, _3) to denote their specific version.
During metadata comparisons, the latest version from the source is compared against the latest version in the target.
An Agent Script cannot be deployed in isolation.
Because of the deep dependencies created during the commit process, the script must be deployed alongside its generated Agents and GenAiPlannerBundles.
You will encounter a problem analyzer due to missing dependencies if you don't include them in the deployment.
When you deploy a script to a target environment, the deployment process automatically triggers the creation of a new version in the target org to preserve history and prevent the accidental overwriting of active logic.
To learn more about deploying Agentforce with Gearset check out our other documentation or get in touch with our customer support team via the in-app chat.