MuleSoft: What it is and how to integrate it in 2026

MuleSoft is Salesforce's integration platform: an iPaaS that connects CRM to ERPs, databases, legacy systems, cloud applications and, since 2025, AI agents, through reusable and governed APIs. In 2026, it changed on three fronts that matter to whoever decides: it gained a published entry price, with packages starting at US$2,000 per month and a single consumption currency, Mule Credits; transformed the company's AI agent control plan with Agent Fabric, which on October 27 received continuous agent evaluation and spending cap; and was recognized for the 11th time in a row as a leader in the Gartner Magic Quadrant for API Management.

For enterprise operations, integration is no longer a technical detail. The more systems, and now more agents, a company adopts, the more integration and governance define whether the technology delivers results or becomes chaos. This guide explains what MuleSoft is, what iPaaS is, what makes up the Anypoint Platform, how it connects to Salesforce, what the new model costs, what Agent Fabric does in 2026 and how to adopt it securely. WeeNow is an official Salesforce partner focused on designing and supporting integration architecture for Salesforce users.

What is MuleSoft?

MuleSoft is Salesforce's API and AI integration, automation, and management platform. Founded in 2006 and acquired by Salesforce in 2018, it connects applications, data, legacy systems and AI agents through reusable APIs, in hybrid and multi-cloud environments, with governance and observability in one place.

In practice, MuleSoft connects practically anything: ERPs such as SAP and TOTVS, databases, mainframes and legacy systems, SaaS applications, files, EDI partners and devices. The objective is to make information flow without rewriting systems from scratch, keeping the legacy communicating with the new within an organized architecture. The problem it solves is well known: according to the official Salesforce Brazil page, the average company has data in silos across more than a thousand applications, and only a third of this data is integrated.

The portfolio is organized into three pillars. Integration, with Anypoint Platform and connectors. Automation, with Composer, RPA and intelligent document processing (IDP). API Management and AI, with API Manager, Flex Gateway, Omni Gateway and, since 2025, Agent Fabric. In 2026, Salesforce itself started to present the set as “MuleSoft for the agentic company”: the same base that integrated systems now discovers, connects, governs and optimizes AI agents.

What is iPaaS and why does it matter?

iPaaS is the acronym for integration platform as a service. It is the category of software that integrates cloud applications with each other and with legacy and on-premises systems, delivered as a service, with ready-made connectors, a central integration mechanism, monitoring, security and elastic scaling. MuleSoft pioneered it with CloudHub, the cloud component of Anypoint Platform, and the official definition of the platform today is exactly that: a unified iPaaS and full API lifecycle management solution.

The reason the term matters to the IT manager is practical. Point-to-point integration, made on demand for each project, generates the so-called spaghetti architecture: dozens of fragile, ownerless connections that break when a system changes. An iPaaS exchanges this for a single layer, with catalog, standards and observability, in which each new integration reuses what already exists. This is what allows us to talk about integration governance, and not just integration.

How does MuleSoft connect to Salesforce?

The connection takes place via ready-made APIs and connectors. MuleSoft offers native connectors to Salesforce and neighboring clouds, which speeds reading, adding, and updating data between CRM and other systems, securely and in real time. From within the Salesforce instance itself, you can invoke MuleSoft APIs and flows and Agentforce agents. There are three paths, depending on the maturity and complexity of the project:

• Salesforce Flow and native connectors: for automation within the platform and simple integrations with systems that already have a connector. O Flow Builder received the biggest update in years in Winter '27, and Salesforce started listing it in the MuleSoft automation portfolio.
• MuleSoft Composer: no-code tool for administrators and business teams to create integrations between Salesforce and other applications without programming.
• Anypoint Platform: the complete environment, for complex integrations, with governance, monitoring and scale.

The most visible result is the 360 view of the customer: data that was previously trapped in isolated systems appears unified within Salesforce, which improves service, sales and personalization. And, with the Data 360, this unification gained its own data layer, which MuleSoft feeds.

Anypoint Platform: what's inside

The Anypoint Platform is the heart of MuleSoft: a single platform for designing, publishing, running, managing, and governing APIs and integrations, in the cloud or on-premises. The components that the IT manager will find in the budget and project:

