LinkedNav Claude Connector Setup 2026

Last updated: May 2026

A Claude Connector is a pre-built bridge between Claude and an external tool. Once you add LinkedNav as a Connector, Claude can:

You do all of this in plain English, in a Claude conversation. No clicking through dashboards, no copying data between tools, no writing code. The Connector is the simplest possible way to use Claude on top of LinkedNav.

The Claude MCP integration is the underlying technical layer — 80+ programmatic tools that any MCP-compatible client (Claude Desktop, custom agents, Skills) can call. The Claude Connector is a packaged consumer experience built on top of MCP, designed for non-technical users. You don't see the tools or the prompts — Claude just works when you ask it LinkedIn-outreach-related questions.

Most SDRs and sales operators should use the Connector. Developers building custom agents should use the MCP layer directly. The Connector is the path of least resistance.

The Connector setup is the simplest integration LinkedNav offers. No JSON config, no API key handling, no command-line tools.

In a new Claude conversation, type:

``` List my LinkedNav campaigns. ```

If you see your campaign list, you're connected. If you see "Connector not found" or "Authentication failed," check the API key in Step 2.

Try one of these:

``` Show me the top 5 high-intent leads from the last 24 hours. ```

``` How many pending replies are waiting for my approval right now? ```

``` What was my best-performing campaign last week? ```

If these return useful answers, you're done. The Connector is fully configured.

These are the prompts production SDR teams use day-to-day. Copy them, adapt to your style, save them as reusable Claude artifacts.

``` Run my daily LinkedNav check-in:

Format as a bulleted briefing I can read in 60 seconds. ```

Run this every morning at 9 AM. Replaces 15-20 minutes of manual dashboard review.

``` Show me all pending replies. For each, display:

Group by sentiment. After I review, I'll tell you which to approve, regenerate, or deny. ```

Run this once or twice per day. The batch review is way faster than clicking through pending replies one at a time.

``` Audit my campaigns for the last 14 days:

Skip campaigns with under 50 sends in the period. ```

Run this every Monday morning. Surfaces what to fix without spending an hour manually comparing campaigns.

``` I'm launching a new campaign for [describe your offer in 2-3 sentences].

Help me:

Don't activate anything yet — just propose. I'll review and approve. ```

Use this whenever you're spinning up campaigns for a new offer or new vertical.

``` Help me set up Social Listening for these competitors:

For each, suggest the right qualification rules so we only auto-import people who match our ICP, not random engagers. ```

The setup conversation lets Claude pre-qualify your Social Listening config so you don't drown in noise.

``` Give me a deep dive on [prospect name or LinkedIn URL]:

```

Use this before high-stakes manual outreach on senior prospects.

``` Summarize my LinkedNav week:

```

Run this every Friday afternoon as you wrap up the week.

You've read this far because clicking through dashboards is slow. LinkedNav's Claude Connector lets you run signal-driven LinkedIn outreach as a conversation. The Signal Agent finds high-intent prospects within 24 hours of their activity; Claude helps you triage, draft, approve, and ship.

Start free →    See Claude Connector docs →

The Connector unlocks workflows that are awkward in the LinkedNav dashboard alone:

You're between two demos and have 5 minutes. Open Claude, ask "Any urgent pending replies?" Approve the 3 that matter. Back to your next demo. Total time: 90 seconds. Same task in the dashboard: 5-7 minutes of clicking.

"Compare campaign A vs campaign B's performance." Claude pulls metrics for both, normalizes them, surfaces what's actually different. Same task in the dashboard: open two browser tabs, eyeball the numbers, compute differences mentally, miss something subtle.

"Reply rate dropped on campaign X this week. What changed in the prompts since last week, and what should I try?" Claude pulls prompt history, compares to high-performing campaigns, suggests a specific change. The dashboard alone makes this multi-step diagnosis hard.

A new hire opens Claude, asks "Walk me through how to spin up my first LinkedNav campaign." Claude leads them through ICP definition, prompt selection, sender configuration, and launches a small test campaign. Replaces 1-2 hours of dashboard onboarding.

"Has any of my campaigns ever touched [prospect name]?" Claude searches across all campaigns, returns the answer with full history. The dashboard requires checking each campaign individually.

"Format my weekly results into an executive summary I can paste into Slack." Claude pulls numbers, formats appropriately, includes context. Saves 20-30 minutes of manual report writing.

These aren't theoretical — they're how SDR teams actually use the Connector once they get past the first week.

The Connector may need to be added as a custom connector pointing to LinkedNav's MCP endpoint. Follow the setup at linkednav.com/claude-linkedin-automation for the latest URL and configuration.

Your API key is wrong, expired, or revoked. Generate a fresh key in linkednav.com/app/integrations and update it in Claude's Connector settings.

