Last updated: May 2026

TL;DR: The LinkedNav + HubSpot integration syncs signal-driven LinkedIn outreach to your CRM as it happens — 24-hour-fresh intent leads land as HubSpot contacts, Unibox replies post to deal timelines, AI-drafted follow-ups trigger lifecycle stage moves, and meeting bookings auto-advance pipeline. Setup takes ~15 minutes. This guide walks through 5 production-grade workflow patterns SDR teams ship in week one, the per-team-size cost math, and the 7 gotchas that break naïve setups.

The integration lives at linkednav.com/hubspot-linkedin-integration. LinkedNav Standard is $49/month; Pro with native sender rotation is $99/month. HubSpot Sales Hub Starter ($20/seat) or Professional ($100/seat) is required on the HubSpot side.

Most SDR teams already have HubSpot as the system of record for pipeline. The question isn't whether to integrate LinkedIn outreach with HubSpot — it's how cleanly the integration produces a single source of truth for prospect activity.

Three reasons LinkedNav + HubSpot is meaningfully different from generic LinkedIn → HubSpot integrations in 2026:

When LinkedNav's Signal Agent surfaces a lead — say, a VP of Sales who engaged with three competitor posts in the last 24 hours — the context that triggered the signal travels with the contact into HubSpot. The deal record shows why the SDR reached out, not just that they did. AEs picking up the deal three weeks later still see "engaged with [Competitor X] post on May 3" as a property on the contact, which changes how they qualify the conversation on the discovery call.

Most LinkedIn automation tools push send/accept/reply counts to HubSpot but leave the actual conversation content in the tool's inbox. When the AE wants to read what the prospect said in week 2, they have to log into both systems. LinkedNav's Unibox syncs the full reply text into HubSpot's contact timeline, so the conversation is visible alongside email and phone activity in one view.

LinkedNav's AI-drafted reply workflow queues messages as pending until a human approves them. When the SDR clicks approve, the message sends and logs to HubSpot in one operation. Tools that draft AI messages externally and require manual logging into HubSpot afterward double the operator's workload at scale.

The integration is bidirectional. Here's exactly what moves between systems:

The integration is OAuth-based; no manual API key management on the HubSpot side.

LinkedNav suggests sensible defaults, but most teams customize at least 2-3 mappings:

Create these custom properties in HubSpot before mapping (Settings → Properties → Create property).

Decide which LinkedNav events move the contact's lifecycle stage in HubSpot. The defaults work for most teams:

If your HubSpot org uses non-default lifecycle stages, override here. The mappings live in the integration settings page within LinkedNav.

For SDR teams using HubSpot deals (recommended), configure:

Add a test contact to a small LinkedNav campaign (10 prospects max). Watch HubSpot for:

If any step fails, re-check the field mappings. The integration logs every sync attempt in LinkedNav's integrations dashboard for debugging.

The integration unlocks new workflows that aren't possible with manual LinkedIn → HubSpot data entry. Five that mature SDR teams adopt within the first week:

The problem: Static-list outbound contacts land in HubSpot with no explanation of why they're in the funnel. AEs ask "why is this person here?" and SDRs scramble to recall.

The workflow: LinkedNav's Signal Agent surfaces a lead based on competitor engagement. LinkedNav creates a HubSpot contact with signal_type = "competitor_engagement" and signal_context = "Engaged with Acme Corp launch post on May 3". Three weeks later when the AE picks up the conversation, they see exactly why the SDR reached out.

Why it matters: Reduces AE qualification time per call by ~5 minutes (no context reconstruction). At an SDR team of 5 generating 30 meetings/week, that's 2.5 hours of AE time recovered weekly.

The problem: SDRs maintain conversation history in LinkedIn DMs, copy-paste relevant messages into HubSpot notes manually. The lag between actual conversation and CRM record is 1-3 days; AEs see incomplete history.

