The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Salesforce Headless 360 exposes the platform to agents through APIs and MCP (opens in a new tab)

You will learn what Salesforce Headless 360 offers through its three access paths, why governance has to move from the UI to the schema, and how to start a controlled pilot with a Hosted MCP Server.

  1. Pick one workflow
  2. Audit the schema
  3. Connect a sandbox client
  4. Define agent identity and limits
  5. Test, trace and measure
A five-step plan for a first Headless 360 pilot

Salesforce Headless 360 is an architecture that exposes Salesforce capabilities through APIs, Model Context Protocol (MCP) tools and CLI commands, so AI agents, apps and developer tools can use the platform without a browser. Announced at TDX 2026, it keeps the data, workflows and business logic built over 25 years, and the company now also calls the offering Headless Toolkit. Salesforce cites more than 60 MCP tools, 30 preconfigured coding skills, 4,000 APIs and 220 CLI commands, and states that Lightning and the browser remain available for human users.

The piece explains three access paths. APIs serve developers and integration platforms that read and write records. MCP tools let AI clients such as Claude, ChatGPT and Cursor discover and call capabilities at runtime, with no custom integration code written in advance. CLI commands support scaffolding, testing and deployment through DevOps pipelines. MCP tools are further split between coding agents, which read metadata, generate Apex and deploy, and business agents, which reach Salesforce from Slack or other chat clients. Hosted MCP Servers became generally available in April 2026, and the Headless 360 MCP Server followed in beta in July 2026. Every Hosted MCP call runs as the authenticated user through an External Client App with the mcp_api scope, and the article warns that pricing via Flex Credits may bill for usage, so teams should confirm terms with their account team.

For architects, the central change is that governance moves from the screen to the schema. An agent never sees a page layout, so Validation Rules, sharing models, Apex and approvals must carry the controls. The article proposes a four-layer view of experience, access, execution and data, and lists review questions about rule placement, least-privilege Permission Sets, human-only actions and approval points for high-risk actions. It also covers the Headless Experience Layer and Multi-Framework support for React, and notes that agent testing needs evaluation sets, session tracing and the Agentforce Testing Center. MuleSoft supplies governed access to systems outside Salesforce, while Data 360 supplies unified customer context.

The article suggests starting with one workflow, auditing the schema, connecting a sandbox Hosted MCP Server to one client, defining agent identity and limits, and then testing, tracing and measuring results against the manual process. It treats vendor customer stories as reference points only and advises a pilot to generate real evidence.

Read the original at Cloud Odyssey (opens in a new tab)

Worth reading?

Using latest for the REST API trades upgrade control for convenience (opens in a new tab)

You will learn what the latest alias for REST API versions changes, why it shifts upgrade timing onto your release testing, and why even fixed versions still depend on the current platform.

Fixed version

  • Upgrade is a planned event
  • Testing happens before the switch
  • Still runs on current platform

latest alias

  • Upgrade arrives with the release
  • No action needed to adopt it
  • Testing moves to release preview
Fixed versions and latest differ in who decides when an upgrade happens

Winter ’27 lets integrations target the REST API with the alias latest in place of an explicit version number such as v68.0. The alias removes the need to update integration versions every four months and spares you from tracking version retirements, since requests always reach the current release.

The author argues the convenience comes at a cost of control. An integration on latest picks up whatever Salesforce treats as current, so when the next version arrives, behavioral differences, new fields or updated metadata can reach your code without a planned upgrade. Salesforce recommends fixed versions for production integrations with a specific contract and latest for scripts and internal tools.

The post also points out that a fixed version does not fully protect you. Once a new version goes live, requests to older fixed versions are served by the current platform with backward compatibility applied, so the platform underneath you still changes. The author concludes that non-critical work can use latest, while critical integrations should stay on fixed versions and be regression tested every release.

Read the original at Bob Buzzard Blog (opens in a new tab)

Worth reading?

Salesforce Winter '27 brings Flow testing, bulk screen actions, and higher heap limits (opens in a new tab)

Readers will learn how to implement the new Flow Test Mode, process multiple records via List Views, and adjust to increased Apex heap limits and updated REST API versioning without manual tracking.

The release introduces Test Mode for Flow Builder, enabling repeatable testing with assertions and mock outputs for external callouts. Screen Flows launched from List Views or Related Lists can now process multiple selected records by accepting a lowercase ids collection variable. Reactive Formulas allow Conditional Visibility to evaluate same-screen inputs instantly, while new save-time validation catches missing Required Fields and character limit breaches before runtime.

Logic handling gains Split by Field Value and Split by Date elements, which create automatic branches but do not fully replace Decision elements. Navigation improves through an Unused Resources filter, Element Grouping, and an Edit History panel. Security receives a User Context option that enforces running user permissions, and an org-wide toggle preserves Manual Shares when record ownership changes.

Synchronous Apex transactions now support a 10 megabyte heap limit, while asynchronous transactions reach 25 megabytes, with a transition setting available to manage the shift. List View inline editing expands to include off-page layout fields and mixed Record Types. Integrations may use latest for REST API versioning, and Field History Tracking becomes generally available for the User object.

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

Also told by Salesforce Ben on YouTube (opens in a new tab)

Worth reading?

How API-Driven Integration remains essential as AI agents expand into Salesforce (opens in a new tab)

You will learn which three integration APIs form the foundation of Salesforce connectivity and how they support emerging AI agent workflows.

Why read this

The piece also outlines the current certification roadmap and upcoming MuleSoft credential changes.

The video argues that artificial intelligence agents interact with the platform through application programming interfaces rather than user interface clicks, making integration expertise increasingly vital. It identifies three foundational tools that practitioners should master first.

The REST API handles standard create, read, update, delete operations and data queries. The Bulk API processes large scale jobs involving fifty thousand or more records. Platform Events combined with the Pub/Sub API enable reliable publish subscribe messaging between systems.

The Certified Platform Integration Architect certification path serves as a stepping stone toward System Architect and CTA designations. Two MuleSoft credentials will retire on February 1, 2027 while the product line continues to operate. Salesforce now classifies Headless 360 capabilities under Agentforce revenue metrics, reporting annual recurring revenue exceeding one point five billion dollars.

Watch the video at MyTutorialRack on YouTube (opens in a new tab)

Worth reading?