.svg)
Overview
Your sales engagement data lives in Salesloft. Your customer records live in HubSpot. And somewhere in between, critical context disappears. Reps make calls without seeing recent email opens. Marketing sends nurture campaigns to prospects already deep in active sequences. Managers build reports from data that is already stale by the time they export it.
The Salesloft-HubSpot integration promises to fix this by creating a bi-directional sync between your sales engagement platform and CRM. But here is the reality: turning on the native integration is the easy part. Getting it to actually improve your workflows requires understanding what data flows where, configuring field mappings correctly, and building processes that leverage the connected systems.
This guide walks through everything GTM engineers need to know about integrating Salesloft with HubSpot: from initial setup and field mapping configuration to advanced use cases and common pitfalls. We will cover what the integration actually does, what it does not do, and how to build reliable workflows on top of it.
What the Salesloft-HubSpot Integration Actually Does
Before diving into setup, it helps to understand the scope of what you are working with. The native integration handles three primary functions:
Contact and Lead Sync
The integration creates a bi-directional link between HubSpot contacts and Salesloft people. When a rep adds someone to Salesloft, the system can create or update the corresponding HubSpot contact. When contact data changes in HubSpot, those updates can flow back to Salesloft. This keeps basic firmographic and demographic data consistent across both systems.
Activity Logging
Every email sent, call made, and meeting booked through Salesloft gets logged as an activity on the corresponding HubSpot contact timeline. This gives your entire team visibility into sales engagement without requiring manual data entry. For teams focused on coordinating their CRM and sequencer workflows, this eliminates the biggest source of missing activity data.
Deal and Opportunity Association
The integration can associate Salesloft activities with HubSpot deals, giving managers visibility into which engagement activities are tied to pipeline. This is essential for any meaningful sales performance analytics.
The integration does not sync custom Salesloft fields to HubSpot custom properties automatically. It does not trigger HubSpot workflows based on Salesloft cadence events. And it does not provide real-time sync. Understanding these limitations upfront saves hours of troubleshooting later.
Setting Up the Integration
The initial connection takes about 15 minutes, but the configuration decisions you make here determine whether the integration actually works for your use cases.
Connect the Accounts
In Salesloft, navigate to Settings > Integrations > CRM and select HubSpot. You will need admin access to both platforms. Authenticate with HubSpot using an account that has the necessary scopes: contacts, deals, engagements, and automation permissions.
Configure Sync Direction
Decide whether you want one-way or bi-directional sync. For most teams, bi-directional sync makes sense: HubSpot remains the system of record for contact data, while Salesloft is the source of truth for engagement activities. However, if you have strict data governance requirements, you might want HubSpot to only receive data without pushing changes back.
Map Standard Fields
The integration provides default mappings for common fields: name, email, phone, company, and job title. Review these carefully. The defaults work for simple setups, but if you have customized your HubSpot properties or Salesloft fields, you will need to adjust the mappings. See our guide on HubSpot field mapping for details on structuring your property architecture.
Configure Activity Types
Specify which Salesloft activities should log to HubSpot. Most teams want all activities logged, but you might exclude certain internal-only activities or test sends. Each activity type can be mapped to a specific HubSpot engagement type.
Set Duplicate Handling Rules
Configure how the integration handles duplicate contacts. Options include merge, skip, or create new. For teams dealing with duplicate prevention in their GTM stack, this setting is critical for maintaining clean data.
Field Mapping Strategy for GTM Teams
The default field mappings get you started, but strategic field mapping is what makes the integration actually useful for workflows. Here is how to think about it.
Core Contact Fields
Standard fields like name, email, and phone should sync bi-directionally. Use HubSpot as the source of truth for firmographic data (company size, industry, revenue) since this data typically comes from enrichment sources. Use Salesloft as the source of truth for engagement-related fields (last contacted date, sequence status).
| Field Type | Source of Truth | Sync Direction | Notes |
|---|---|---|---|
| Basic contact info | HubSpot | HubSpot to Salesloft | Name, email, phone updates flow from CRM |
| Firmographic data | HubSpot | HubSpot to Salesloft | Industry, size, revenue from enrichment |
| Engagement status | Salesloft | Salesloft to HubSpot | Sequence stage, last touch, etc. |
| Lead score | HubSpot or External | To Salesloft | For prioritization in sequences |
| Custom research | Varies | Bi-directional | Depends on where research originates |
Custom Fields for Advanced Workflows
If you are doing trigger-based outreach or personalization at scale, you need custom fields synced between systems. Common examples include:
- Personalization snippets: Custom research or talking points generated for each contact
- Sequence reason: Why this contact was added to a specific sequence (for reporting)
- ICP score: Fit score from your lead scoring model
- Buying signals: Intent data or trigger events that prompted outreach
For teams using Clay or other enrichment tools, this is where Salesloft field mapping becomes essential. You need a clear path from enrichment data to CRM to sequencer.
Common Workflow Patterns
Once the integration is configured, you can build workflows that leverage the connected data. Here are the patterns that work best.
Inbound Lead Routing to Sequences
When a new lead comes into HubSpot, use workflows to flag the lead for Salesloft import. Then configure Salesloft to automatically add flagged contacts to the appropriate sequence based on properties like industry or company size. This pattern works well for teams doing inbound-to-outbound lead nurturing.
Engagement-Triggered CRM Updates
Use Salesloft's activity sync to trigger HubSpot workflows. For example, when a contact replies to a sequence email (logged to HubSpot as an activity), trigger a workflow that notifies the assigned rep, updates the lead status, and pauses any marketing automation. This prevents the common problem of marketing emails going out to prospects in active sales conversations.
Deal-Based Sequence Enrollment
For deal progression sequences (demo follow-up, proposal follow-up, closed-lost re-engagement), trigger enrollment based on HubSpot deal stage changes. When a deal moves to "Demo Scheduled," automatically add the contact to your demo follow-up sequence in Salesloft. This ensures consistent engagement without requiring reps to manually manage sequence enrollment.
Multi-Touch Attribution Reporting
With all Salesloft activities logged to HubSpot, you can build attribution reports spanning marketing and sales touchpoints. This is valuable for teams optimizing their outbound campaign management.
HubSpot stores Salesloft activity details in engagement properties. You can use these in workflows by checking for specific text in the activity body or subject. For example, trigger a follow-up task when an activity contains "left voicemail" to ensure no voicemail goes without email follow-up.
Common Issues and How to Fix Them
Even well-configured integrations hit issues. Here are the most common problems and their solutions.
Sync Delays
The integration does not sync in real-time. Standard sync intervals range from 5-15 minutes. If you need faster sync for specific use cases, consider using the Salesloft API to push updates directly, or implement a middleware solution that handles near-real-time sync.
Missing Activities
If activities are not appearing in HubSpot, check these common causes:
- The contact does not exist in HubSpot (activities only log to existing contacts)
- Email address mismatch between systems
- Activity type is not configured for sync
- Rate limits are being hit during high-volume periods
Duplicate Contacts
Duplicates typically occur when the same person exists in both systems with slightly different data (different email formats, company name variations). Review your duplicate handling rules and consider running a deduplication process before enabling bi-directional sync. Our guide on automated CRM deduplication covers this in detail.
Field Mapping Conflicts
When both systems try to update the same field, conflicts occur. The integration typically uses last-write-wins logic, which can cause data to flip-flop. Solve this by designating a clear source of truth for each field and configuring one-way sync for those fields.
Advanced Integration Patterns
For teams ready to go beyond basic sync, these patterns unlock more sophisticated workflows.
Webhook-Based Real-Time Triggers
Both Salesloft and HubSpot support webhooks. By setting up webhooks for key events (email reply, call completed, deal stage change), you can trigger actions in near-real-time without waiting for sync cycles. This is essential for buying signal-based outreach where timing matters.
Enrichment Pipeline Integration
For teams using enrichment tools like Clay, the integration becomes part of a larger data pipeline: Lead enters HubSpot > Clay enriches > Data syncs to Salesloft > Rep adds to sequence > Activities sync back to HubSpot. Understanding how to sync Clay data to your CRM is the foundation for this pattern.
Sequence Performance Feedback Loop
Use HubSpot's reporting capabilities to analyze which sequences perform best for different segments. Then feed those insights back into your sequencing strategy. For example, if your data shows that three-step sequences outperform five-step sequences for enterprise prospects, adjust your Salesloft cadences accordingly. Teams focused on optimizing sequencer settings should build this feedback loop into their regular review process.
What Changes at Scale
Running the Salesloft-HubSpot integration for a 10-person sales team is straightforward. Running it for 100 reps across multiple business units, with data flowing from dozens of sources, is a different challenge entirely.
At scale, three problems compound. First, sync latency becomes visible. When thousands of activities need to log per hour, the 5-15 minute sync window creates noticeable gaps in data freshness. Reps check HubSpot and see outdated information. Managers pull reports with incomplete data. Second, field mapping complexity explodes. Different teams need different custom fields. Sales uses one lead scoring model, marketing uses another, and customer success has their own qualification criteria. Maintaining consistent field mappings across all these use cases becomes a full-time job. Third, troubleshooting becomes impossible. When sync issues occur, finding the root cause among millions of records requires tooling that neither platform provides natively.
What you actually need is a context layer that sits above these point-to-point integrations. A unified system that maintains the canonical version of every contact, every activity, and every data point, then pushes the right information to the right system at the right time.
This is what platforms like Octave are built for. Instead of relying on native integrations to keep HubSpot and Salesloft in sync, Octave maintains a unified context graph that orchestrates data across your entire GTM stack. When a contact's data changes, Octave ensures every system has the update immediately. When you need to answer "what happened with this account," you get the complete picture, not just what one system happened to capture. For teams running AI-powered SDR workflows or complex multi-tool outbound motions, this infrastructure layer is the difference between fragile integrations and reliable automation.
FAQ
No. The integration requires HubSpot Sales Hub Professional or Enterprise. You need the workflows and custom property features that are not available in free or Starter tiers.
Partially. Individual activities (emails, calls) sync as engagements. However, cadence-level data like "which cadence is this contact in" or "cadence step number" requires custom field mapping or API work to surface in HubSpot.
Configure your sync settings to create new HubSpot contacts when they do not exist. Alternatively, run a bulk import of Salesloft contacts to HubSpot before enabling sync to ensure all records have matching entries.
Salesloft supports connecting to one HubSpot portal per Salesloft team. If you have multiple HubSpot portals (common in holding company structures), you will need multiple Salesloft teams or a middleware solution to route data appropriately.
The native integration does not support HubSpot custom objects. You will need to use the APIs of both platforms or a third-party integration tool to sync custom object data.
Conclusion
The Salesloft-HubSpot integration is a foundational piece of any modern sales tech stack. When configured correctly, it eliminates manual activity logging, keeps contact data consistent across systems, and enables workflows that span both platforms.
The key to success is treating the integration as infrastructure, not a set-and-forget checkbox. Define clear sources of truth for each data type. Build field mappings that support your actual workflows. Test thoroughly before scaling. And most importantly, understand the limitations so you can architect around them when your needs outgrow what native integrations provide.
For teams building sophisticated GTM operations, this integration is a starting point. The real value comes from layering enrichment data, lead scoring, trigger-based automation, and unified reporting on top. Get the foundation right, and everything else becomes easier to build.