Component	Purpose
Anypoint Code Builder	Next-generation IDE for designing, developing, and deploying APIs, integrations, and automations, with natural language-assisted generation; Anypoint Studio continues as a classic IDE
Anypoint Connectors	Ready connectors for enterprise applications, databases, protocols and industry standards
Anypoint Exchange	Catalog of connectors, templates, examples, MCP servers and reusable agents
CloudHub and Runtime Manager	Execution and monitoring of integrations, with performance and health visibility
API Manager	Manage, secure, and analyze APIs and microservices in one place, wherever they are deployed
API Governance	Ensure APIs follow security standards and policies by design
Flex Gateway and Omni Gateway	Gateways for APIs in any environment; Omni Gateway extends control to language models, MCP servers, and agent-to-agent traffic
Experience Hub API	Unified portal and showcase of the company's APIs, with ready-made templates
Partner Manager	Partner integration via API and EDI
DataWeave	Data transformation language used across the platform
Composer, RPA and IDP	No-code automation, process robots and document data extraction

This structure is what allows you to reuse integrations, standardize processes and reduce the time for each new project. Salesforce cites, based on an Omdia value assessment, a 49% reuse rate of integrations and APIs and a 74% reduction in maintenance effort among evaluated customers; It is worth reading as an order of magnitude, not as a guarantee.

What is API-led connectivity?

API-led connectivity is the approach that MuleSoft is known for. Instead of creating a point-to-point integration for each pair of systems, the company exposes each functionality or data source as a well-defined, reusable API. A “client” API, created once, powers the website, app, Salesforce, and financial reporting, without anyone redoing the integration for each project.

The model organises these APIs into three layers, from data to channel:

• System APIs: expose data from core systems such as ERP, databases, and Salesforce itself.
• Process APIs: combine and orchestrate data from multiple systems within a business process.
• Experience APIs: deliver this data in the right format for each channel, be it an app, a website, CRM or, now, an agent.

Separating the layers is what allows you to change a source system without breaking the one above, and reuse the same base in different projects. In 2026, this architecture gained a new use: Agent Fabric's MCP Bridge transforms existing APIs into MCP tools, so that AI agents can use what the company has already built without rewriting integrations. Whoever designed the layers correctly is one step away from giving agents governed tools.

How much does MuleSoft cost?

Until 2026 the answer was “under consultation”. In September 2026, MuleSoft published a new model, and it changes the budget conversation:

Item	How it works
Entry price	Packages from $2,000 per month, billed annually, with access to core capabilities and an allocation of Mule Credits
Mule Credits	Single consumption currency for integration, API management, automation and agents; each type of use has a credit rate, which drops as the volume grows, with up to 90% reduction in the highest bands
Packages by use case	Govern APIs and AI (70 million or more API and template calls per year), manage agents (180 million or more agent actions per year), connect applications (40 million or more records moved per year), process documents and the entire suite (340 million or more calls between apps, APIs, and agents per year)
Purchase methods	Pre-purchase (block of credits upfront, lowest rate per credit, no minimum), pre-commitment (annual commitment of at least US$50,000, paid monthly, single pool between teams) and unlimited (customized fixed price with unlimited credits and complete portfolio)
Surplus and follow-up	It is possible to purchase additional credits when consumption exceeds allocation; the consumption panel shows credits used, remaining and projected until renewal, by capacity, application, team, environment or cost center, with alerts by limit
Technical	30 days free with full portfolio, no credit card

The values are reference, in dollars, and the exact composition of each package depends on negotiation. For the IT manager, three consequences. The first: MuleSoft left the “only for those with a budget of millions” category and started competing in the entry-level iPaaS category. The second: as credits are shared between integration, APIs, automation and agents, sizing the contract requires estimating the four consumptions together, and not just the number of integrations. The third: the surplus is not penalized, but it is not free either; Without a limit alert, the agent count grows silently. To plan your total investment in Salesforce, see the how much Salesforce costs.

When does it make sense to use MuleSoft?

Not every integration needs MuleSoft. To connect two tools with a native Salesforce connector, or for specific automation, Flow and connectors do the trick. MuleSoft pays off when complexity grows:

Scenario	Best path
Automation within Salesforce or integration with a system that already has a native connector	Salesforce Flow and native connectors
Simple integration between CRM and a SaaS application, run by the business team	MuleSoft Composer
Many systems, legacy and cloud, real-time data, multiple teams consuming the same APIs	Anypoint Platform with API-led connectivity
Regulated sector, requiring auditing, access control and API standards	Anypoint Platform with API Manager and API Governance
Multiple AI agents, on more than one platform, that need to act on the company's systems	Agent Fabric on Anypoint Platform

