Salesloft + Salesforce Integration Guide: Setup, Use Cases

How the Salesloft and Salesforce Integration Works

Salesloft connects to Salesforce through a native OAuth integration that syncs contacts, leads, accounts, opportunities, and activity data in near real-time. The sync is bidirectional: records updated in Salesforce push into Salesloft, and calls, emails, and cadence steps logged in Salesloft write back to Salesforce as Tasks. Most activity events push within 2 to 5 minutes.

Salesforce is the system of record: if you update a phone number in both tools at the same time, the Salesforce value wins on the next sync. That's by design, and it's what makes the integration reliable rather than conflicting.

The integration doesn't just move data passively. It powers attribution. When a Salesloft cadence touches a contact who later becomes a closed-won opportunity, you can trace that path if you've configured opportunity contact roles and influence attribution. Without that setup, you're flying blind on what outbound actually contributes to pipeline.

How to Set Up the Salesloft and Salesforce Integration

Setting up the native Salesloft and Salesforce integration takes 20 to 40 minutes if your Salesforce org is clean. You need Salesforce admin access and Salesloft admin rights. The native integration is available on Salesloft Essentials and above. Salesforce Professional Edition or higher is required because the integration calls the Salesforce API.

1. Connect your Salesforce org. In Salesloft, navigate to Settings, then CRM, then Salesforce. Click Connect to Salesforce and authenticate with admin credentials. Use a dedicated integration service account if your org has one. Connecting under a personal account means the integration breaks the moment that person's account is deactivated or their password changes.
2. Review and configure field mappings. After connecting, Salesloft displays a default mapping table. Don't accept the defaults without reviewing them. In most orgs, job titles, territories, and custom lead sources live in custom Salesforce fields, not the native field names the default mapping assumes. Fix these before your first sync or you'll spend weeks chasing bad data downstream.
3. Set your record creation rules. Decide whether Salesloft can create new records in Salesforce. If you allow it, an SDR adding a contact in Salesloft can push a new Contact record that duplicates an existing Lead. Most teams set Salesloft to update-only mode and handle all new record creation in Salesforce exclusively.
4. Configure activity logging. Under Activity Log Settings, enable email sends, calls, and meeting bookings to write back to Salesforce as Tasks. If you skip this step, your Salesforce activity timeline stays blank and outbound pipeline attribution becomes impossible to report on accurately.
5. Enable cadence-to-opportunity attribution. This setting is off by default and most teams never turn it on. Go to Salesloft's attribution settings and enable Opportunity Contact Role stamping. It marks opportunities with the cadence that touched the associated contact before the deal was created. This one setting is worth more than every dashboard you'll build without it.
6. Run a test sync and verify the connection. Pull 3 to 5 contacts from Salesforce into Salesloft, send a test email, log a call, and confirm the activities appear in Salesforce within 5 minutes. Then update a field in Salesforce and verify it reflects in Salesloft. A broken sync that runs silently for 30 days is much harder to untangle than one caught on day one.

Four Integration Pitfalls That Break Your Data Quality

The most common Salesloft and Salesforce integration failures share a pattern: they're silent. No error message, no failed sync notification. You discover them weeks later when a report looks wrong or a rep asks why their activities aren't showing up. Here are the four to watch for and how to catch them early.

Duplicate Records from Bidirectional Creation

This happens when Salesloft is allowed to create records in Salesforce and your team also creates records manually on the same prospects. Set Salesloft to update-only mode and run a deduplication pass in Salesforce before you go live. Salesforce's native duplicate rules don't always catch records pushed in via API, so test your rules explicitly with a sample import before launch.

API Rate Limits During Peak Hours

Salesforce caps API calls per 24-hour period, and that cap is shared across every integration connected to your org. A 50-rep Salesloft team running high-volume sequences can burn through the budget fast, especially when data enrichment tools and reporting layers are also calling the same API. Watch your API usage dashboard and stay under 80% of your daily limit. If you're already close, audit your integrations for unnecessary calls or talk to Salesforce about increasing your allocation.

Field Mapping Drift After Salesforce Updates

Every time a Salesforce admin renames an API field, removes a picklist value, or adds a validation rule, the Salesloft mapping can silently break. Data stops flowing for that field and you won't get an alert. Set a quarterly calendar reminder to audit your active field mappings, especially after any Salesforce seasonal release window.

Enrichment Tools Overwriting Email Addresses Mid-Sequence

If you run an enrichment tool that auto-updates Salesforce contact records, those email changes push into Salesloft. A rep thinks their cadence is hitting the right inbox. It isn't. Exclude active Salesloft prospects from enrichment auto-update rules, or build a suppression list in your enrichment tool that blocks updates on any contact currently enrolled in a sequence.

Use Cases That Justify the Setup Time

Three workflows get the most value from the Salesloft and Salesforce integration: automatic lead enrollment on record creation, lifecycle status sync from cadence reply to CRM task, and outbound pipeline attribution reporting. If you're not running at least two of these, the integration is doing less than half its job.

Automatic Lead Enrollment into Sequences

A Salesforce Flow or workflow rule can trigger Salesloft cadence enrollment the moment a qualifying lead record is created. This cuts time-to-first-touch from hours to under 15 minutes on inbound leads without requiring rep action. Scope the trigger carefully. Enterprise accounts should not get auto-enrolled in the SMB cadence because someone forgot to add a filter.

Reply Detection Flowing Back as CRM Tasks

When a prospect replies to a Salesloft email, the cadence pauses automatically. But if that pause doesn't create a task in Salesforce, the assigned rep may not notice for hours. With activity logging active, Salesloft writes a task to the Salesforce record within minutes of reply detection. Without it, roughly a third of replies get missed because they never appear in the rep's normal Salesforce workflow.

Outbound Pipeline Attribution Reporting

This is the use case that justifies cold email as a revenue channel to your CFO. When you configure cadence-to-opportunity attribution in step 5 above, you get a field on every Salesforce opportunity showing which Salesloft cadence touched the contact before the deal was created. That data answers the question your VP of Sales faces every quarter: how much pipeline did outbound actually influence?

Plan Requirements and True Cost of Running This Integration

The native Salesloft and Salesforce integration is included on all current Salesloft plans: Essentials, Advanced, and Premier. Salesforce Professional Edition or higher is required for API access. If you're on Salesforce Essentials Edition, the integration won't work at all. Enterprise Edition gets significantly higher API limits, which matters at 20 or more Salesloft seats.

There's no additional per-seat fee for the integration itself. But running it incorrectly has a real cost. At a conservative $75 per hour for fully-loaded rep time, and 45 to 90 minutes per week in manual data entry when the sync doesn't work, you're burning $225 to $450 per rep per month. On a 10-person outbound team, that's $27,000 to $54,000 per year in avoidable overhead.

If you're not ready for the native integration and need a temporary workaround, a Zapier connector can push basic contact data in one direction. It won't handle activity logging, it breaks on field changes, and attribution is impossible. Treat it as a stopgap for under 30 days while you complete the native setup, not a permanent solution.

If you'd like help building outbound infrastructure that integrates cleanly with your Salesforce setup, Modern Inbound runs the full execution layer: account lists, sequences, deliverability, and meeting routing.

Frequently Asked Questions