How to integrate Lunatro with Salesforce for seamless data sync

If you’ve got customer data split between Salesforce and another tool, syncing them is always more annoying than it should be. This guide is for anyone who wants a straightforward, no-fuss way to get Lunatro talking to Salesforce—no wild promises, no hand-wavy “seamless integration” claims, just what actually works.

Whether you’re a Salesforce admin, a Lunatro power user, or just the person who got stuck with the integration project, I’ll walk you through the steps, call out the gotchas, and help you avoid common headaches.

1. What You Actually Need Before You Start

Don’t start clicking around yet. Here’s what you’ll need on hand:

  • Admin access to both Salesforce and Lunatro: No way around this. If you’re missing permissions, expect to hit walls.
  • An understanding of which data you really need to sync: Contacts? Deals? Custom objects? Don’t fall into the trap of syncing everything “just in case.”
  • A test Salesforce environment (strongly recommended): If you can, use a sandbox first. Trust me, you don’t want to break production data.
  • API access enabled on Salesforce: Not all Salesforce licenses allow this by default.

Pro tip: Write down (literally, on paper) which fields you want to sync and in which direction. Saves a ton of confusion later.

2. Step-by-Step: Connecting Lunatro to Salesforce

Here’s how to set up the integration so data moves reliably between the two platforms.

Step 1: Set Up an Integration User in Salesforce

Don’t use your personal Salesforce login for this. Create a dedicated “Lunatro Integration” user:

  • Go to Setup > Users > Users.
  • Click New User.
  • Fill in the required fields.
  • Assign a profile with API access (usually “System Administrator” or a custom integration profile).
  • Give it a strong password and save the credentials somewhere safe.

Why do this? If the integration ever breaks, you won’t lose access, and it’s way easier to troubleshoot.

Step 2: Create a Connected App in Salesforce

This lets Lunatro talk to Salesforce through the API.

  • In Salesforce Setup, search for App Manager.
  • Click New Connected App.
  • Fill out the basics:
  • Name: “Lunatro Integration”
  • Email: Your admin address
  • Under API (Enable OAuth Settings):
  • Check Enable OAuth Settings
  • Set Callback URL to: https://app.lunatro.com/oauth/callback (or whatever Lunatro documentation says)
  • Select OAuth scopes:
    • Access and manage your data (api)
    • Perform requests on your behalf at any time (refresh_token, offline_access)
  • Save and wait a few minutes for Salesforce to process it.

Copy the following for later: - Consumer Key - Consumer Secret

Gotcha: If you don’t set the right OAuth scopes, the integration will fail in frustrating, vague ways.

Step 3: Enable API Access in Salesforce Profile

Check that the integration user has API access:

  • Go to Setup > Profiles, select the profile for your integration user.
  • Under Administrative Permissions, make sure API Enabled is checked.

If you skip this, nothing will work—and the error messages aren’t helpful.

Step 4: Gather Your Salesforce Info

You’ll need: - Salesforce domain (e.g., yourcompany.my.salesforce.com) - Integration User username and password - Consumer Key and Secret (from the Connected App above) - Security Token (sometimes needed; Salesforce emails this when you reset it)

Step 5: Connect Lunatro to Salesforce

Now, finally, head to Lunatro:

  • Log in as an admin.
  • Go to Integrations (sometimes called “Apps” or “Connections”).
  • Find Salesforce and select Connect or Add Integration.
  • Enter the info from above: domain, user credentials, Consumer Key/Secret.
  • Authenticate using OAuth; you’ll get redirected to Salesforce to approve access.
  • If prompted for a security token, add it to the end of your password (Salesforce quirk).

If all goes well, you’ll see a confirmation. If not, double-check every field—the tiniest typo can kill this step.

3. Mapping Data: Don’t Sync Everything

Here’s where things get messy if you’re not careful.

  • Lunatro and Salesforce organize data differently. Don’t assume “contacts” always match.
  • Decide which objects (Leads, Contacts, Deals, Custom objects) you want to sync.
  • Map fields explicitly. For example:
    • Salesforce FirstName → Lunatro first_name
    • Salesforce AccountId → Lunatro company_id
  • In Lunatro’s interface, there should be a “field mapping” or “data mapping” section. Take your time here.

What to ignore: Don’t try to sync every field. Focus on what your team actually uses. Otherwise, you’ll end up with clutter and more ways for things to break.

Pro tip: Start with a one-way sync (Salesforce → Lunatro) first. Once you trust the mapping, enable two-way sync if you really need it.

4. Setting Up Sync Rules and Schedules

You’ll usually have options for:

  • One-way or two-way sync: Most teams only need one-way sync. Two-way sounds nice but multiplies complexity (and risk of conflicts).
  • Sync frequency: Real-time is possible, but unless you need instant updates, a scheduled sync (every 15 minutes or hour) is more reliable and less likely to hit API rate limits.
  • Conflict resolution: Decide what happens if the same record changes in both systems. Pick a “source of truth” and stick with it.

Be honest about what your team really needs. Overcomplicating this just means more late-night troubleshooting.

5. Test with Sample Data First

Before flipping the switch for your whole database:

  • Select a handful of test records—maybe five to ten.
  • Run a manual sync.
  • Check both Lunatro and Salesforce for:
    • Data accuracy (fields match as intended)
    • No duplicates
    • No data loss
  • Fix any mapping or sync rule issues before scaling up.

What can go wrong: Most problems at this stage are due to mismatched field types (e.g., Salesforce picklists vs. Lunatro text fields) or missing required fields.

6. Monitor and Maintain

Integration isn’t “set it and forget it,” no matter what the marketing says.

  • Set up error notifications: Make sure someone gets emailed if a sync fails.
  • Check sync logs weekly: Look for failed records or bottlenecks. Lunatro’s logs are usually under the integration settings.
  • Plan for Salesforce schema changes: If someone changes a field name in Salesforce, your integration can break silently.
  • Review permissions: If your integration user loses access, data stops flowing.

Pro tip: Keep a simple doc listing what’s mapped and who to call if something breaks. Future you will thank you.

7. Common Pitfalls (and How to Avoid Them)

  • Trying to sync everything: Resist this. Only sync what’s needed.
  • Ignoring API limits: Salesforce has API call quotas. High-frequency syncs can blow past these—especially if you have lots of data.
  • Assuming two-way sync will “just work”: It won’t. Expect data conflicts and duplicates. Start simple.
  • Not testing with real data: Dummy data isn’t enough. Use actual records (with dummy emails if you need to).

Keep It Simple (and Don’t Be Afraid to Iterate)

Integrating Lunatro with Salesforce isn’t magic, but it doesn’t have to be a nightmare. The real trick is to start small, sync only what you need, and keep an eye on things. If you run into trouble, back up, simplify, and try again—fancy features are only helpful if they work.

If you’re ever in doubt, focus on keeping your data clean and your sync rules simple. The rest can wait.