Boomi technical guide
Everything an engineer needs to connect Boomi to Salesforce: architecture, the exact build steps with real code, field mapping, the data model, security, monitoring, and the pitfalls we design out.
Boomi integration touchpoints with Salesforce. We have shipped it across 2 client projects and 2 build tasks.
The value is governed, monitored integration that scales, with reusable connectors, transforms, and retries instead of brittle point-to-point scripts.
We use Boomi as governed middleware: Salesforce and your other systems connected once, mappings and transforms kept in one place, and scheduled flows with retries and monitoring.
Every Boomi build is delivered by a senior Salesforce architect on a fixed price, tested end to end in a sandbox, deployed to your org, and backed by 30 days of hypercare. You own the result: documented, source-controlled, and free of black-box middleware lock-in.
How Boomi connects to Salesforce
The real connection surface: how it authenticates, what it is built on, the endpoints and events in play, and where the reference docs live.
- Connects via
- Boomi Integration (AtomSphere) Salesforce connector (SOAP-based CRUD) running on an Atom/Molecule/Atom CloudA separate Salesforce REST connector for the REST APIA Salesforce Platform Events connector for event subscribe/publish
- Package
- Custom build (no managed package)
- Authentication
- OAuth 2.0 (browser-based) or username/password (+ security token); the user must have the API Enabled permission
- API type
- SOAP/XML
OAuth/login via https://login.salesforce.com; SOAP operations against /services/Soap/u/{version}- Reference
- Official developer docs
Key endpoints
Query, Create, Update, Upsert, Delete, Get Updated/Deleted (SOAP)Salesforce REST connector CRUD operationsSalesforce Platform Events: Listen (subscribe) and Send (publish)Webhook and platform events
Salesforce Platform Events subscription (with replay)Streaming (CometD/Bayeux) via the Platform Events connectionBuild this with AI agents
Copy the full playbook as a prompt for any coding agent, or install it as a Claude Code skill. Either way your agent builds with our exact approach: the architecture, the Apex code, the field mapping, the rate limits, and the pitfalls to design out. Free, no signup.
Loading the Boomi playbook...What we build for a Boomi integration
Boomi integration touchpoints with Salesforce.
Boomi connectivity
Set up Boomi integration touchpoints with Salesforce for data movement between systems.
Real components we ship
What you will need
What we confirm on both sides before writing a line of code.
From trigger to record, end to end
The production runtime flow, with what happens in each system.
- 01
Systems connected
In BoomiBoomi connects Salesforce to the target systems with managed connectors.
$The Salesforce connector uses a Connected App and OAuth; targets use their own credentials. - 02
Data transformed
In BoomiMappings and transforms shape each payload to a canonical model.
$DataWeave (MuleSoft) or recipe steps normalize the data before it moves. - 03
Flow orchestrated
In BoomiScheduled or event-driven flows move the data with retries.
$Records are batched in chunks; a dead-letter queue captures anything that fails. - 04
Delivered to Salesforce
In SalesforceRecords land in Salesforce, monitored end to end.
$Upserted on external ids, with the whole flow observable in the iPaaS console.
How the data actually flows
Left to right: sources, the integration layer, Salesforce, and the outcomes it drives.
// sources feed the integration layer, Salesforce persists, outcomes ship
The objects behind the integration
The Salesforce objects we read and write, what each one is for, and the fields that carry the load.
| Object | Purpose | Key fields |
|---|---|---|
record | The primary Salesforce record Boomi data maps onto. | External_Id__c, Name, Status |
Account | Matched or created for the customer or company behind the record. | Name, External_Id__c |
Error_Log__c (custom) | Captures every request, response, and failure so anything can be replayed. | Payload__c, Status__c, Related_Id__c |
Salesforce objects typically in play for Boomi
Build the Boomi integration
Every step we follow to ship a production-grade build, with the code that matters.
Plan the integration and prerequisites
We line up both systems and the platform first.
- API access on Salesforce and your other systems, plus the Boomi environment and connectors
- The objects, direction, sync pattern, and success criteria agreed up front
Connect Salesforce to Boomi
We wire up the Salesforce connector securely.
- Configure the Salesforce connector with a Connected App and OAuth, or JWT for a headless flow
- Give the connector a dedicated least-privilege integration user
Connect the target systems
We bring the other endpoints into the platform.
- Configure each target connector with its own secure credentials
Design a canonical data model
We map everything to one shared shape, not point to point.
- Define a canonical model so each system maps to and from one schema, which scales as systems are added
Build the transforms
We keep all the mapping logic in one governed place.
- Build the Boomi flows or recipes that move each record
- Map and transform payloads (for example, DataWeave on MuleSoft) to and from the canonical model
%dw 2.0
output application/json
---
payload map (row) -> {
External_Id__c: row.id,
AccountId: row.customerId,
Amount__c: row.total,
Status__c: upper(row.state)
}Choose the sync pattern
We pick real-time or batch per use case.
- Real-time via Platform Events or Change Data Capture, or scheduled batch with an updatedSince filter
// Real-time: Salesforce publishes a Platform Event, the iPaaS subscribes
trigger OrderEventTrigger on Order_Event__e (after insert) {
List<Sync_Task__c> tasks = new List<Sync_Task__c>();
for (Order_Event__e ev : Trigger.new) {
tasks.add(new Sync_Task__c(Order_Id__c = ev.Order_Id__c, Status__c = 'Queued'));
}
insert tasks;
}Add error handling and retries
We make it reliable at volume.
- Batch records in chunks, add retries with backoff, and route failures to a dead-letter queue
// Scheduled delta pull: only records changed since the last successful run
global class DeltaPullScheduler implements Schedulable {
global void execute(SchedulableContext ctx) {
Datetime since = IntegrationConfig.lastSync();
ExternalService.pullUpdatedSince(since); // the iPaaS flow filters by updatedSince
IntegrationConfig.setLastSync(System.now()); // watermark for the next run
}
}Pro tip: build for retries
At volume, transient failures are normal. Batch in chunks and add retries with a dead-letter queue, so a blip never means lost data.
Test in a sandbox environment
We validate before production.
- Run representative loads end to end and confirm both sides reconcile
Deploy with CI and monitor
We ship it and keep it observable.
- Promote Boomi artifacts through environments with CI, and monitor the flows with alerting plus 30 days of support
Example field mapping
How Boomi data lands on your Salesforce records. We tailor the full mapping to your org.
| Boomi | Salesforce | Notes |
|---|---|---|
| Boomi email | record.Email | Match key |
| Boomi name | record.Name | |
| Boomi company | record.Company | Required on Lead |
| Boomi record id | record.External_Id__c | Unique external id, upsert key |
| Boomi status | record.Status | Picklist value mapping |
| Created / updated at | LastModifiedDate | Enables delta sync and audit |
| Owner or rep | record.OwnerId | Assignment rules or a default owner |
Rate limits and governor limits
The platform constraints we design around, so the integration stays fast and never falls over at scale.
Specific to Boomi
Salesforce platform limits
Secure by design
How we keep the integration safe, least-privilege, and compliant.
Monitoring, retries, and reliability
What keeps the integration trustworthy in production, and how you know the moment something needs attention.
How we test, deploy, and hand it over
The quality gates every build clears before it touches your production org.
Common pitfalls we design out
The mistakes that quietly break integrations, and how we avoid each one.
Point-to-point sprawl
Map every system through one canonical model instead of pairwise connections.
Silent failures at volume
Add retries with backoff and a dead-letter queue with alerting.
Schema drift breaks the flow
Version the transforms and validate payloads against a contract.
No visibility when it breaks
We log every call and surface failures on a dashboard with alerts, so an issue never goes unnoticed.
Reporting drifts from reality
External-id keys and a delta timestamp keep Salesforce and the source reconciled, so reports stay trustworthy.
Gotchas specific to Boomi
Boomi integration: technical FAQs
How do you authenticate Boomi with Salesforce?
We connect Boomi using secure named credentials and store every secret in Salesforce Named Credentials with a permission set, so nothing is hard-coded or shipped in metadata.
Does the Boomi integration handle bulk volume?
Yes. All Apex is bulkified, volume moves to Queueable or Batch Apex, and we respect the Salesforce governor limits (SOQL, DML, and callout caps per transaction).
How do you prevent duplicate records?
We upsert on a unique external-id field, so a retried or duplicate payload is idempotent and never creates a second record.
How is the integration tested and deployed?
Apex tests with HttpCalloutMock cover the success, failure, and a 200-record bulk case (75 percent plus coverage). We deploy via change sets or an SFDX and CI pipeline.
What happens if Boomi or Salesforce is briefly down?
Failed calls retry with backoff and land in an Error Log object with alerting, so nothing is lost and any event can be replayed.
Real-time or batch sync?
Either. We use Platform Events or Change Data Capture for real-time, or a scheduled batch with an updatedSince delta filter for high volume.
Want us to build your Boomi integration?
Skip the build. In a free 30-minute call we will map your Boomi flow and hand you a clear, fixed-price plan.