Studio
Black Friday

Up to 70% off kits30% off services

Ends in
All Tools
Salesforce · Free Check

Salesforce Integration Health Check

Fifteen yes-or-no questions about the integrations connected to your Salesforce org: who they run as, how many API calls they use, how they match records, what happens when they fail and who owns them. Five minutes, a score, and a fix for every gap. Answers stay in your browser.

1.Access

  1. Every integration runs as a dedicated integration user, not a person's login.
  2. Integration users have only the object and field permissions they need, through a permission set.
  3. You know every connected app and AppExchange package that calls your org, and who owns each one.

2.API usage

  1. Daily API usage stays under about 70% of your allocation, including busy days.
  2. API Usage Notifications are set to email someone before the limit is reached.
  3. Integrations sync only changed records, and large loads use Bulk API 2.0.

3.Matching

  1. Records are matched on an External ID field, not on names or emails.
  2. Duplicate and matching rules are active for accounts and contacts, and integrations respect them.
  3. Every synced field has one system of record, and nothing else writes to it.

4.Errors

  1. Failed syncs alert a named person or channel the same day.
  2. Integrations retry temporary failures and keep failed records to replay later.
  3. Flows, triggers and validation rules are designed with integration updates in mind.

5.Ownership

  1. Integration changes are tested in a sandbox before production.
  2. Each integration has a document: what syncs, which way, how records match and who owns it.
  3. Someone is responsible for each integration after launch.

Want someone to check the real org?30% OFF

Our $349$499 integration health check reviews your actual integration users, permissions, API usage and error logs, and gives you a written fix plan in about 5 business days, credited toward the fix.

Why integrations break, and how to keep them healthy

Most Salesforce integration failures don't start as bugs. They start as shortcuts that worked on launch day: a connector authorised with an admin's own login, customers matched by name because no ID was stored, a nightly full resync because changed-records-only took longer to build.

  1. Give every integration its own user. API-only, with a permission set that covers only the objects it maps. It survives staff changes, and its edits are easy to spot.
  2. Match on IDs. Store the other system's ID in an External ID field and upsert on it. Names and emails change; IDs don't.
  3. Budget your API calls. Every integration shares one daily allocation. Our API limit calculator shows how much yours have to spare.
  4. Make failures loud. Retries for temporary errors, a queue for failed records, and an alert that reaches a person the same day.
  5. Write it down. One page per integration: what syncs, which way, how records match and who owns it. Start from our field mapping template.

Frequently asked questions

What the check covers, how it scores and what to do next.