You may have multiple LinkedNav workspaces (common at agencies). Check that the API key belongs to the workspace you intended. Switching workspaces means generating a new key from that workspace.

Be more specific in your request. Instead of "show me my data," try "show me my LinkedNav campaigns active this month sorted by reply rate." Specificity helps Claude pick the right tool.

The Connector intentionally requires explicit confirmation for outbound actions (approving pending replies, sending messages, launching campaigns). This is the safety architecture — you'll always be asked to confirm before something goes out. If Claude isn't asking, the action probably isn't actually outbound (e.g., creating a draft is internal, sending it requires approval).

Claude has request size limits. If you ask for "all contacts" on a workspace with 50,000 contacts, the response is too big. Scope your request: "Show me the 50 most recently surfaced leads from the high-priority campaigns."

Settings → Connectors → LinkedNav → Disconnect. The API key remains valid in LinkedNav (revoke it separately at linkednav.com/app/integrations if you want to fully cut access).

If you're rolling out the Connector to a 3-10 person SDR team, here's the cleanest playbook:

Pick the most curious / fastest-adopter SDR on the team. Have them set up the Connector in 5 minutes (Steps 1-4 above). Run the Daily Morning Briefing prompt for the first time. Observe what works and what they want to adjust.

Most pilot SDRs report that the morning briefing alone changes how they start their day — instead of opening 4 dashboards, they ask Claude one question and get the same information in 60 seconds.

Capture the prompts that worked best for the pilot SDR. Standardize them in a shared doc (Notion, Slack canvas, or shared Claude artifacts). Most teams end up with 8-12 reusable prompts after the first week.

Each SDR generates their own API key from their LinkedNav account, adds the Connector in 5 minutes, and starts with the team's prompt library. The first time they run "Daily Morning Briefing" it just works — they don't have to reinvent the prompt.

After two weeks, review which prompts are getting used and which aren't. Trim the unused ones; add new ones for newly-discovered workflows. The library evolves as the team's needs sharpen.

The Connector is great for routine, repeated workflows. It's not the right tool for everything. Cases where you should stay in the LinkedNav app directly:

The right pattern: dashboard for setup, exploration, and visual review; Connector for daily routine work and conversational triage. They complement each other.

Every LinkedNav differentiator is accessible through natural language:

No. The Connector is specifically designed for non-technical SDRs and sales operators. You need to be able to copy/paste an API key into a settings page; that's it. No JSON, no command-line, no code.

Yes — Claude with web browsing can read your LinkedIn feed but can't act on LinkedNav's product surface. The Connector lets Claude do things in LinkedNav: pull signal leads, approve replies, manage campaigns. It's the difference between Claude reading a webpage versus Claude operating a tool.

No. The Connector is included in all LinkedNav tiers (Free $0, Standard $49, Pro $99). You only pay for the LinkedNav subscription level you need; the Connector is bundled.

Yes. Each team member generates their own API key from their LinkedNav account and adds the Connector to their own Claude. Conversations stay private per person; the underlying LinkedNav data is shared at the workspace level.

The Connector has approval gates by design — Claude can draft but you have to confirm before any message is sent. The pending-approval queue is the safety architecture; the Connector respects it. You'll always be asked to confirm before LinkedNav sends anything.

Yes — the Connector setup is account-level, so once configured on any Claude client, it's available everywhere you log in. Mobile is great for quick triage ("any urgent pending replies?") between meetings.

Yes — the Connector lets Claude read your LinkedNav data including contacts, campaigns, and conversation history. This is necessary for the AI workflows; Claude needs context to be useful. Treat your Claude conversations accordingly. For especially sensitive prospects (NDAs, regulated industries), don't use the Connector — handle those manually.

The Connector relies on Claude's availability. If Claude is down, you lose the conversational interface but LinkedNav itself continues running normally — campaigns send, signals surface, the Unibox accepts replies. Just open the LinkedNav app directly until Claude is back.

Yes. The Connector and Claude Skills work together — Skills are pre-engineered prompts that use the Connector's tool surface. Drop in a Skill, get one-click access to a packaged workflow without writing the prompt yourself.

The Connector is a managed wrapper around the MCP layer. For non-technical users, the Connector is the right entry point — minimal setup, immediate utility. For developers building custom agents or wanting fine-grained control over tool calls, the MCP server setup is the better path. Most SDR teams start with the Connector and only graduate to direct MCP usage if they have specific custom workflows that the standard surface doesn't handle.

Most SDRs report 30-60 minutes per day saved on routine workflows (morning triage, pending reply review, daily campaign check). At an SDR team of 5, that's 12-25 hours per week of recovered productive time. The Connector pays back its setup cost in the first day.

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