Module 4 — Salesforce Connector

All Interview Q&A 76 Cheat sheets 17 Code 278

This module is where MuleSoft stops being abstract and becomes:

“How exactly does my Mule application talk to Salesforce?”

The current Salesforce Connector 12.0 supports Salesforce SOAP, REST, Bulk, and Streaming APIs depending on the operation, while handling HTTPS setup, headers, and much of the protocol plumbing for you.

For your interview, you should be comfortable with these operations:

Query
Query All

Create
Update
Upsert
Delete

Bulk API / Bulk API v2

+ event/pub-sub patterns

Let's work through them as a developer would.

4.1The Salesforce Connector's jobWithout a connector, you would have to write something conceptually like:44 words 4.2codeConnector configurationIndividual Salesforce operations normally point to a reusable global configuration:21 words 4.3●Authentication: what you should know in 2026This is worth knowing because the current connector changed very recently.163 words 4.4codeQUERYThis is probably the Salesforce operation you'll use most besides Upsert.48 words 4.5codeWhat Query returnsSuppose Salesforce contains:66 words 4.6QUERY ALLThere is also:78 words 4.7codeCREATESuppose you're creating a Contact:29 words 4.8codeUPDATEUpdate means:19 words 4.9codeUPSERT — probably your favorite operationSuppose upstream gives us:45 words 4.10Upsert and idempotencyHere's why this matters enormously.70 words 4.11External IDDo not confuse:46 words 4.12DELETEDelete is straightforward conceptually.36 words 4.13Salesforce deletes aren't necessarily permanentSalesforce has its own deletion/recycle-bin semantics.32 words 4.14Target Variable — useful Mule trickRemember in Module 2 we said Salesforce changes the payload.61 words 4.15●Why this is better than endless Set VariableEarlier we did:61 words 4.16codeParent → child creationLet's revisit:11 words 4.17codeSalesforce operations usually handle collectionsA major performance mistake would be:30 words 4.18But “just send everything” isn't good eitherSuppose:10 words 4.19Normal API versus Bulk APIThink of it this way:46 words 4.20Bulk API V2 mental modelSay we need to synchronize:18 words 4.21Bulk processing introduces partial failuresSuppose:23 words 4.22Salesforce errorsThe connector exposes typed Salesforce/Mule errors.24 words 4.23Retryable versus non-retryableThis is an excellent interview topic.34 words 4.24Retry + idempotency belong togetherThis is crucial.63 words 4.25Salesforce limitsSalesforce isn't an unlimited database sitting behind Mule.63 words 4.26This is why query-before-upsert may be wastefulBad pattern:26 words 4.27When Query first still makes senseSuppose requirements say:29 words 4.28Don't confuse Salesforce API with SOQLImportant conceptual distinction:21 words 4.29Mule's Salesforce Connector isn't always RESTAnother interview trap.47 words 4.30Event-driven Salesforce integrationNot every integration is:27 words 4.31codeA realistic developer flowRequirement:35 words 4.32What would you automate as a tester?This is where you can connect your existing expertise directly.30 words 4.33Q&ALikely interview questionAnswer:226 words 4.34cheat sheetYour Salesforce Connector cheat sheetAnd this relationship:60 words •Next — Module 5: Salesforce data model + SOQLThis one should be quite practical. We'll cover Account, Contact, Opportunity, Case, standard vs custom objects/fields, Salesforce IDs…65 words