Introducing the A2A Bridge for Agentforce
Overview
For years, enterprises have invested in integration to keep their systems talking. Now they are investing in AI agents, and discovering the same problem of lack of interoperability all over again. Agentforce agents run customer service in the CRM, Copilot agents work across Microsoft 365, and cloud-native agents handle everything in between. Each is powerful on its own. Together, they don’t always speak the same language.
The agent ecosystem is consolidating around Agent2Agent (A2A) as the open standard for inter-agent communication running in production across more than 150 organizations. Agent Fabric already discovers agents from every major platform and catalogues them in Agent Registry. But orchestration has been limited to agents that natively speak A2A and some enterprise agents don’t, yet.
Today, that changes. Without changing a single line of agent code, you can present your existing agents as first-class A2A citizens to any downstream consumer. That’s what the A2A Bridge — a new Agent Fabric capability — makes possible: it translates protocols, maps identifiers, synthesizes the A2A task lifecycle, and handles authentication, so any non-A2A agent appears fully A2A-compliant. The first supported platform is Agentforce.
Why It Matters
Agent Fabric’s promise is simple: turn your agents into business action, with a single plane of visibility and control. But until now, discovery had outrun action. The Agent Scanner could catalog your Agentforce agents and catalogue in Agent Registry — yet the Agent Broker couldn’t orchestrate them, because those agents don’t expose A2A endpoints. You could see your entire agent estate; you could only put a sliver of it to work.
Salesforce has already announced native A2A, but production-ready A2A exposure is still maturing. The projects that need multi-agent orchestration are being planned now. The A2A Bridge closes that gap on day one, and it matters because:
- Put the agents you already have to work: Bring Agentforce agents into multi-agent A2A flows with zero changes to those agents no rewrites, no platform migration, no waiting on a vendor roadmap.
- One policy and observability plane: Authentication, PII detection, schema validation, rate limiting, audit logging, and end-to-end tracing apply uniformly across native and bridged agents.
- Configuration, not code: A guided experience stands up a working bridge in minutes and publishes the A2A card so the Scanner and Broker can find it.
- A migration path with no regrets: When Agentforce ships native A2A, you simply replace the A2A bridge with the native card so the A2A clients keep working. The bridge is an accelerant, not a lock-in.
And this capability is unique in the market: no competitor, across cloud agent platforms, iPaaS, or AI gateways, offers a bridge that takes a non-A2A agent and makes it speak A2A.
Use Cases
The Agentforce A2A Bridge enables the following scenarios for your enterprise:
| Capability Theme | Use Case | Business Impact |
|---|---|---|
| Cross-Vendor Collaboration | Salesforce service agents run inside multi-agent MuleSoft flows, enabling CRM-native automation such as case routing and order management to operate as standard A2A tasks alongside agents from other platforms. | Compose cross-vendor agent workflows today, with zero changes to existing Agentforce agents. |
| Task Visibility & Trust | Every bridged Agentforce interaction is authenticated, policy-checked, and traced, with task metrics, latency, and errors flowing into the MuleSoft observability stack. | One policy and audit plane across native and bridged agents — one set of rules, not one per platform. |
| Immediate Deal Enablement | Customers adopt Agent Fabric orchestration for their Agentforce estate now, rather than waiting for native A2A support to mature, with a seamless cut-over once it ships. | Unblocks in-flight initiatives and protects multi-agent project timelines. |
Key Features
This release delivers full A2A bridging for Salesforce Agentforce agents:
- Protocol translation on Omni Gateway: The bridge is an Omni Gateway policy that translates between A2A and Agentforce AI Agent API. It runs on gateway infrastructure you already own, with no net-new components.
- Honest Agent Cards: The bridge auto-generates an A2A Agent Card that reflects actual platform capabilities so A2A clients never need custom logic and unsupported features return correct error codes.
- Guided setup and lifecycle management: Configure the bridge and deploy your first A2A instance in one step, customize the advertised card and skills, and manage versioned card updates across instances, all from the Agent Fabric UI.
- Enterprise-grade authentication: OAuth 2.0 upstream authentication to Agentforce with on-behalf-of (OBO) support, plus configurable inbound authentication for agents calling the bridge.
What’s Next
The Agentforce bridge is the first of a family. Next up: the Microsoft Copilot Studio A2A Bridge, expected in Q3. Our bridge will bring Copilot Studio agents into the same governed, orchestration layer as your Agentforce and other A2A agents, and bring the vision of every enterprise agent speaking A2A one platform closer.
Ready to orchestrate the agents you already have? Talk to your MuleSoft account team about enabling the A2A Bridge in your Agent Fabric environment.
