Salesloft + HubSpot Integration Guide: Setup, Use Cases

How the Salesloft + HubSpot Integration Actually Works

The Salesloft + HubSpot integration syncs contacts, email and call activities, and CRM stage changes bidirectionally on a 5 to 15 minute polling cycle. Salesloft pushes cadence activity to HubSpot contact timelines. HubSpot lifecycle stage changes flow back to Salesloft to pause or reassign prospects in active cadences.

The data flows through three channels. Contact records sync bidirectionally: add a contact in Salesloft, it appears in HubSpot; update a field in HubSpot, it reflects in Salesloft on the next poll. Salesloft logs every touchpoint (email step executed, call completed, LinkedIn step triggered) as a HubSpot activity. Deal stage changes in HubSpot push a status flag back to Salesloft so prospects don't get emailed after entering a live sales cycle.

What doesn't sync natively: Salesloft meeting data only goes to HubSpot if you're on Salesloft's Meetings product. Call recordings don't transfer. Custom object data requires the API. For most outbound teams, those gaps don't matter. The contact, activity, and lifecycle sync covers the value.

How to Set Up the Salesloft + HubSpot Integration (6 Steps)

Setup takes 20 to 30 minutes if your HubSpot permissions are correct before you start. The most common failure point isn't the configuration itself. It's connecting with a personal user account instead of a dedicated service account. When that user's password changes or they leave the company, the sync breaks silently and nobody notices for weeks.

1. Create a dedicated HubSpot service account. Don't use your personal login. Set up a non-personal account (ops@yourcompany.com works) with Super Admin or CRM plus Marketing access. This account owns the connection permanently.
2. In Salesloft Admin, navigate to CRM Setup. Select HubSpot from the CRM dropdown. You need Super Admin access in Salesloft to see this screen.
3. Authenticate via HubSpot OAuth. Salesloft redirects you to HubSpot's auth page. Log in with the service account from Step 1, not your personal credentials.
4. Map your contact fields. Map Salesloft's default fields (First Name, Last Name, Email, Company, Title, Phone) to your HubSpot contact properties. Add any custom properties here. Document the mapping in a shared spreadsheet now. Field mapping drift starts the moment someone adds a new HubSpot property without telling the Salesloft admin.
5. Set sync rules for contact creation. Decide whether Salesloft should create new HubSpot contacts automatically or only update existing ones. Set HubSpot to the same logic. If both sides create on new import, you'll generate duplicates at scale. For outbound-first teams, Salesloft is the source of truth for net-new contacts and HubSpot updates from there.
6. Test with one record before going live. Add a single contact to a Salesloft cadence. Wait 15 minutes. Check HubSpot for the record and the activity timeline. Confirm lifecycle stage is correct. If this passes, enroll your full list. If it doesn't, check Admin > CRM Setup > Sync Log in Salesloft for specific error codes before adding 2,000 contacts.

Common Pitfalls and How to Fix Them

Duplicate contacts are the most expensive failure mode in this integration. When both Salesloft and HubSpot are set to create contacts on new prospect import, a 500-person cadence generates 500 HubSpot duplicates within hours. The deduplication tool helps, but it's manual cleanup that takes days on a large database.

Rate limits are the second most common problem. HubSpot's API allows 100 requests per 10 seconds on Professional and 150 on Enterprise, per HubSpot's developer documentation. If you're running multiple cadences with thousands of active contacts, the sync queue backs up. Activities may log 4 to 6 hours after they occur. Spread cadence launches across the day instead of enrolling 2,000 contacts at 9 AM.

Field mapping drift is silent and slow. Every time someone adds a new custom property in HubSpot without updating the Salesloft field map, that property drops out of sync. Teams that skip documenting their mappings end up with CRM data that's half-mapped six months later and no clean way to fix it without a full re-sync.