The workflow: Replies arrive in LinkedNav's Unibox and sync immediately to HubSpot's contact timeline as "LinkedIn message" engagements. AI-generated reply suggestions appear in Unibox; SDR approves/edits/sends; the sent message also logs to HubSpot. Zero duplicate data entry.

Why it matters: SDR time saved on CRM admin (typically 30-45 min/day per rep), plus AEs getting real-time conversation context for hot inbound.

The problem: Many SDRs only create HubSpot deals after the discovery call is booked, losing conversion data on conversations that almost-but-not-quite booked.

The workflow: Configure the integration to auto-create a HubSpot deal at "Initial Conversation" stage the moment a prospect replies in Unibox. Deal amount defaults to $0; AE updates after qualifying call. Pipeline reporting now captures every conversation, not just the booked ones.

Why it matters: Cohort analytics on conversation-to-meeting and conversation-to-pipeline conversion rates. Most SDR teams discover their reply-to-meeting rate is 35-50%, not the 70%+ they assumed.

The problem: Bringing a current customer back into outbound by accident. Embarrassing, brand-damaging, often missed because the SDR didn't check HubSpot before adding contacts to a campaign.

The workflow: HubSpot → LinkedNav sync runs every 15 minutes. Any contact whose HubSpot lifecycle stage is "Customer" or "Opportunity" is automatically excluded from new LinkedNav campaign add-list operations. SDRs can't accidentally re-target someone the company is already working with.

Why it matters: Prevents the common multi-team pipeline accident. Customer-success-style cross-team incidents drop to near-zero.

The problem: Closed-lost reasons in HubSpot are gold for ICP refinement, but SDR teams rarely consume them — their target list is already built.

The workflow: When a deal moves to "Closed Lost — Bad Fit" in HubSpot, LinkedNav tags the contact and downweights the prospect's profile attributes (title, industry, company size) in future Signal Agent surfacing. Over time, the Signal Agent learns from real lost-deal data what your ICP isn't.

Why it matters: Continuous ICP refinement based on ground truth (won/lost data) instead of static ICP definitions that drift over quarters.

You've read this far because volume isn't working anymore. LinkedNav's Signal Agent finds prospects showing real intent in the last 24 hours — competitor engagers, topic posters, recent job changers — so your team messages people while their interest is still active. Connect HubSpot in 15 minutes; signal context flows into your CRM automatically.

Start free →    See HubSpot integration docs →

The integration produces clean, auditable funnel reporting in HubSpot. Most SDR teams build a custom dashboard with these reports:

Group contacts by signal_type property. Report on conversion rate from signal-surfaced contact to meeting booked. Typical breakdown:

The signal types performing best inform where to allocate Signal Agent attention. Job-change signals consistently outperform other types in B2B SaaS.

