Salesforce Headless 360 Explained: When the CRM Itself Becomes an API
At TDX 2026 in San Francisco, Salesforce rolled out what may be the most structurally significant announcement the company has made in a decade: Salesforce Headless 360. The pitch is simple and slightly provocative – in a world where AI agents can reason, plan, and execute on behalf of users, does a company still need a CRM with a graphical interface? Salesforce’s answer is no, and Headless 360 is the architecture built around that answer.
What Headless 360 Actually Is
Headless 360 exposes the entire Salesforce platform – data, workflows, business logic, governance – as APIs, Model Context Protocol (MCP) tools, and CLI commands. VentureBeat reported that the launch included more than 100 new tools and skills immediately available to developers, with 60-plus new MCP tools and 30-plus preconfigured coding skills aimed at coding agents like Claude Code, Cursor, Codex, and Windsurf.
In practical terms, if something can be done inside Salesforce through clicks and screens, it can now be done through an API call, an MCP invocation, or a CLI command – without a browser in the loop. The Register framed it as Salesforce turning its platform into pure infrastructure for the agentic era.
Why “Headless” Matters for CRM
Every major SaaS vendor has been shipping agent features for the past eighteen months, but most of them layer agents on top of an existing UI-first product. Headless 360 inverts that model. The user interface becomes optional – agents (human-invoked or otherwise) get first-class access to the same capabilities a human admin would reach through Setup, Metadata API, or a Lightning page.
This is a bigger shift than it looks. Salesforce is effectively saying that the screen is no longer the primary interface to the CRM. Workflows execute. Records get updated. Campaigns launch. And none of it requires anyone to log in and click anything.
The Experience Layer
One of the more interesting pieces inside Headless 360 is the Experience Layer, a UI service that separates what an agent does from how it gets rendered. Salesforce designed it so that the same agent-driven workflow can surface natively inside Slack, mobile apps, ChatGPT, Claude, Gemini, Microsoft Teams, or any MCP-compliant client. CIO described this as Salesforce extending agent-first workflows across the enterprise stack rather than forcing users into a Salesforce-branded chrome.
For marketing and customer experience teams, that means a Journey Builder journey or a Marketing Cloud campaign can increasingly be triggered, inspected, and updated from wherever the user happens to be working – including inside a chat with an AI assistant.
Built on Data 360, Customer 360, and Agentforce
Headless 360 is not a greenfield product. It sits on top of existing Salesforce primitives: Data Cloud (branded Data 360), Customer 360, and Agentforce. The difference is that each of those layers now advertises itself through a uniform, agent-readable surface. An agent doesn’t need to know that it’s talking to Data 360 versus a Flow versus a custom Apex class – it sees tools, inputs, and outputs.
This also extends to existing API surfaces. Teams that have already invested in the Marketing Cloud REST API or programmatic triggers through the Metadata API don’t lose that work; Headless 360 standardizes on top of it.
Governance Is the Quiet Headline
The flashy part of Headless 360 is agents. The durable part is governance. Constellation Research argued that enterprise agent adoption will stall unless buyers can measure, govern, debug, and tune agent behavior over time – and Salesforce has shipped governance tooling as a first-class part of this release.
That matters because the hardest problem in agentic CRM is not “can the agent do the thing?” It’s “how do we know which agent did what, with whose authority, and how do we roll it back if something goes sideways?” Headless 360 bakes in permissions, audit trails, and observability so that running agents against live CRM data isn’t a leap of faith.
AgentExchange and the Partner Play
Headless 360 launched alongside AgentExchange, a marketplace that unifies 10,000+ Salesforce apps, 2,600+ Slack apps, and 1,000+ Agentforce agents, tools, and MCP servers from partners. Gizmodo noted that Salesforce is backing the marketplace with a $50 million AgentExchange Builders Initiative – a clear signal that the company wants the ecosystem, not just its own agents, building on Headless 360.
What This Means for Marketing and CX Teams
Three takeaways for anyone running marketing automation, CX, or CRM operations. First, the long-run default for how you interact with Salesforce is going to be through an agent or a programmatic client, not through Setup. Skills that translate business requirements into tool definitions and prompt design will matter more; skills anchored purely in navigating the UI will matter less. Second, Data 360 and Customer 360 become even more central – agents can only deliver value when they’re reasoning over harmonized data. Third, governance is now a buying criterion, not an afterthought. If you can’t measure an agent, you can’t trust it in production.
Headless 360 is not a feature release. It’s an operating-model bet. Salesforce is wagering that the next decade of enterprise software is agent-first, and that customers would rather have the platform reshape itself than stitch agents on from the outside.
Share With Others
