Salesforce
MuleSoft integration.
How MuleSoft connects to Salesforce through the Anypoint Connector, which Salesforce APIs it uses, and what it leaves out.
A Salesforce MuleSoft integration links Salesforce to other systems through Mule apps on MuleSoft's Anypoint Platform. The Anypoint Connector for Salesforce, version 12.1, lets those apps create, update, upsert and query records, run Bulk API jobs, call Apex, and react when Salesforce records are added, changed or deleted.
How it works
Which Salesforce APIs does the MuleSoft connector use?
MuleSoft says most operations map to the SOAP API. The connector also uses the Bulk API for batches, the Streaming API for change notifications, the Metadata API, and Apex SOAP and REST for custom Apex services. It does not give access to the Chatter or Tooling API.
The connector
Salesforce at the center, MuleSoft in between.
Techila Global Services is a Salesforce Summit Partner. On this kind of project we design the Mule apps, configure the Salesforce Connector and its authentication, map the data, and test volumes against your API limits.
Looking for MuleSoft consulting and delivery? See our MuleSoft services page.
What can the MuleSoft Salesforce Connector do?
| Salesforce API | What the connector uses it for |
|---|---|
| SOAP API | Most connector operations, such as Create, Update, Upsert, Delete, Merge, Convert Lead and Search |
| Bulk API | Loading batches of data, including Bulk API v2 jobs and query jobs |
| Streaming API | Change notifications: Subscribe Topic, Subscribe Streaming Channel and replay listeners |
| Metadata API | Creating, reading, updating, deploying and retrieving metadata |
| Apex SOAP and Apex REST | Calling custom Apex web services |
| Chatter and Tooling API | Not available through the connector |
What moves between Salesforce and a Mule app?
- Create, update, upsert, delete (from Mule app to Salesforce)
- New, modified or deleted objects (from Salesforce to Mule app)
- Query and Bulk API v2 results (from Salesforce to Mule app)
- Platform event messages published (from Mule app to Salesforce)
- Apex REST and SOAP methods called (from Mule app to Salesforce)
Its triggers include On New Object, On Modified Object, On Deleted Object, Replay Channel Listener and Replay Topic Listener.
What do you need to connect MuleSoft to Salesforce?
- Salesforce credentials: MuleSoft lists a Salesforce developer account and a security token, plus a consumer key and secret.
- An authentication type: Basic, OAuth 2.0, OAuth JWT, OAuth Client Credentials or OAuth SAML.
- For OAuth: a namespace and schema location.
- Anypoint Platform: Salesforce offers a 30-day free trial and does not list prices on its MuleSoft page.
Salesforce MuleSoft integration use cases
MuleSoft's Salesforce Connector documentation names four common uses. Each one is a different shape of project:
| Use case | What MuleSoft describes | What it looks like in Salesforce |
|---|---|---|
| ERP integration | Syncing Salesforce with ERP systems such as SAP and NetSuite | Accounts and products from the ERP, orders from won opportunities, invoice status back on the account. See our Salesforce SAP and NetSuite Salesforce guides. |
| Data aggregation | Bringing data together from several Salesforce orgs and databases | One customer view across business units, or reporting that spans orgs without manual exports |
| Legacy modernization and migration | Moving data from older systems into Salesforce | Bulk API jobs for the initial load, then ongoing flows while the old system is retired |
| Customer experience integration | Connecting Salesforce with tools such as ServiceNow and Marketo | Incidents linked to cases, or marketing activity on the lead. See our ServiceNow Salesforce integration guide. |
Our case studies show two of these in practice: St. James's Place kept Sales Cloud and Marketing Cloud in step through MuleSoft, and a leading bank connected Salesforce with MuleSoft. The pattern is the same each time: one integration layer, reusable APIs, and Salesforce as the system of engagement.
Salesforce MuleSoft integration best practices
MuleSoft's own documentation for the Salesforce Connector and Anypoint Monitoring sets out most of these:
- Use the Pub/Sub Connector for new event integrations. MuleSoft says that if you are adding a new connector for platform events and Change Data Capture events, you can use the Salesforce Pub/Sub Connector, which is based on the Pub/Sub API.
- Run event sources on the primary node. MuleSoft says the source must run on the primary node; in non-cluster multi-worker mode it runs on every node and consumes duplicate events.
- Keep one flow per channel. When several flows listen to the same channel or topic, MuleSoft suggests putting that logic in a single flow instead.
- Give flows their own connector configuration. MuleSoft recommends different Salesforce Connector configurations with different Salesforce usernames when flows use different sources, to avoid performance issues. Use dedicated integration users, not personal accounts.
- Persist replay IDs. MuleSoft recommends persisting replay IDs across application restarts so no message is processed twice. Salesforce stores events for 72 hours, or 24 hours for legacy PushTopic and generic events, so an app down longer than that misses events.
- Use Bulk API for volume. The connector uses the Bulk API to load batches of data; reserve record-by-record operations for small, real-time changes.
- Plan API limits. Every connector call counts against your Salesforce API allowance, so size volumes before go-live.
- Monitor from day one. Anypoint Monitoring provides built-in dashboards, alerts, log search and traces; MuleSoft lists custom dashboards, alerts and custom metrics in Integration Advanced rather than Integration Starter.
When does a team need MuleSoft rather than a direct connection?
| Route | Fits when | Trade-off |
|---|---|---|
| A vendor's own Salesforce app | One system, standard objects, a ready-made sync | Limited to what the app maps |
| MuleSoft Anypoint Platform | Several systems, reusable APIs, bulk loads or event-driven flows | A platform to license, build on and run |
| Custom code on Salesforce APIs | One narrow flow you are happy to maintain | Monitoring, retries and changes are yours |
This page covers how the two connect. For the basics, see what MuleSoft is and how API-led connectivity works, and for alternatives, our MuleSoft vs Boomi comparison. For MuleSoft design, build and support, see our MuleSoft services or our wider Salesforce integration services. To scope a project, book a discovery call.
Architecture
How does Salesforce connect to MuleSoft?
Salesforce
Anypoint Connector for Salesforce
Other systems
What's included
What does Techila set up for Salesforce and MuleSoft?
Integration in action
Where this connector is live.
All case studies →FAQ
Frequently asked questions.
What architects ask before commissioning a Techila integration.
Yes. The Anypoint Connector for Salesforce, version 12.1 when we read MuleSoft's docs, lets Mule apps work with Salesforce records, bulk jobs, metadata, events and Apex.
Yes. The connector has On New Object, On Modified Object and On Deleted Object triggers, and replay listeners for streaming channels and topics.
MuleSoft says it does not expose every Salesforce API operation and gives no access to the Chatter or Tooling API.
Salesforce's MuleSoft page does not list prices, but MuleSoft's own pricing page says packages start at $2,000 per month, billed annually, on a credit-based model, with a 30-day free trial. Ask for a quote for your volumes.
MuleSoft's Salesforce Connector documentation names ERP integration with systems such as SAP and NetSuite, data aggregation across orgs and databases, legacy modernization and data migration, and customer experience integrations with tools such as ServiceNow and Marketo.
MuleSoft says that if you are adding a new connector for platform events and Change Data Capture events, you can use the Salesforce Pub/Sub Connector, which is based on the Pub/Sub API. The Salesforce Connector's own replay listeners remain in its 12.1 reference.
No. This page explains how Salesforce and MuleSoft connect. Our MuleSoft services page covers consulting, build and support.
Sources
Last reviewed:
- MuleSoft Documentation, Salesforce Connector 12.1 (read 10 November 2026)
- MuleSoft Documentation, Salesforce Connector reference (read 10 November 2026)
- Salesforce, MuleSoft (read 10 November 2026)
- MuleSoft Documentation, Processing events with Salesforce Connector 12.1 (read 11 November 2026)
- MuleSoft Documentation, Anypoint Monitoring overview (read 11 November 2026)
- MuleSoft, MuleSoft pricing (read 11 November 2026)
Talk to an expert about MuleSoft Salesforce integration
Tell us what you need. We reply within 1 business day.
Let's plan your next Salesforce program.
We reply within 1 business day · +1 617-777-9873
See case studies