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

So you’ve got data in Salesforce, maybe in a few other tools, and you’re tired of copy-pasting, CSV exports, and things falling through the cracks. You’ve heard Sheppardd might help, but you don’t want to spend all day reading docs or chasing support tickets. This guide is for you: folks who want their apps to just talk to each other, without getting a computer science degree in the process.

Below, I’ll walk you through how to actually connect Sheppardd to Salesforce, what you can skip, and what you shouldn’t ignore. I’ll also call out stuff that’s not as “seamless” as the marketing makes it sound, so you don’t waste time.

What You Need Before You Start

Before you dive in, make sure you have:

  • Admin access in Salesforce. You’ll need this to set up integrations and get API credentials.
  • A Sheppardd account (with integration features unlocked).
  • A clear idea of what data you want to sync. Contacts? Opportunities? Custom objects? Don’t just “turn it all on” and hope for the best.

Pro tip: Write down your use case. “Sync all new Salesforce leads into Sheppardd as contacts” is a lot easier to test and troubleshoot than “make everything talk to everything.”

Step 1: Prep Salesforce for Integration

1.1 Create a Connected App in Salesforce

Sheppardd will need to talk to Salesforce through its API. For that, you’ll need to set up a “Connected App.”

  • Go to Setup in Salesforce (top right gear icon).
  • Search for App Manager in the Quick Find box.
  • Click New Connected App (top right).
  • Give it a name (e.g., "Sheppardd Integration"). The rest of the info is for your own reference.
  • Under API (Enable OAuth Settings), check the box.
  • For Callback URL, use: https://app.sheppardd.com/oauth/callback (double-check this in Sheppardd’s docs or support, as it can change).
  • Selected OAuth Scopes: Add Full access (full), Access and manage your data (api), and Perform requests on your behalf at any time (refresh_token, offline_access). Don’t go nuts with permissions you don’t need.

Click Save. You’ll get a Consumer Key and Consumer Secret—copy these somewhere safe (but not on a sticky note).

Heads up: Salesforce can take 2–10 minutes to make new Connected Apps live. If you get weird errors, wait and try again.

1.2 Check User Permissions

The Salesforce user you’ll connect needs API access and permissions to the objects you plan to sync. Profiles and permissions in Salesforce can be a maze—if you get auth errors later, this is usually why.

Step 2: Prep Sheppardd for Salesforce Connection

2.1 Find the Salesforce Integration Option

  • Log in to Sheppardd.
  • Go to Integrations or Connections (name might vary).
  • Find Salesforce in the list. If it’s not there, you might need to upgrade your plan or ask support to enable it.

2.2 Authorize Salesforce

  • Click Connect (or similar).
  • You’ll be prompted for your Salesforce Consumer Key and Consumer Secret.
  • Enter these, along with the Salesforce instance URL (usually looks like https://yourcompany.my.salesforce.com).
  • You’ll be sent to Salesforce to log in and approve access.

If you see an error about redirects or permissions, double-check your Connected App settings in Salesforce.

Step 3: Set Up Your Data Sync Rules

Here’s where things get real. Don’t just “sync everything.” Start small.

3.1 Choose What to Sync

  • Sheppardd will show you available Salesforce objects: Leads, Contacts, Accounts, etc.
  • Pick one to start (say, Contacts).
  • Decide direction: Salesforce → Sheppardd, Sheppardd → Salesforce, or both. Bi-directional sync sounds cool, but it gets messy fast—especially with data conflicts.

Pro tip: Start with one-way sync. Get that working, then get fancy.

3.2 Map Fields

  • For each object, map Salesforce fields to Sheppardd fields.
  • Don’t just click “Auto-map”—look for field mismatches (e.g., Salesforce has “FirstName” and Sheppardd has “Given Name”). Fix these now or you’ll be cleaning up bad data later.
  • If you have custom fields, you’ll need to add those mappings manually.

What to ignore: Don’t bother mapping fields you don’t use. More data isn’t always better.

3.3 Set Sync Triggers

  • Most tools let you pick: sync on create, update, or on a schedule (e.g., every hour).
  • For starters, set it to manual or scheduled sync. Real-time sync can hammer your API quotas and make debugging harder.

Step 4: Test the Connection With a Single Record

Don’t skip this, even if you’re feeling lucky.

  • Create a test Contact (or whatever object you picked) in Salesforce.
  • Trigger your sync in Sheppardd.
  • Check if the record shows up, with correct field mapping, in Sheppardd.
  • Make a change in Sheppardd (if you’re testing two-way sync) and see if it pushes back to Salesforce.

Common gotchas: - Field type mismatches: Text-to-number or date formats won’t sync cleanly. - Required fields: If Sheppardd tries to create a Salesforce record without filling all required fields, you’ll get errors. - Permissions: API user doesn’t have access to object/field.

Step 5: Roll Out to Live Data—Cautiously

Once you’ve tested with a single record:

  • Expand to a small batch (10–20 records).
  • Watch for duplicates, missing data, or weird formatting.
  • If you’re syncing old data, consider running a one-time import/export first, then turning on ongoing sync.

Don’t: Turn on full bi-directional sync for all records on day one. You’ll regret it.

Step 6: Monitor and Maintain the Integration

“Set it and forget it” is a myth. Here’s what you should actually do:

  • Check sync logs weekly (or more during rollout). Look for failures and weirdness.
  • Set up alerts if Sheppardd supports them. Don’t wait for someone in sales to tell you the data’s off.
  • Review field mappings when you add new fields or change Salesforce layouts.
  • Keep an eye on API limits. Salesforce has daily quotas—if Sheppardd blasts through them, other apps might break.

Honest Takes and Troubleshooting

  • What works: Sheppardd’s integration is solid for standard objects and straightforward mapping. Setup isn’t hard if you’ve done any API work before.
  • What doesn’t: Custom objects, formula fields, or really complex Salesforce automations can break things. Expect to tweak field mappings or add manual steps.
  • Ignore the “seamless” hype: No integration is truly “set and forget.” Plan on regular check-ins, especially as your Salesforce setup changes.

If you get stuck:
- Check Sheppardd’s support docs and forums—someone’s probably had your issue before. - Don’t be afraid to contact support, but be specific (“Sync fails for custom field X on Contact” beats “It’s broken”). - If all else fails, roll back and start with just the basics.

Keep It Simple

There’s always a temptation to sync everything everywhere, but that’s how you end up with a mess. Start with the minimum, get it working, and iterate. Integrations are living things—they need tweaks as your business changes. Keep your setup clean, review it a couple of times a year, and don’t buy the “no-maintenance required” myth. That’s how you get seamless (enough) data sync that actually works.