The rule of thumb: if the question is “how do I connect A to B”, Flow or Composer are enough; If the question is “how do I make thirty systems and ten agents talk to each other without losing control”, it’s MuleSoft. For a large operation, with governance requirements, it is usually worth the investment. For simple cases, it makes sense to start small and migrate when the complexity warrants.

What MuleSoft Agent Fabric does in 2026

MuleSoft's role has grown with AI agents. As companies adopt Agentforce and agents from other platforms, a new problem arises: scattered agents, created by different teams, without orchestration or governance. The 2026 Connectivity Benchmarking Report, with more than 1,050 IT leaders, projects a a 67% increase in AI-agent adoption by 2027, with companies moving from an average of 12 to around 20 agents.

The Agent Fabric, launching in 2025, is the answer: a control plane to discover, govern, orchestrate, and observe any agent, AI asset, and agentic flow, built on the Anypoint Platform. In general availability, with new capabilities every month, it is organized into five fronts:

• Action on systems: MCP and A2A support to make any API and any agent usable in agent flows, AI connectors, IDP, RPA, and Partner Manager for legacy, unstructured, and partner data.
• Finding: the Agent Registry is the single catalog of MCP agents, APIs, and tools, with a curated list of public MCP servers; Agent Scanners automatically find and register agents and MCP servers across Amazon Bedrock and AgentCore, Google Vertex AI, Microsoft, Claude, Databricks, Kong, and ServiceNow.
• Orchestration: Agent Broker routes work between agents and tools from different ecosystems, with guided determinism inherited from Agentforce's Agent Script, and full support for version 1.0 of the A2A protocol, with transcoding between versions for mixed fleets.
• Governance: Omni Gateway is the single point of control for cost, usage, security and compliance over agents, MCP servers and over 140 language models; Trusted Agent Identity guarantees that the agent acts with the user's identity and authorization; and the Agent Kill Switch stops an agent in production.
• Note: Agent Visualizer shows the map of the agent network, with trust scores, bottlenecks and risk of hallucination.

On October 27, 2026, Salesforce announced the expansion it needed to operate at scale: the Agent Evals generates tests before deployment and evaluates agents, models and MCP servers in production against quality thresholds, triggering predefined interventions, including Kill Switch, when the result drops (beta November 2026, general availability January 2027); the API Evals generates functional and performance tests from the API specification and catches changes that break the agent before they reach production; the Custom Agent Scanner extends discovery to indoor environments and platforms outside the standard list; the Open Policies Apply one-time policy on Azure, Apigee, and Kong gateways; and cost controls, with FinOps Dashboard, Model Wallet, which blocks over-budget requests, and optimization policies that, in Salesforce tests, cut up to 75% of token consumption, are now generally available. According to Salesforce, Agent Fabric processes more than 1.2 billion requests per day.

Two MuleSoft publications complete the picture for the technical team. On September 3, the team detailed token cost-cutting policies in AI Gateway: intelligent response clipping, progressive tool discovery, and compression of repeated structures in TOON format, with an example of a tool response shortened from 38,693 to 928 characters. On November 3, Omni Gateway policies for agent-to-agent traffic arrived: Azure and AWS guardrails applied to A2A calls, behavior tracking that detects an agent going out of scope, masking of personal data in transit, and full support for A2A 1.0. For those who operate Salesforce, this speaks directly to the governance of the MCP in Salesforce and the Winter ‘27 MCP Server Risk Score.

Without this layer, it is common for so-called shadow AI to emerge: agents created in isolation by different teams, without central visibility, which duplicate work and open loopholes. Agent Fabric attacks precisely this: MuleSoft becomes the system of record for how agents are discovered, routed, governed and paid.

MuleSoft enterprise use cases with Salesforce

The applications are wide. The most common in large operations:

• Legacy integration: connect legacy systems to Salesforce without replacing them, exposing data and functions through controlled APIs.
• ERP and CRM in the same conversation: order, invoicing, inventory and credit from the ERP visible in Salesforce, and opportunities and contracts from the CRM going back to the ERP, without double entry.
• Financial automation: receive bank or accounting data and trigger reconciliation, invoicing, or collection flows in CRM.
• Retail and omnichannel: unite inventory, e-commerce and after-sales for a consistent experience across all channels, including WhatsApp integrated with CRM.
• Energy, industry and IoT: connect sensors, work orders and real-time monitoring dashboards.
• Customer 360 view: consolidate history, payments, and interactions from multiple systems into a single timeline within Salesforce.
• Agents with access to systems: expose existing APIs as MCP tools for agents from Agentforce, Claude, or other platforms to query and act on enterprise systems under gateway policies.

