Integrations & data
Integration is a core part of our work. We connect Salesforce, mobile apps, websites, messaging and business systems so the right information reaches the right place.
Discuss your project
What we can deliver
Connect CRM, finance, ecommerce and operational systems through supported REST or SOAP APIs, webhooks, events and batch interfaces. Compare direct connections with middleware, including MuleSoft where appropriate, based on transformation needs, traffic, monitoring and who will maintain the interfaces.
Plan field mapping, cleanup, external identifiers and record relationships before migration. Rehearse imports with sample data, reconcile results and agree the cutover and recovery steps before moving live records.
Define one-way or two-way updates and which system wins when values conflict. Plan retries, duplicate prevention and reconciliation so interrupted transfers can recover without overwriting valid changes.
Prepare consistent customer, product, order and activity data for operational reports or a data warehouse. Standardise currencies, time zones and status values, retain useful history, and expose reconciliation results so reporting teams can explain missing or late records.
Use events for time-sensitive changes and scheduled batches for larger transfers. Agree update delays, API limits and how to handle duplicate or out-of-order messages.
Agree identifiers, formats and which system owns each field. Compare source and destination records after migrations or transfers, and make discrepancies traceable.
Limit integration access, protect credentials and verify incoming notifications. Add error alerts and a documented way to replay failed work without creating duplicate records.
Connect document generation, e-signature, document storage and finance or ERP tools to CRM workflows. Keep document versions, signing status and business records aligned using supported connectors or APIs.
Use dedicated integration identities, OAuth or the provider’s supported authentication, with narrowly scoped permissions. Plan credential rotation, API version changes and contract tests. Document payloads, limits and troubleshooting so another team can operate the connection after handover.
How we approach it
We map the data flow first: which system owns each record, what triggers an update, who may access it and what happens when a connection fails. The integration design follows those decisions.
How we workHealthcare & pharmaceuticals
Review summary
Prompt integration support and reporting delivery under technical pressure.
Yes, if it provides a suitable way to connect. We first review its APIs, access requirements and limits, then explain what the integration will involve.
Not always, and not every process needs it. Source APIs, event support, volume and rate limits determine the options. We agree an acceptable delay for each data flow and how users can see the latest successful update.
API documentation, sample records, access to test systems and your required workflows. Record volumes, one-way or two-way updates, migration history and recovery requirements affect the estimate.
Sometimes. We assess supported file exports, secure file transfer, database access or an existing connector before proposing a solution. These options can suit scheduled exchanges, but they have different security, timing and maintenance requirements. If no reliable interface exists, we explain the limitation before committing.
Insights
A customer checking an order on a phone needs a different app from an employee recording a visit. Before connecting either one to Salesforce, decide what people need to do and which data they can use.
Read the guideMarketing automationSomeone responds to an ad, but the salesperson sees only a name and an email address. Connecting marketing to Salesforce should also bring over the campaign, the person’s request and the information needed to follow up.
Read the guideOOB Consulting
Tell us what you want to build, connect or improve.
Services & project enquiries
Please leave out passwords and confidential information.
Send these details to OOB so we can respond to your project enquiry. This is not a marketing subscription.
Your enquiry is sent to OOB Consulting so we can review and respond to your project request.
Your details have not been sent.