Step by step guide to integrating Salesforce data into Clari Co Pilot

If you’re trying to get your Salesforce data into Clari Co-Pilot, you probably want real answers, not marketing speak. Maybe your sales team is sick of double entry, or you’re tired of telling reps, “Just update the CRM.” Either way, connecting Salesforce to Clari Co-Pilot can help you pull in call notes, opportunity data, and more—if you do it right. This guide is for admins, ops folks, or anyone tasked with making the tools actually talk to each other.

Let’s get your data flowing, minus the headaches.

What You Need Before You Start

Before you dive in, check that you have:

  • Salesforce admin access (or at least API access and permission to create connected apps)
  • Clari Co-Pilot admin access
  • A clear idea of which Salesforce objects and fields you want to sync (don’t just pull everything—trust me)
  • A test Salesforce account or sandbox if you don’t want to risk your production data

Pro tip: If you’re not sure what data you need, ask your sales team what actually gets used in their workflows. No point syncing “Annual Revenue” if no one looks at it.

Step 1: Map Out What Data You Actually Need

Don’t just hit “sync all.” Figure out:

  • Which objects: Most people care about Leads, Contacts, Opportunities, Accounts, Activities, and maybe custom fields.
  • Which fields: Keep it lean. Too many fields slow down syncs and clutter your UI.
  • Direction: Do you want data flowing only into Clari Co-Pilot, or both ways? (Most folks start with one-way.)

What to ignore: Standard fields like “Created By” or “Last Modified” that don’t help sales conversations. Also, avoid syncing highly sensitive data unless you’re sure you need it.

Step 2: Set Up a Salesforce Connected App for Clari Co-Pilot

To let Clari Co-Pilot pull data, you’ll need a connected app in Salesforce. Here’s how:

  1. Log into Salesforce as an admin.
  2. Go to Setup → App Manager → New Connected App.
  3. Name it something obvious, like “Clari Co-Pilot Integration.”
  4. Under API (Enable OAuth Settings):
    • Check “Enable OAuth Settings.”
    • Set the callback URL as provided by Clari Co-Pilot.
    • Select OAuth Scopes: Access and manage your data (api), and maybe Perform requests on your behalf at any time (refresh_token, offline_access) if you want background syncs.
  5. Save the app. Note the Consumer Key and Consumer Secret.

Heads up: Salesforce takes 2-10 minutes to make the app available after saving. Don’t panic if it doesn’t show up instantly.

Step 3: Get Your Salesforce API Credentials

You’ll need:

  • Client ID (a.k.a. Consumer Key)
  • Client Secret
  • Salesforce Username and Password (ideally, use a dedicated integration user so you’re not stuck if someone leaves)
  • Security Token (if your org requires it—Salesforce sends this to your email)

Pro tip: Don’t use your own admin account for this. Create an “integration” user so you don’t break things later.

Step 4: Connect Salesforce to Clari Co-Pilot

Now, jump into Clari Co-Pilot:

  1. Log in as an admin.
  2. Go to Settings → Integrations → Salesforce (it might be under “CRM Integrations”).
  3. Click Add Integration or Connect Salesforce.
  4. Enter your Salesforce credentials:
    • Client ID
    • Client Secret
    • Username
    • Password (+ Security Token, if prompted)
  5. Choose which Salesforce environment: Production or Sandbox.
  6. Authorize the connection.

Clari Co-Pilot should now handshake with Salesforce and show a “Connected” status.

What can go wrong: - Invalid credentials: Double-check your Client ID/Secret and security token. - Wrong permissions: Make sure your Salesforce user has API access and rights to the objects you want to sync. - Firewall/IP restrictions: Some Salesforce orgs block outside connections. Ask IT if nothing works.

Step 5: Configure Data Sync Settings

This is where you decide what actually flows into Clari Co-Pilot.

  1. In Clari Co-Pilot’s integration settings, select which Salesforce objects to sync (Opportunities, Contacts, etc.).
  2. Pick the fields you want. Less is more—don’t try to sync every custom field unless you love debugging.
  3. Decide on sync frequency: Real-time, hourly, or daily. For most, hourly is plenty.
  4. Set up any filters. For example:
    • Only pull Opportunities where Stage ≠ Closed Lost.
    • Ignore Leads created before a certain date.

Pro tip: Start small. Sync a single object and a few fields, then expand. It’s a lot easier to fix a small sync than untangle a huge mess.

Step 6: Test the Integration

Before you roll it out to the whole team:

  1. Create or update a test record in Salesforce (e.g., change an Opportunity stage).
  2. Wait for the sync (or trigger it manually if possible).
  3. Check Clari Co-Pilot to see if the change appears.

If you see the update, you’re in business.

If you don’t: - Check sync logs in Clari Co-Pilot for errors. - Double-check field mappings and permissions in Salesforce. - Make sure you didn’t hit API limits (Salesforce loves to rate-limit).

Step 7: Roll Out to Your Team (and Train Them)

Once it’s working:

  • Announce the integration to your team. Explain what’s new and what they can ignore.
  • Show them where Salesforce data now appears in Clari Co-Pilot.
  • Be clear about where to enter/update data. Don’t let folks enter the same info in two places.

What to watch out for: Users sometimes keep using old workflows out of habit. Check in after a week to make sure they’re actually using the new setup.

What Works, What Doesn’t, and What to Ignore

What works: - Real-time or near real-time syncing of core sales data (Opportunities, Contacts, etc.) - Reducing manual entry, especially for call notes and activity logging - Better forecasting and coaching tools when data is actually up to date

What doesn’t: - Overly complex field mappings (they break easily and are hell to troubleshoot) - Trying to sync every possible object “just in case” - Ignoring data privacy—don’t pull in sensitive stuff unless you’re sure

What to ignore: - Marketing claims about “seamless” integrations. There’s always a hiccup or two. - Old, unused fields or objects. If you don’t use them, don’t sync them.

Troubleshooting Common Issues

  • Sync errors: Usually permissions or API limits. Check the error logs in both systems.
  • Data mismatches: Double-check your field mappings—sometimes a “Status” in Salesforce doesn’t match what Clari Co-Pilot expects.
  • Slow syncs: Cut down the number of fields and objects. More data = slower syncs.
  • Disconnected integration: Salesforce passwords and tokens expire. Set reminders to update them.

Keep It Simple and Iterate

Integrating Salesforce with Clari Co-Pilot isn’t rocket science, but it’s easy to overthink. Start with the basics, get the core data flowing, and add complexity only if you need it. Keep your field mappings lean, document what you did, and don’t be afraid to tweak as your team’s needs change. Most importantly—ask your users what’s actually helpful, not just what looks impressive in a demo.