Execute the Code Extension Workflow by Using Agentforce Vibes
Author, debug, and deploy Data 360 code extensions by using natural-language prompts in Agentforce Vibes IDE. You can also use local IDEs, such as VS Code, Windsurf, and Cursor, where the Agentforce Vibes extension is enabled.
Prompts work best when you follow the natural workflow sequence—each step builds on context from the previous one. The exact wording of your prompt is flexible. Agentforce Vibes uses the built-in Data 360 skill context to interpret your intent and carry out the action.
To author and deploy Data 360 code extensions by using natural-language prompts in Agentforce Vibes:
Permission set:
Data Cloud Architect
Prerequisites
Make sure that you have access to a Data 360 sandbox and the Data Cloud Architect permission set. If you don’t have a sandbox, create one. See Create a Data 360 Sandbox.
Enable skills for Agentforce Vibes if you haven’t already. See Enable Skills.
Update the Salesforce Skills version to the latest available version by enabling the Auto Update Skills setting. See Salesforce Skills in Agentforce Vibes.
Ensure that you have these Salesforce skills, which are enabled by default.
Skill
Description
data360-code-extension-generate
Guides end-to-end code extension development and deployment.
data360-schema-get
Retrieves DLO and DMO schema metadata so that you can validate object and field names before testing and deploying a code extension.
The data360-code-extension-generate skill installs the Code Extension plugin for the Salesforce CLI and the Data Custom Code Python SDK automatically if they aren’t already present.
Note
Before you start prompting, note these expected behaviors.
Agentforce Vibes can pause and ask you to review and approve certain commands before running them. For example, terminal commands or file operations that aren’t pre-approved. When prompted, review the proposed action and click Run Command to approve or Reject to cancel.
Agentforce Vibes can ask for your org alias during the workflow. For example, running local tests or deploying. Sometimes, it determines the org automatically by running sf org list. If prompted, provide your org alias to continue.
In Agentforce Vibes chat, describe each workflow action. For example, use these prompts.
Initialize a code extension package.
create new code extension script package named code_extension_pkg_1
Author the script.
Refer to @/code_extension_pkg_1/payload/entrypoint.py and modify that file to read Employee DLO and write to Employee_Hierarchy DLO. Make sure to compute values for all the fields of Employee_Hierarchy DLO.
Agentforce Vibes uses the data360-schema-get skill to retrieve schema context and the data360-code-extension-generate skill to update payload/entrypoint.py based on your prompt.
j