July 13, 2026
To set up the MuleSoft Salesforce Connector, add it from Anypoint Exchange to your Mule project, create a global Salesforce configuration, choose an authentication method, test the connection, and add a Salesforce operation to your flow. That's the whole setup in five steps. Once connected, your Mule application can query, create, update, upsert, and delete Salesforce records as part of any integration between Salesforce and the rest of your systems.
This guide walks through each step in Anypoint Studio, plus the connector's operations, OAuth 2.0 authentication, where to find the documentation and version details, and the errors that trip people up.
The MuleSoft Salesforce Connector is an Anypoint Connector that lets a Mule application connect to Salesforce and run operations against its API - querying, creating, updating, upserting, and deleting records, and subscribing to events. It's the bridge that puts Salesforce inside a MuleSoft integration flow.
Because Salesforce owns MuleSoft, the connector is a first-party, well-maintained one, available on Anypoint Exchange. You add it to a Mule project, point it at your Salesforce org with credentials, and then call Salesforce operations wherever you need them - pulling accounts into an ERP, pushing orders back, or syncing data across systems. Whenever people talk about MuleSoft and Salesforce working together, this connector is usually what's doing the work.
Line these up before you open Anypoint Studio, and the setup goes smoothly:
This walkthrough uses Anypoint Studio. Follow the steps in order; the connection configuration in Step 3 is the part worth slowing down for.
In Anypoint Studio, create a new Mule project (or open an existing one). Start with a simple flow - an HTTP Listener or a Scheduler - that will trigger the Salesforce operation you're about to add.
In the Mule Palette, click Search in Exchange, look up "Salesforce," and add the Salesforce Connector to your project. Anypoint Exchange is MuleSoft's marketplace of connectors and templates, and the Salesforce Connector is one of its most-used. Studio adds the dependency to your project automatically.
Drag a Salesforce operation (for example, Query) into your flow, then click the green plus to create a Salesforce Config global element. This is where the connection lives. Choose your connection type - Basic Authentication is the quickest to test; OAuth 2.0 or a Connected App is better for production.
For Basic Authentication, enter the integration user's username, password, and security token, and set the correct Salesforce URL (production or sandbox). Click Test Connection - a green success message means the connector reached your org. If it fails, the credentials or security token are almost always the cause.
With the connection working, configure the operation itself. For a Query, enter a SOQL statement like SELECT Id, Name FROM Account. For Create or Upsert, specify the object (such as Account or Contact) and the records to write. Each operation has its own fields in the connector.
Add a Transform Message component to shape data between systems using DataWeave, MuleSoft's mapping language. This converts an incoming payload into the fields Salesforce expects, or reshapes Salesforce results for the next system in the flow.
Run the project in Studio and trigger the flow. Confirm records move correctly and check the console for errors. Once it's clean, deploy the Mule application to CloudHub or your Anypoint Runtime, and set up monitoring so failures surface early. Getting this deployment and monitoring right is core to our Salesforce integration and DevOps practice.
The MuleSoft Salesforce Connector supports the full set of data operations - create, retrieve, update, upsert, delete, and query - plus bulk jobs, Apex REST calls, and event subscriptions. Knowing which operation fits your use case keeps flows simple and API-efficient.
For record-by-record work, use the standard operations. For anything over a few thousand records, switch to the bulk operations to stay inside API limits.
The Salesforce Connector supports several authentication methods. The right one depends on whether you're testing or shipping to production.
For production, OAuth 2.0 JWT Bearer is the standard because it avoids storing a password. The setup is short:
This is the pattern most enterprises standardize on because it's secure and avoids password-rotation headaches.
The official MuleSoft Salesforce Connector documentation, version history, and release notes live on the MuleSoft documentation site and on the connector's Anypoint Exchange listing. That's where you'll find the operations reference, configuration details, and every change between releases.
Three things worth doing before and during a build:
Match your connector version to your Mule runtime version, and confirm both against the release notes when you upgrade either one.
Most setup issues come from a short list of causes. Here's how to clear them fast.
For deeper platform detail, the Salesforce Developer blog and Salesforce Admins resources cover API limits and Connected Apps, and Apex Hours and Salesforce Ben have practical MuleSoft walkthroughs.
MuleSoft is powerful, and it's not the answer to every integration. Use this quick test.
Reach for a MuleSoft Salesforce integration when you're connecting many systems (an API-led, hub-and-spoke architecture), orchestrating complex multi-step flows, transforming data between very different schemas, or you already run Anypoint Platform across the business. A salesforce integration with MuleSoft pays off most when reusability and governance matter.
Skip it when you just need one simple point-to-point connection - a single REST callout or the native connector often does the job for less cost and effort. MuleSoft earns its licensing when integration is a program, not a one-off.
Yes. Salesforce acquired MuleSoft in 2018, so MuleSoft's Anypoint Platform and the Salesforce Connector are part of the Salesforce family. That's why the connector is a well-supported, first-party integration option.
MuleSoft connects Salesforce to other systems - ERPs, databases, and SaaS apps - through APIs, so data flows automatically between them. Teams use it to unify customer data, orchestrate multi-system processes, and build reusable APIs across the business.
Add the Salesforce Connector from Anypoint Exchange to a Mule project, create a Salesforce Config global element, enter your credentials (or set up OAuth 2.0), test the connection, then add operations like Query or Create to your flow.
Yes - "SFDC" is shorthand for Salesforce, so the MuleSoft SFDC connector and the MuleSoft Salesforce Connector are the same Anypoint Connector. Some people just abbreviate the name.
Create, retrieve, update, upsert, delete, and query, plus bulk jobs, Invoke Apex REST, and event subscriptions to Platform Events and Change Data Capture. Use standard operations for record-level work and bulk operations for high volumes.
The connector itself is free from Anypoint Exchange, but it runs on the Anypoint Platform, which is licensed. You'll also need a Salesforce edition with API access. Budget for the platform, not the connector.
The MuleSoft Salesforce Connector is straightforward to set up once you know the flow - add it from Anypoint Exchange, configure the connection, pick the right operation, secure it with OAuth 2.0, and wire it into your Mule application. The harder part is designing a salesforce MuleSoft integration that stays reliable and reusable as you connect more systems, which is exactly where a specialist partner helps.
That's what we do at Minuscule Technologies. As a trusted Salesforce engineering partner with 160+ specialists and 75+ projects delivered since 2014, we design and build Salesforce integrations and MuleSoft-based architectures for enterprises - including Nasdaq-listed firms - connecting Salesforce to ERPs, data warehouses, and operational systems. From a first connector setup to an API-led integration program, we scope it, build it, and manage it long term.
Ready to connect Salesforce to the rest of your stack with MuleSoft? Talk to Minuscule Technologies and let's design it right.
You've seen what's possible. Now, let's make it happen for your business. Whether you need an end-to-end Salesforce solution, a complex integration, or ongoing managed services, our team is ready to deliver.
Schedule a Free Strategic Call