Group by linkednav_sender_account. Report acceptance rate, reply rate, meetings per sender. Identifies which LinkedIn accounts in your rotation are pulling weight and which need attention (low acceptance often signals the sender's profile needs strengthening).

Group deals by linkednav_campaign. Report on pipeline created and closed-won revenue per campaign. Most SDR teams discover that 60-70% of LinkedIn-sourced revenue comes from 20-30% of campaigns; doubling down on the high-performers compounds.

Custom HubSpot report on the time delta between first reply (timeline event from Unibox) and meeting booked. Faster velocity correlates with higher close rate. SDRs maintaining sub-48-hour reply-to-meeting times close 2.3× more deals on average.

Note: LinkedNav Pro at $99 covers up to ~10 rotated senders flat. HubSpot Sales Hub Pro at $100/seat is per-user. The combined per-sender cost is dominated by HubSpot at scale, not LinkedNav.

For agencies running on HubSpot Free + LinkedNav, the integration still works at zero HubSpot cost — engagement events log to the timeline, but custom properties for signal context require Sales Hub Starter ($20) at minimum.

Mistakes mature teams have already made (so you don't have to):

If you map signal_type to a custom property that doesn't exist yet in HubSpot, the sync silently drops the value. Always create properties in HubSpot first, then configure the mapping.

If your HubSpot portal has marketing automation that moves contacts through lifecycle stages on email opens, the LinkedNav stage moves can conflict. Audit existing workflows before enabling LinkedNav lifecycle automation; resolve precedence rules explicitly.

LinkedNav matches contacts to HubSpot by email. If a prospect's HubSpot record uses a personal email and LinkedNav enriches with their work email, you get duplicates. Solution: enable HubSpot's deduplication rules (by LinkedIn URL or by name+company) before turning on the integration.

The "exclude closed-customer contacts from outbound" sync runs forward — it doesn't retroactively pull closed-lost contacts from active campaigns. After enabling, do a one-time audit to remove existing closed-deals from active LinkedNav campaign lists.

HubSpot Free CRM allows custom properties but caps engagement events per contact. High-volume LinkedIn outreach can hit those limits within weeks. Sales Hub Starter ($20/seat) lifts most relevant limits.

If you're using a separate Sales Navigator import workflow into HubSpot in parallel with LinkedNav, you can end up with stage-move race conditions. Pick one source of truth for LinkedIn → HubSpot moves; let the other be read-only.

If your HubSpot has multiple deal pipelines (new business, renewal, expansion), LinkedNav's auto-deal-creation defaults to the first pipeline. Configure the target pipeline explicitly or you'll create deals in the wrong pipe and skew reporting.

Most teams considering this integration are migrating from one of three patterns. The migration path differs:

The most common starting point. SDRs run LinkedIn outreach in some tool (Waalaxy, HeyReach, manual) and copy-paste relevant context into HubSpot notes by hand. The migration:

Time recovered: 30-45 min/SDR/day on CRM admin.

Teams running Waalaxy or Dripify with custom Zapier zaps to push events to HubSpot. This works but is fragile:

The migration: enable LinkedNav's native HubSpot integration, run in parallel with the Zapier zaps for 7 days, validate data parity, then disable the zaps. Most teams report 40-60% reduction in CRM data quality issues post-migration.

HubSpot ships a native LinkedIn Sales Navigator integration that displays profile data inside CRM and tracks InMail credits. It does not run outbound campaigns or sync conversation content. Teams running only this integration are doing manual outbound — the migration to LinkedNav layered on top is additive (Sales Navigator integration stays for profile display, LinkedNav adds the execution layer).

Different B2B verticals optimize the integration differently:

These patterns aren't exclusive — teams adopt and adapt based on their actual sales motion.

The integration isn't generic — it's designed around LinkedNav's specific architecture. The four differentiators each produce specific HubSpot artifacts:

24-hour intent signals — every signal-surfaced contact carries signal_date and signal_context properties, so HubSpot reports can filter by signal freshness. Stale leads (signal > 7 days old) can be auto-tagged for re-evaluation.

AI follow-ups with human approval — approved replies log as outbound engagements with the AI suggestion preserved as a custom note, so AEs can see what the AI proposed vs what the SDR actually sent. Useful for AI-coaching SDRs and refining LinkedNav's prompts over time.

Comment campaigns — comment events log as a separate engagement type in HubSpot ("LinkedIn comment"), distinguishing comment-based touches from connection-request touches in funnel reporting. Many teams discover comment campaigns generate 30-40% of inbound replies despite being a smaller share of total touches.

Auto-withdraw — when a connection request auto-withdraws unaccepted, an engagement note logs the withdrawal. Helps with post-mortem analysis of why specific outreach didn't convert.

Yes, the OAuth integration connects to any HubSpot tier including Free CRM. Engagement events log to contact timelines on Free, but custom properties for signal context (used by most workflow patterns) require Sales Hub Starter ($20/seat/month) or higher. For teams evaluating LinkedNav with a basic HubSpot setup, Free + Starter ($20) is the lowest-cost combined entry point at $49/month total.

No. LinkedNav creates new contacts when matching by email fails, and updates only the LinkedNav-specific custom properties on existing contacts. Standard HubSpot fields (job title, company, lifecycle stage source-of-truth) are preserved unless you explicitly enable LinkedNav lifecycle automation, which can move stages forward.

LinkedNav's data residency is configurable for EU customers, and the OAuth scopes requested are limited to the specific scopes needed for the integration (contacts, deals, engagements, lists). The integration honors HubSpot's GDPR deletion: when a contact is deleted in HubSpot, LinkedNav receives the webhook and removes the contact from active campaigns.

The current integration is HubSpot-native. Salesforce sync is supported via webhook + Zapier or via the LinkedNav API. For dual-CRM setups (rare but exists at large enterprises), one CRM should be designated source of truth and the other read-only for LinkedNav.

Yes, but only after the SDR approves the draft. Pending drafts (before approval) stay in LinkedNav's Unibox and don't pollute the HubSpot timeline. Once approved, the sent message logs as an outbound engagement; the original AI draft is preserved as an internal note for AI-coaching purposes.

Every 15 minutes for list membership changes and lifecycle stage updates. Webhook-driven events (contact deleted, deal stage changed) propagate within seconds. Bulk operations (importing a 5,000-contact list) sync within 1-2 minutes.

Yes — HubSpot workflows can call LinkedNav's API to add contacts to specific LinkedNav campaigns when HubSpot conditions are met (e.g., "lifecycle stage = MQL AND industry = SaaS → add to LinkedNav SaaS campaign"). This is the foundation of mature signal-driven outbound where HubSpot triggers and LinkedNav executes.

HubSpot's native LinkedIn Sales Navigator integration covers profile data display in CRM and InMail credit tracking. It doesn't run outbound campaigns, surface intent signals, or draft AI follow-ups. LinkedNav + HubSpot is complementary — most teams run both, with HubSpot's native integration handling Sales Navigator profile sync and LinkedNav handling all outbound execution.

Replies sync to HubSpot's timeline within ~30 seconds of arriving in Unibox. AEs receive the conversation context essentially in real time, which matters for fast inbound handoffs.

Yes. LinkedNav Pro at $99 supports native sender rotation across multiple LinkedIn accounts under a single workspace, all syncing to one HubSpot portal. Each contact gets a linkednav_sender_account property identifying which LinkedIn account made the touch, so reporting can break down sender performance without splitting HubSpot portals.

If a connected LinkedIn account is restricted by LinkedIn, LinkedNav pauses outbound from that sender automatically and posts an internal note to LinkedNav admins. HubSpot data already synced is not affected; new outbound from that sender stops until the restriction lifts. The conservative volume defaults (≤100 invites/week per account) and server-side execution reduce restriction risk meaningfully — the integration's reliability is downstream of account safety.

No. The HubSpot integration is included in all LinkedNav tiers (Free, Standard $49, Pro $99). HubSpot tier costs are independent — Sales Hub Starter ($20/seat/month) is the practical minimum for full workflow patterns. There are no per-sync fees or API call charges from LinkedNav's side.

LinkedNav's published benchmarks for B2B offers are 40-60% connection acceptance rate and 25-55% reply rate on signal-targeted campaigns running Signal Agent and AI-drafted personalization. With those numbers landing as HubSpot timeline events, reporting becomes auditable: every signal source produces a measurable funnel from acceptance → reply → meeting → pipeline. Static-list outbound (no signal layer) typically caps at 25-35% acceptance and 8-15% reply regardless of CRM integration quality. The integration ensures those numbers are visible to your sales leadership in HubSpot reports rather than buried inside the LinkedIn tool.

Sales Navigator Automation · Social Listening · Multiple Senders · Unified Inbox · Buying Signals

If you are weighing whether to replace Sales Navigator entirely: