Step by step guide to integrating Trustworthy with Salesforce for seamless data sync

If you’ve ever tried to keep customer data in sync between two systems, you know how easily things get messy. This guide is for anyone who needs to connect Trustworthy with Salesforce and actually wants it to work—without handwaving, jargon, or “just click here” shortcuts that leave you stuck. Whether you’re in IT, ops, or you just drew the short straw for “integration lead,” here’s how to get it done (and what to watch out for).

Before You Start: What You’ll Need

Don’t skip this. Save yourself some backtracking.

  • A Trustworthy account: If you’re not set up yet, start here.
  • A Salesforce account: With admin rights. If you can’t add apps, stop now and get permission.
  • API access: Both platforms need it. On Salesforce, check your edition—API isn’t included in all plans.
  • Clear goals: Know what data you actually want to sync. “Everything” is a recipe for pain.
  • A test environment: Don’t do this live. Use sandboxes or demo data until you’re sure.

Step 1: Map Out Your Data Flows (Seriously, Do This)

Jumping straight into tools is tempting, but it’s a trap. Spend 10 minutes sketching out:

  • Which objects/fields sync? (e.g., Contacts, Accounts, Custom Fields)
  • Direction: One-way (Trustworthy → Salesforce), the other way, or both?
  • Frequency: Real-time, hourly, daily?
  • Ownership: Who “owns” the data if there’s a conflict?

Pro tip: If you skip this, you’ll waste hours later untangling field mismatches and weird duplicates.

Step 2: Set Up API Access in Salesforce

Here’s where most integrations break down, thanks to Salesforce’s maze of settings.

  1. Create a Connected App:
  2. Go to Setup > App Manager > New Connected App.
  3. Fill in basic info (name, contact email).
  4. Enable OAuth Settings. Set the callback URL (you’ll get this from Trustworthy during setup).

  5. Add required OAuth scopes (usually api, refresh_token, and offline_access).

  6. Save and Wait

  7. Salesforce can take up to 10 minutes to make the app live. Don’t panic if it doesn’t show up right away.

  8. Grab Your Credentials

  9. Copy the Consumer Key and Consumer Secret. You’ll need these for Trustworthy.

What’s worth your time: Setting up a separate integration user in Salesforce. Don’t use your personal admin account.

What’s not: Overcomplicating the app settings. Start simple—you can lock things down later.

Step 3: Configure Trustworthy’s Salesforce Integration

Now you’ll connect the dots from the Trustworthy side.

  1. Log into Trustworthy
  2. Go to the Integrations section.

  3. Find Salesforce and click “Connect”.

  4. Enter Salesforce API Credentials

  5. Paste in the Consumer Key and Consumer Secret from your Salesforce Connected App.

  6. Enter your Salesforce login info if prompted.

  7. Set Callback/Redirect URL

  8. Use the exact URL Trustworthy gives you in the setup instructions; copy-paste to avoid typos.

  9. Authorize the Connection

  10. Trustworthy should redirect you to Salesforce to grant permissions.
  11. Approve the requested access (read what it’s asking for).

What works: Trustworthy usually guides you pretty well through this, but if you get stuck, check your OAuth scopes and callback URLs—they’re the usual suspects.

What doesn’t: Assuming “it just works” because you got a green checkmark. Test the connection before moving on.

Step 4: Define What Gets Synced (and How)

Here’s where you decide what actually moves between the two systems.

  1. Choose Salesforce Objects
  2. Typically: Contacts, Accounts, maybe Opportunities.

  3. Avoid syncing every custom object unless you have a real use case.

  4. Map Fields

  5. Match Trustworthy fields to Salesforce fields. Watch out for differences in data types (e.g., text vs. picklist).

  6. Set up any required field transformations (Trustworthy may let you tweak them).

  7. Set Sync Rules

  8. Direction: Trustworthy to Salesforce, Salesforce to Trustworthy, or bi-directional.

  9. Conflict resolution: If a field is updated in both places, which system wins?

  10. Test With Sample Data

  11. Run a dry run with a few records.
  12. Check if everything lands where you expect it.

Pro tip: Start with a single object (like Contacts) until you’re sure the sync is reliable. Layer in more complexity only after you see it working.

Step 5: Schedule and Monitor Your Sync

Now, make sure your integration isn’t just a one-time thing.

  1. Set Sync Frequency
  2. Real-time is tempting, but overkill for most folks. Hourly or daily works for most use cases.

  3. If you do need real-time, be ready for more troubleshooting.

  4. Enable Notifications

  5. Turn on email or in-app alerts for failed syncs or data errors.

  6. Audit Logs

  7. Make sure you can review what data was synced, when, and if anything failed.

  8. Both systems should give you some log access—use it.

  9. Set a Rollback Plan

  10. If things go sideways (they might), know how to disconnect or undo a sync without nuking your data.

What works: Regular, low-frequency syncs with clear logs.

What doesn’t: “Set it and forget it.” Always check the first few runs, and after any schema changes on either side.

Step 6: Test, Troubleshoot, and Go Live

You’re almost done, but this is where most integrations fall apart.

  1. Test Edge Cases

  2. Try special characters, empty fields, really long text—see what breaks.

  3. Check Permissions

  4. Make sure your integration user in Salesforce has the right object and field permissions.

  5. Missing permissions are the #1 cause of silent sync failures.

  6. Look for Duplicates

  7. If you see duplicate records, check your matching rules. Adjust as needed.

  8. Go Live (Gradually)

  9. Move from sandbox to production.
  10. Start by syncing a small batch of real data.
  11. Monitor closely for at least a week.

What’s worth your time: Documenting what you did. Future you—or the unlucky soul after you—will thank you.

What’s not: Syncing everything at once. “All or nothing” launches are a disaster waiting to happen.

Gotchas, Shortcuts, and Honest Advice

  • Don’t trust default mappings—double-check them.
  • Avoid syncing confidential data unless you’re sure about compliance on both sides.
  • Trustworthy support is actually pretty responsive—if you hit a wall, ask for help instead of banging your head.
  • Salesforce API limits are real—if you sync a lot, monitor your usage or you’ll get throttled.

Wrapping Up: Keep It Simple, Keep It Safe

Integrating Trustworthy with Salesforce isn’t rocket science, but it’s not a “click and done” job either. Start small, document everything, and resist the urge to sync more data than you need. If something feels too easy, double-check it. Good integrations are boring—they just work. And that’s the goal.

Now, go make your data less of a mess. And if you ever have to redo it, you’ll actually know what you did the first time.