Salesforce redesigns platform for agent-driven automation

Salesforce today announced Headless 360, an API-first system designed to make its software easier for AI agents to use. 

At a high level, Headless 360 allows agents to access data, workflows and logic without relying on a traditional user interface. That lets AI agents execute tasks in the background, rather than requiring users to click through dashboards.

The change reflects a broader shift in enterprise software, where automation is moving closer to the center of how work gets done. Instead of navigating tools, users increasingly rely on systems that act on their behalf.

Salesforce is not building everything from scratch. The company is layering this approach on top of existing products like Customer 360, Data 360 and its Agentforce tooling, effectively making them accessible to agents through structured interfaces.

Moving toward agent-driven workflows

The practical impact is a move away from screen-based interactions and toward orchestration. Agents can call APIs, trigger workflows and move data across systems without human intervention, which changes how processes are designed.

That shift also changes how developers think about building applications. Instead of focusing primarily on user experience, the emphasis moves toward making systems composable, accessible and understandable for machines.

There are tradeoffs. As AI systems take on more responsibility, outcomes become less predictable, which introduces new challenges around testing, governance and control.

At the same time, the flexibility of agent-driven workflows can make systems more adaptive, allowing organizations to respond more quickly to changing conditions.

A different model for enterprise software

Salesforce’s approach suggests a longer-term move toward platforms that operate as infrastructure rather than interfaces. In this model, the user interface becomes optional, while APIs and automation layers become the primary way work is executed.

That has implications for marketing and customer experience teams. If agents are handling more interactions, the focus shifts to making data and workflows accessible in ways that those agents can interpret and act on.

For developers, the change reinforces the importance of interoperability. Systems need to work together seamlessly, with standardized ways to share data and trigger actions.