What we do
Tools
Industries
Department
How we workLet's talk →
Home/Salesloft/Salesloft Salesforce Integration
Salesloft and Salesforce

Salesloft Salesforce Integration: What Each Setting Decides, and What's Left Over

The native Salesloft integration with Salesforce is two-way and does more than most teams switch on: it matches people to leads or contacts, syncs mapped fields in both directions, logs calls and emails as activity, and keeps a log of every change. Most of the trouble comes from two places: who wins when both systems edit a field, and the data your cadences need that isn't on a lead, contact or account.

Salesloft's sync, in five lines

People: each Salesloft person is matched to a Salesforce record using the rule you pick: contact first then lead, contacts only, or leads only.

Fields: mapped fields sync both ways. For each one, an admin sets which system takes priority and which can receive updates. Changes push from Salesloft as they happen, and Salesloft pulls from Salesforce every 1, 5 or 10 minutes.

Accounts: standard and custom account fields come across, along with the related contacts.

Activity: emails, calls and steps log to Salesforce as completed tasks on the lead or contact, with more than 30 activity details available to map, such as call duration and disposition.

Sync log: every change, its direction and any failure, with a retry for failed records.

When the Salesloft and Salesforce data stops agreeing

A field that flips back every few minutes

How you'll know: A rep fixes a title or phone number in Salesloft, and the old value comes back after the next pull.

Fix: Both systems are allowed to write the field and Salesforce has priority. Decide which system owns each mapped field and let only that one send updates.

New people that never reach Salesforce

How you'll know: The sync log shows failures on create, often the same error over and over.

Fix: A required Salesforce field or a validation rule is rejecting the record. Map a value for the required field, or adjust the rule for the integration user, then retry from the log.

Duplicates between leads and contacts

How you'll know: One person is a lead and a contact in Salesforce, and Salesloft activity lands on the one nobody looks at.

Fix: Pick the matching rule that suits how your team converts leads, merge the existing pairs, and keep the rule consistent from then on.

An automation rule that ignores people who already qualify

How you'll know: You build a rule for a stage or field value, and the hundreds of people already sitting at that value are never enrolled.

Fix: Salesloft's automation rules fire when data changes, not on what's already there. Enroll the existing group once, by list or through the API, and let the rule handle new changes.

Activity on the contact, nothing on the opportunity

How you'll know: Your Salesforce opportunity report can't say which cadence produced the deal.

Fix: Tasks attach to the lead or contact. Getting the sourcing cadence onto the opportunity takes logic that runs when the opportunity is created, which is a build, not a setting.

Setting up the Salesloft connection so it stays clean

  1. 1

    Connect with a dedicated integration user

    Use a Salesforce user with API access whose visibility covers every record reps work. A personal login leaves gaps the day that person changes role.

    Watch for: Salesloft's pulls are Salesforce API calls on that user, counted against the same daily allowance as your other connected apps.

  2. 2

    Choose the person matching rule

    Contact first then lead suits most teams that convert leads. Leads only or contacts only fits teams that work one object.

  3. 3

    Map fields, and give each one an owner

    Map only the fields reps and reports use. For each, set the priority and which side can receive updates, so a field is edited in one place and read in the other.

  4. 4

    Decide which activity details go across

    Pick the call and email details your Salesforce reports need, like disposition, duration or the cadence name, and create matching custom activity fields in Salesforce first.

  5. 5

    Set the automation rules for deal changes

    Removing people from cadences when a company or opportunity stage changes is built in. Set those rules now rather than paying anyone to build them, and order the specific ones above the general ones.

    Watch for: rules run top to bottom, so a broad rule near the top can act before the precise one you meant.

Gaps between Salesloft and Salesforce that need code

01

Custom objects that should drive cadences

Renewals, subscriptions, product usage or partner records often live on custom objects. We bring the signal onto a field Salesloft maps, or enroll people directly through the Salesloft API when the record changes.

02

The sourcing cadence on the opportunity

When an opportunity is created, we look back at the contact's Salesloft activity and write the cadence and step that produced it onto the opportunity, so pipeline reports can group by play.

03

Data from outside Salesforce

Billing status, usage spikes or support tickets from other systems can enroll or pause people. Automation rules only see what's in Salesloft, so that data has to be brought in first.

04

A cleanup after years of two-way edits

Duplicate leads and contacts, conflicting owners and fields overwritten in both directions, fixed once in Salesforce and then kept from coming back.

Salesloft and Salesforce sync questions

Does Salesloft have a native Salesforce integration?

Yes. It's built in, two-way and configured from Salesloft's CRM settings. It matches people to leads or contacts, syncs mapped fields with a priority you choose for each, brings over account fields and logs activity as completed tasks.

Can Salesloft sync with Salesforce custom objects?

Not directly in most setups. The mappings center on people, accounts and activity, including custom fields on those. Data held on a separate custom object needs to be copied onto a field Salesloft maps, or acted on through the Salesloft API, which is the kind of work n-frames builds.

Do I need a Salesforce admin to set up the Salesloft integration?

It helps. Someone needs to create the integration user with API access, add any custom activity fields, and check validation rules that could block records. Field mapping and automation rules are done on the Salesloft side by a Salesloft admin.

Is there a cost to connecting Salesloft and Salesforce?

The native integration comes with Salesloft, with no separate connector fee. You do need a Salesforce edition with API access. Custom work beyond the native sync, like custom-object enrollment or opportunity attribution, is priced on what's being built.

Will Salesloft stop emailing someone when the deal closes in Salesforce?

It can, without custom work. Salesloft's automation rules can remove people from cadences when a company or opportunity stage changes, for example to Closed Won or Closed Lost. The stage just has to be visible to Salesloft through the sync.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.