The native HubSpot + LinkedIn Sales Navigator integration connects in 5 minutes and looks like a complete solution. In practice, InMail conversations do not appear in the deal timeline, notes from Navigator are not synced to HubSpot, and reverse deal stage feedback into Navigator does not work. The SDR sees the conversation in Navigator, the AE opens the deal in HubSpot - and sees no context.
LinkedIn Sales Navigator + HubSpot is one of the most popular pairings in EU B2B. According to LinkedIn, Sales Navigator is used by more than 700,000 companies. The native integration with HubSpot takes 5 minutes to connect - but within 2-3 months teams discover structural limitations that are not visible during the initial setup. In HubSpot Community, the question “why are InMails not logged in the timeline” consistently ranks in the top 10 integration topics. This article breaks down the specific limitations of the native integration and the architecture of the right solution.
What the native integration actually does (honestly)
It is important to start with an honest description of what works - otherwise it is unclear where exactly the problem lies.
The native LinkedIn Sales Navigator + HubSpot integration provides:
- Sales Navigator widget in HubSpot. Directly in the contact or company card in HubSpot you can see LinkedIn information: job title, company, mutual connections, recent LinkedIn activity.
- Lead recommendations. Navigator suggests similar profiles based on your HubSpot contacts.
- Quick navigation. From a HubSpot card you can click through to open the profile in Navigator without searching.
- CRM Sync (with Advanced Plus). With Sales Navigator Advanced Plus (enterprise tier) two-way sync is enabled: contacts and companies are synchronized between platforms.
This is real value. The problem starts when the team expects the integration to solve the task of fully logging LinkedIn activities in the CRM.
Problem 1 - InMail activities not in deal timeline
Symptom: An SDR sends an InMail via Sales Navigator. There is no such event in the HubSpot deal timeline. The AE who picks up the deal has no idea what was said.
Root cause: LinkedIn restricts access to message content via API. InMail is LinkedIn’s internal messaging system, and they intentionally do not expose its content to third-party platforms. The basic native integration has no technical capability to retrieve InMail body text.
What CRM Sync (Advanced Plus) provides: with activity writeback enabled, InMails sent through Navigator are logged as an activity in HubSpot on the contact. But there are two caveats here:
- The activity is attached to the contact, not the deal. If a contact has multiple deals, the activity appears in the contact’s general timeline, but not in any specific deal.
- Each SDR must individually authenticate their LinkedIn account in HubSpot. If even one person has not done this - their InMails are not logged. This is a constant operational overhead.
The right solution: Use the HubSpot Engagements API to write LinkedIn activities manually via a custom integration. The SDR clicks a “Logged” button in a browser extension or in Navigator, a webhook sends the data to an intermediate service, which creates an engagement of type NOTE or CALL in HubSpot associated with the specific deal.
Problem 2 - Notes from Navigator are not synced to HubSpot
Symptom: An SDR takes notes in Sales Navigator - about a conversation, customer pain points, next steps. These notes live only in Navigator and never reach the HubSpot deal.
Root cause: Navigator Notes are a separate entity in LinkedIn, and the native integration does not include their synchronization in either the basic version or CRM Sync. LinkedIn API provides access to Notes only through the limited Sales Navigator Application Platform (SNAP) - a partner program with a separate approval process.
The scale of the problem: in a typical team of 5 SDRs, 200-500 conversation notes accumulate in Navigator per month. None of them are visible in HubSpot. The AE who receives the lead is working blind.
The right solution: Either discipline (copying notes manually - unrealistic at scale), or a custom integration via SNAP API if your vendor has access. The alternative is to move the notes process entirely into HubSpot and use Navigator only for prospecting.
Problem 3 - no deal stage sync back to Navigator
Symptom: A deal in HubSpot moved to “Contract Sent.” In Navigator, that contact’s profile still looks like a regular lead. The SDR keeps sending outreach to someone who is already in the final stages of negotiation.
Root cause: The native integration is one-directional on deal data. Navigator sees contacts and companies from HubSpot, but does not receive deal stage updates. This is not a bug - LinkedIn intentionally limits which CRM data flows into Navigator.
The consequence: duplicate outreach in late deal stages is a classic reason clients complain about sales “pressure” at a point when negotiations are already underway.
The right solution: A webhook in HubSpot on deal stage change -> intermediate service -> tag or list update in Navigator via Sales Navigator API (if available). Or - create a custom property in HubSpot “Navigator Status” that the SDR updates manually, with automation for notifications.
Problem 4 - GDPR and EU Data Residency
This problem is less obvious, but critical for EU teams.
The situation: HubSpot EU Data Center stores data in the EU (Ireland, Germany). LinkedIn is a US company, and Sales Navigator data is processed on servers in the US. When the native integration synchronizes contact data between HubSpot EU and Sales Navigator, a cross-border transfer of EU subjects’ data to US servers occurs.
Legal context: After Schrems II and the introduction of the new EU-US Data Privacy Framework (DPF), this is legally permissible if LinkedIn is certified under DPF (at the time of writing - yes). But for companies in highly regulated industries (finance, healthcare), this point requires verification with the legal team.
The practical consequence: some EU companies restrict the synchronization of personal data with Navigator, leaving the integration in view-only mode without contact export. This significantly reduces the value of the native integration.
The right architecture via LinkedIn API
A complete solution is built on three layers:
Layer 1 - Data collection. A browser extension or Sales Navigator SNAP integration that captures activities (InMails, notes, profile views) and sends them to an intermediate service.
Layer 2 - Processing. An intermediate service (Node.js/Python microservice) receives events, enriches them with data (mapping LinkedIn ID -> HubSpot contact ID), and creates or updates objects in HubSpot via HubSpot API.
Layer 3 - HubSpot records. Through Engagements API v3, engagement records of type NOTE are created with attribution to the specific deal (not just the contact). The deal stage via webhook updates the corresponding tag in Navigator.
The critical point: associating the engagement with the deal, not just the contact. In the native integration this does not work. In a custom integration - it is implemented via associations in HubSpot API:
{
"engagement": {"type": "NOTE"},
"associations": {
"dealIds": [12345],
"contactIds": [67890]
},
"metadata": {
"body": "InMail from LinkedIn Navigator: [message text]"
}
}This record appears in the deal timeline, not just the contact timeline.
Real case
EU B2B SaaS company, 8 SDRs + 4 AEs, Sales Navigator Advanced Plus, HubSpot Sales Hub Enterprise.
Problem: SDRs work in Navigator, AEs work in HubSpot. At handoff the SDR verbally recaps the context. Loss of context is the cause of 30-40% of “cold” intro calls by AEs with leads that the SDR had already warmed up.
Solution architecture: Chrome extension for SDRs with a “Log to HubSpot” button. Clicking it captures the InMail or note and sends it to an intermediate service. The service creates a NOTE engagement via HubSpot API attached to the deal. AEs see the full conversation history directly in the deal timeline.
Additionally: when the deal stage in HubSpot changes to “Closed Won” or “Closed Lost,” a tag is automatically set on the Navigator contact - SDRs see the status without having to check HubSpot.
Result: time spent on handoff briefings dropped from 15-20 minutes to 2-3 minutes per deal. Activity history is fully available in HubSpot.
Frequently asked questions
Do you need Sales Navigator Advanced Plus for the native integration?
For the basic widget (viewing LinkedIn data in HubSpot) Sales Navigator Advanced is sufficient. For CRM Sync with two-way contact synchronization and activity writeback, Advanced Plus is required - this is an enterprise tier with custom pricing, typically from $1,600/user/year. Without Advanced Plus, you get a view-only integration with no activity logging.
Why are InMails not being logged even though I have CRM Sync connected?
Most likely the problem is individual authentication. CRM Sync requires each HubSpot user to separately authorize their LinkedIn account in the CRM Sync settings. If a user has not completed this step - their activities are not synced. Check Settings -> Integrations -> Sales Navigator in HubSpot and confirm that each SDR has the status “Connected.”
Can you import contacts from LinkedIn into HubSpot via the native integration?
No. The native integration does not allow bulk import of contacts from LinkedIn into HubSpot. This is a LinkedIn API limitation - they protect profile data from bulk export. Contacts can be added one at a time via the Navigator widget in HubSpot, or via CSV export from Navigator and manual import.
How do the native integration limitations relate to the HubSpot + Zapier anti-pattern?
If you try to solve the InMail logging problem via Zapier (for example, through Email Parser or LinkedIn triggers), you will encounter the same API limitations plus rate limits. Writing to HubSpot via Zapier will reach the contact, but not the deal - and the problem partially persists. HubSpot + Zapier is a separate anti-pattern with predictable scaling issues.
Is it worth paying for Sales Navigator Advanced Plus for CRM Sync?
Only if native CRM Sync is sufficient for your needs (contact-level logging without deal association). At $1,600+/user/year for 5 SDRs that is $8,000/year just for CRM Sync. In most cases, a custom integration via HubSpot Engagements API is cheaper to build and offers more capabilities, including deal timeline association.
Summary
The native HubSpot + LinkedIn Sales Navigator integration covers the task of superficially viewing LinkedIn data in the CRM. It does not solve three key B2B sales tasks:
- Logging InMail in the deal timeline (not just the contact timeline)
- Syncing notes from Navigator to HubSpot
- Reverse deal stage transfer to Navigator
If your SDRs actively work in Navigator and your AEs work in HubSpot, the native integration will not be enough. A custom architecture via HubSpot Engagements API is needed, with activities associated with deals.
If you currently have this setup and see a gap in context transfer between SDRs and AEs - describe the problem to the Exceltic.dev team. We will analyze the architecture and estimate the scope of work for your stack.