Peopleid From Salesnavigatorid

What Peopleid From Salesnavigatorid does

Peopleid From Salesnavigatorid converts a Sales Navigator person identifier into the standard LinkedIn people ID so your enrichment pipelines stay unified across both surfaces. You get a single canonical ID that downstream actions, CRM syncs, and dedupe logic can rely on. It targets engineering teams stitching Sales Navigator lists into LinkedIn-first data models.

The action runs on the LinkedIn level and resolves the mapping through your authenticated LinkedIn session on Edges.

How it works

You pass in a Sales Navigator person identifier (the opaque ID from a Sales Navigator profile URL or lead list export). Edges issues a lookup against LinkedIn using your connected session, resolves the corresponding LinkedIn people ID, and returns it in a typed response. The operation is synchronous and lightweight — a single round-trip per ID.

Edges handles authentication, rate guidance, and pacing so your pipeline does not need to throttle client-side. If the Sales Navigator ID is invalid, revoked, or points to a profile you cannot access from your session, the action returns a typed error your workflow can branch on.

When to use Peopleid From Salesnavigatorid

Reach for this action whenever your pipeline mixes Sales Navigator extracts with LinkedIn-native data. CRMs, warehouses, and enrichment stacks almost always key on the LinkedIn people ID, not the Sales Navigator variant — so resolving the mapping up front saves you from maintaining two identifier spaces.

It is a core identifier primitive for the LinkedIn profile and company data API use case. Run it as a step between a Sales Navigator search and any LinkedIn extraction so the rest of your graph speaks one ID.

Use cases

• Unified enrichment pipelines. After Search Sales Navigator People returns leads, map each ID to the LinkedIn people ID before calling Extract LinkedIn Profile.
• CRM deduplication. When your CRM already stores LinkedIn IDs, resolve Sales Navigator exports to the same key so you avoid duplicate contact records.
• Cross-surface matching. Join a Sales Navigator saved list with LinkedIn post engagement data by reducing both sides to the LinkedIn people ID.
• Warehouse loads. Emit a single canonical people_id column into your warehouse regardless of which LinkedIn surface discovered the lead.
• Fallback routing. If a Sales Navigator ID fails to resolve, route the record to a manual review queue before it pollutes downstream jobs.

Best practices

• Resolve in bulk, cache forever. The mapping is stable. Store the mapping once in your warehouse or a key-value cache and skip the lookup on future runs.
• Handle unresolvable IDs explicitly. Profiles outside your network visibility or with revoked Sales Navigator access will not resolve; treat the typed error as a normal branch, not an exception.
• Chain after search, before extraction. The optimal sequence is search on Sales Navigator, map the IDs with this action, then extract on LinkedIn.
• Run async for large batches. For thousands of IDs, use async execution so your pipeline does not block on long runs.

Common questions

How many IDs can I map per run?

One per call. The action is a focused identifier primitive — parallelize at the pipeline level when you need throughput, and let Edges pace the requests for you.

Does this use my LinkedIn account or a shared pool?

Your LinkedIn account. Every mapping request is signed with the session of the LinkedIn account you connect to Edges, so resolution visibility matches what you would see manually.

Can I chain Peopleid From Salesnavigatorid with other Edges actions?

Yes. Most teams run it right after a Sales Navigator search and feed the resolved peopleId directly into Extract Linkedin User Contact Info or Visit LinkedIn Profile.

Get started

Add Peopleid From Salesnavigatorid to a workflow whenever your pipeline crosses the Sales Navigator / LinkedIn boundary. Wire it into Zapier, Make, n8n, or call it directly from the Edges API, and browse the full Actions library to pick the enrichment steps that follow.