Connect LinkedIn prospecting with the tools your team already uses

The integration layer LinkedNav covers

LinkedNav integrations are organized around the actual handoffs a sales team makes during a week: contacts go to CRM, leads go to email outreach, and AI assistants get tool access to plan and review work. Each integration covers one of those handoffs directly instead of forcing a generic webhook between unrelated tools.

• HubSpot: sync enriched LinkedIn contacts into a HubSpot Private App, with LinkedIn URL preserved on the contact record
• Instantly: push enriched leads into a specific Instantly campaign, with optional verification on import
• Claude MCP: expose LinkedNav contacts, lists, campaigns, signals, and enrichment as Model Context Protocol tools
• Claude Skills: upload custom skills that compose LinkedNav actions for repeatable AI workflows

Build versus buy: when MCP beats a Zapier hop

For a long time, the answer to "how do I get LinkedIn leads into our outbound stack" was to wire up Zapier and let a Zap fire on each new contact. That works for one-off plumbing, but it collapses under real volume: every lead is a separate Zap run, schema drift between tools breaks the integration silently, and there is no way for an AI assistant to reason about the workflow.

MCP changes the shape of the problem. Instead of triggering an event per lead, an AI assistant can call a LinkedNav tool directly to read a list, filter it, enrich the subset that matters, and push the result into HubSpot or Instantly as one bulk action. The integration becomes a conversation rather than a chain of fragile event handlers.