Deliverability risk from enrichment tools is underrated. If you're running Clay or Clearbit connected to HubSpot, those tools can overwrite the email field on contact records. Salesloft's next send then uses the overwritten address. Configure enrichment tools to write to a separate enriched email property, not the primary email field. One bad enrichment run can corrupt thousands of outbound contacts overnight.

Three Use Cases Where This Integration Pays Off

The integration is worth the setup time in three scenarios: lifecycle-triggered cadence enrollment, reply-based deal creation, and pipeline attribution reporting. All three require the bidirectional sync to work correctly, which is why the six setup steps above matter before anything else.

Lifecycle-triggered enrollment. When a HubSpot contact reaches Marketing Qualified Lead status from an inbound form, a HubSpot workflow pushes a property update that Salesloft reads to auto-enroll that contact in an SDR outbound cadence. This closes the inbound-to-outbound gap without manual handoffs. Teams using this pattern report cutting MQL-to-first-touch time from 2 to 3 days down to under 4 hours, per Salesloft's published customer case studies.

Reply-based deal creation. When a prospect replies to a Salesloft cadence, that event triggers a HubSpot workflow to create a Deal record and assign it to the rep who owns the contact. Instead of reps creating deals manually, every meaningful reply becomes pipeline automatically. It takes about 20 minutes to configure and saves real CRM hygiene work each week.

Attribution reporting. With the integration running, every Salesloft touchpoint appears on the HubSpot contact timeline with a timestamp. You can build a HubSpot report showing deals where outbound activity preceded the first inbound signal. It's not perfect attribution, but it's more defensible than a spreadsheet when someone asks which outbound efforts drove closed revenue.

Plan Requirements and the Zapier Fallback

The native Salesloft + HubSpot integration is available on Salesloft Essentials and above (starting around $75/user/month, per Salesloft's public pricing). HubSpot requires Sales Hub Starter or above. Teams on HubSpot Free can connect but only get one-way contact creation. Bidirectional activity sync requires a paid HubSpot tier.

Zapier handles the fallback for lower-tier teams: one-way logging of Salesloft cadence completions as HubSpot activities, on a 15-minute delay. On Zapier Professional at $49/month, it works fine for teams with under 200 active cadence contacts. Above 200, the native integration is worth the cost. The Zapier queue breaks under load and requires troubleshooting you don't want mid-campaign.

The honest take: if your outbound motion runs more than 200 active contacts at any point, the Zapier fallback will frustrate your ops team within a month. Pay for the native integration at that scale.

Want Research-Led Outreach Run For You?

Modern Inbound mines buyer language, builds account lists, writes outreach, manages client-owned inboxes, and routes qualified replies. Your team gets sales conversations, not another tool to operate.

Frequently Asked Questions

Does Salesloft have a native integration with HubSpot?

Yes. Salesloft's native HubSpot integration syncs contacts, activities, and lifecycle stages bidirectionally. It requires Salesloft Essentials or above and HubSpot Sales Hub Starter or above. HubSpot Free accounts only get one-way contact creation, not activity sync.

How often does Salesloft sync with HubSpot?

Salesloft polls HubSpot every 5 to 15 minutes for contact and lifecycle stage changes. Activity logging typically appears in HubSpot within 15 minutes of the event. Under heavy cadence load with thousands of active contacts, the sync queue can back up to 4 to 6 hours.

Why are duplicate contacts appearing in HubSpot after connecting Salesloft?

Duplicates appear when both Salesloft and HubSpot are set to create new contacts on import. Fix it by designating one system as the source of truth for net-new contacts. For outbound-first teams, set Salesloft to create and HubSpot to update-only. Then run HubSpot's deduplication tool to clean up existing duplicates.

Can Zapier replace the native Salesloft + HubSpot integration?

Zapier handles one-way activity logging from Salesloft to HubSpot on a 15-minute delay. It doesn't support bidirectional contact sync or lifecycle stage updates. For teams with under 200 active cadence contacts, Zapier works fine. Above that, the native integration handles the load and doesn't require manual babysitting.