A concrete scenario: a retail operation with a physical store, e-commerce and an inventory ERP. MuleSoft connects all three sources to Salesforce. When a customer purchases on the website, stock is updated in real time, customer service sees the complete history and marketing triggers the right offer. In 2026, the same design takes a further step: the service agent consults the order API through the MCP Bridge and resolves the change of address without anyone opening the ERP.

How does MuleSoft handle legacy systems?

Legacy is often the biggest fear in integration projects. MuleSoft solves this dilemma with connectors to legacy databases and protocols and by wrapping legacy logic in modern APIs. A typical path:

1. Evaluate current systems and map integration points and owners of each data.
2. Identify the critical processes that already exist and what cannot be stopped.
3. Build System APIs to expose data and functions in a controlled way, without changing the source system.
4. Continuously monitor performance and security and retire deprecated point-to-point integrations.

Thus, the legacy stops being an obstacle and becomes more of a connected source, without risky migration all at once. The API management in Salesforce and the choice between Bulk API and SOAP continue to apply on the CRM side.

Governance and security of APIs and agents

Scaling integrations without governance is where many projects break down. Anypoint Platform centralizes monitoring, authentication, access control, and usage history for each API, and Omni Gateway extends the same control to models, MCP servers, and agents. This is especially important in regulated sectors such as finance and healthcare, where every access needs to be auditable. Good practices that sustain growth:

• Manage the lifecycle of every API, from creation to retirement.
• Apply security policies and standards consistently, the role of API Governance.
• Treat personal data in accordance with the LGPD, with encryption, access control and, in agent traffic, masking of personal data in transit.
• Reuse APIs from the catalog instead of recreating integrations for every project.
• Give each agent their own identity and authorization, and maintain a stop button.
• Measure the consumption of credits and tokens per team and per use case, with a ceiling defined before the agent goes into production.

Both MuleSoft and Salesforce feature native security controls, but real protection depends on a well-designed architecture from the start. The data governance in Salesforce is the other half of this work.

What does the IT manager decide before hiring

1. What questions does the project answer. Where essential data is, which systems need to talk and with what priority. Without this list, the credit budget will not be finalized.
2. Flow, Composer or Anypoint. According to the scenario table above. Making more mistakes costs money; going wrong costs a project redone in a year.
3. Scaling in Mule Credits. Estimate the four consumptions together (integration, APIs, automation and agents), choose between pre-purchase, pre-commitment and unlimited, and define limit alerts.
4. Owner of the APIs. Who publishes, who approves changes, who retires. API without owner becomes point-to-point integration with another name.
5. Agents in scope from the start. If the company is going to use Agentforce or third-party agents, the Agent Registry and gateway policies are included in the design of the first phase, not the third.
6. Legacy and personal data. What will be wrapped in the API, what will be replaced and how the LGPD is met in the three layers.
7. Acceptance metric. Delivery time for a new integration, reuse rate, incidents per month and cost per call or agent action.

How to adopt MuleSoft in your company

Adopting MuleSoft with a return is less about buying the tool and more about designing the right architecture. A script that works:

1. Diagnosis (weeks 1 to 3): inventory of systems, existing integrations and agents already in use, including those that no one has registered.
2. Architecture (weeks 4 to 6): design of the API layers, catalog, governance policies and credit consumption model.
3. First wave (weeks 7 to 14): the System APIs of central systems, a business Process API with measurable return and publishing on Exchange.
4. Agents (from week 12): exposure of APIs such as MCP tools, registration of agents in the Agent Registry and cost and security policies at the gateway before the first agent in production.
5. Ongoing support: monitoring, retirement of old integrations and quarterly review of consumption.

This is where WeeNow comes in. As an official Salesforce partner, WeeNow works from assessment through ongoing support: mapping systems, designing APIs, sizing MuleSoft, defining governance and evolving the architecture as the business changes. Explore WeeNow Salesforce consulting and the Salesforce integrations guide.

MuleSoft FAQ

What is MuleSoft?

It is Salesforce's AI and API integration, automation, and management platform, acquired in 2018. Its flagship product is the Anypoint Platform, which connects Salesforce to ERPs, databases, legacy systems, cloud applications, and AI agents through reusable APIs.

What is iPaaS?

