The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Building and testing agents in the new Agentforce Builder (opens in a new tab)

You will learn how to create an agent from a natural-language description, switch between Canvas and Agent Script views, and test with Simulate and Live Test before committing and activating a version.

Why read this

It is a practical walkthrough of the Builder's main workflow.

  1. Describe the agent in natural language
  2. Refine in Canvas or Script view
  3. Test in Preview
  4. Commit Version
  5. Activate the version
The Builder workflow from creating an agent to going live

The new Agentforce Builder, found under Agentforce Studio, is presented as a way to make agent behavior more predictable by combining an upgraded reasoning engine, Agent Script that mixes natural language with programmatic logic, and built-in AI assistance. An agent can be started by describing its role and tasks in natural language, after which Agentforce generates an initial configuration that can be refined through chat or configured manually.

The Builder is organized into an Explorer for navigating settings, subagents, actions, variables and connections, a Canvas for editing configuration in a low-code block view, a Preview panel for testing, and an Agent Optimizer for natural-language changes. Canvas and Script views stay in sync, so changes made in one are written into Agent Script in the other. Typing a slash adds inline logic such as if/else conditionals, and typing an at-sign opens a resource picker for subagents, actions and variables.

Preview offers Simulate, which skips permission checks and does not run actions or touch data, and Live Test, which runs actions and changes data in the org. Both show reasoning explanations, traces, variable values and timing per step. Finally, a version is committed as a locked snapshot and activated; only one version can be live at a time, and activating a new one turns the previous one off.

Read the original at Salesforce Time (opens in a new tab)

Worth reading?

Skills admins need to build with AIforce's MCPs, Skills and Plugins (opens in a new tab)

You will learn how MCPs, Skills and Plugins fit together in the AIforce extensibility stack and which new admin skills to pick up first.

Why read this

It gives a roadmap and the training trails to follow.

  1. User triggers a Plugin
  2. Skill fires
  3. MCP executes
  4. Output returns to user
How the AIforce building blocks work together when a user acts

The post introduces AIforce as a new layer of the AI extensibility stack and explains three building blocks. MCP, the Model Context Protocol, is a standard bridge between an AI interface and live systems, data and APIs, so admins can expose flows, APIs and Apex without writing custom code for each system. Skills define the exact steps, rules and formatting an AI needs to complete a task consistently, and Plugins package MCP connectors, Skills and interfaces into a single installable product. It describes a flow in which a user triggers a Plugin, a Skill fires, an MCP executes and the output returns to the user.

The author lists the new admin skills to develop: MCP management, including centralised org-wide connections and Agentic Identity; building deterministic agent logic with Super Agents and Subagents; lifecycle management of Plugins mapped to user roles; and using Agentforce Coworker, Agent Script, Builder Central and Agentforce Vibes for AI-assisted building. The roadmap moves from AI Trust, Security and Governance trails through hands-on work with Agentforce Studio to advanced building and packaging, then ongoing change management.

The article is largely an overview with links to trails, workshops and resources rather than technical implementation detail, so practitioners will get orientation more than hands-on specifics.

Read the original at Salesforce Admins Blog (opens in a new tab)

Worth reading?