The Salesforce Connector
By the end of this lesson, you'll be able to:
- Describe what the Salesforce connector lets a Mule flow do
- Configure a basic Salesforce connector operation
Prerequisites: Mule Flow Building Blocks
What the connector provides
Instead of hand-writing REST or SOAP callouts to Salesforce from scratch, the Salesforce connector exposes common operations — SOQL query, create/update/upsert records, subscribe to Platform Events or Change Data Capture — as ready-made flow steps, handling authentication and API versioning for you.
Connector configuration
A Salesforce connector configuration (username/password/token, or OAuth) is defined once and referenced (config-ref) by every flow step that needs it — centralizing credentials the same way a Named Credential does on the Salesforce side.
A shared connector config, reused by a flow step
<salesforce:config name="Salesforce_Config">
<salesforce:basic-connection username="${sf.username}" password="${sf.password}" securityToken="${sf.token}"/>
</salesforce:config>
<flow name="create-contact-flow">
<http:listener path="/contacts" config-ref="HTTP_Listener_config"/>
<salesforce:create config-ref="Salesforce_Config" type="Contact"/>
</flow>The Salesforce_Config block authenticates once; the create operation in the flow reuses it via config-ref, needing no credentials of its own.
Exercise
In a comment, explain what config-ref accomplishes when used across multiple Salesforce connector operations in different flows.
Show hint
Think about how many times authentication actually needs to be defined.
The Salesforce Connector — Quick Check
My Notes
Log in to keep private notes on this lesson.
Questions about this lesson
No questions yet — be the first to ask.
Log in to ask a question about this lesson.
Summary
The Salesforce connector is a pre-built Anypoint connector exposing Salesforce operations — query, create, update, upsert, and more — as drag-and-drop flow steps, authenticated once via a shared connector configuration rather than per-flow.