It is the integration platform as a service: a cloud layer, with ready-made connectors, integration, monitoring and security mechanism, which integrates cloud applications with each other and with on-premises systems. Anypoint Platform is an iPaaS with complete API lifecycle management.

How much does MuleSoft cost?

As of September 2026, packages start at $2,000 per month, billed annually, with an allocation of Mule Credits, the single consumable currency for integration, APIs, automation, and agents. There are three forms of purchase: pre-purchase, pre-commitment (annual minimum of US$50,000) and unlimited. The values are reference and the composition of the packages is negotiated.

What are Mule Credits?

The consumer unit shared across MuleSoft capabilities. Instead of purchasing separate capacity by product, teams consume from a single pool as they run integrations, manage APIs, automate processes, and use agents. Each type of use has a rate, which drops as the volume grows.

How does MuleSoft integrate with Salesforce?

By native APIs and connectors. Business teams set up no-code integrations with Composer, complex projects use the Anypoint Platform, and from within Salesforce it is possible to invoke APIs and flows from MuleSoft and agents from Agentforce. The objective is to keep the CRM always updated with data from different sources.

What is the difference between Salesforce Flow, MuleSoft Composer and Anypoint Platform?

Flow automates processes within Salesforce and uses native connectors. Composer is MuleSoft's no-code tool for simple integrations between CRM and other applications. The Anypoint Platform is the complete environment for complex integrations, with governance, monitoring and enterprise scale.

What is MuleSoft Agent Fabric?

MuleSoft's AI agent control plane, released in 2025: registers, discovers, orchestrates, governs, and observes agents from Agentforce and other platforms in a single network. In October 2026, Agent Evals, API Evals, Custom Agent Scanner and cost controls with spending caps were added.

What is MCP Bridge?

It is the Agent Fabric capability that exposes existing APIs as MCP tools, so that AI agents use the integrations the company has already built without rewriting them.

Is MuleSoft safe and GDPR compliant?

MuleSoft and Salesforce bring authentication, encryption and access management controls, and integrations can be monitored and audited. In agent traffic, Omni Gateway adds guardrails, agent identity and masking of personal data in transit. Effective security depends on well-designed API governance and architecture.

Does MuleSoft replace Salesforce Flow?

No. Flow remains the automation within the platform, and Salesforce itself lists it in the MuleSoft automation portfolio. MuleSoft comes in when the integration leaves Salesforce and involves multiple systems, API governance, or agents.

Is there a free trial of MuleSoft?

Yes. Anypoint Platform offers 30 days free with the complete portfolio, without a credit card, which serves to validate connectors and a first flow before scaling.

Do I need consultancy to implement MuleSoft?

Not mandatory, but API architecture, credit scaling, and agent governance are where projects win or lose. An official Salesforce partner speeds up diagnosis, avoids peer-to-peer architecture, and scales the contract by actual consumption.

Conclusion

MuleSoft is what allows Salesforce to talk to the rest of the company. With the Anypoint Platform and API-driven connectivity, data previously trapped in silos becomes a single basis for service, sales and decision-making. In 2026, the price published on Mule Credits took the platform out of the “on request” category, and Agent Fabric extended its role into the AI era: integrating, governing and paying agents became as important as integrating systems.

The advantage comes from designing the platform with architecture, governance and a budget that accounts for agents from the start. WeeNow supports that journey from assessment to ongoing support. To turn integration into a real business advantage, talk to a specialist.

Sources

• MuleSoft Pricing, MuleSoft, pricing page published September 14, 2026.
• MuleSoft Agent Fabric, MuleSoft, updated October 28, 2026.
• Salesforce Expands Agent Fabric to Automatically Stop Runaway Costs and AI Agent Failures, Salesforce Newsroom, October 27, 2026.
• Governing Agent Networks in Production with Agent Fabric, MuleSoft Blog, November 3, 2026.
• Cutting Token Costs at the AI Gateway, MuleSoft Blog, September 3, 2026.
• Welcome to Dreamforce 2026: Turning AI Ambition Into Measurable ROI with Agent Fabric, MuleSoft Blog, September 15, 2026.
• Salesforce (MuleSoft) Recognized as a Leader for 11th Time in 2026 Gartner Magic Quadrant for API Management, MuleSoft Blog, October 6, 2026.
• MuleSoft and MuleSoft Anypoint Platform, Salesforce Brazil, product pages updated September 2026.
• iPaaS: cloud integration platform, MuleSoft.
• Salesforce projects 67% increase in adoption of AI agents by 2027, Salesforce Brazil, March 2, 2026.