Extract Sales Navigator Profile ID
Resolve a LinkedIn profile URL or /in/ handle to the Sales Navigator profile ID and matching profile URLs.
/v1/actions/linkedin-extract-salesnavigator-profile-id/run/liveEdges is not related to LinkedIn and is not an official LinkedIn product.
Input
Input parameters
A LinkedIn Profile URL should start with 'https://www.linkedin.com/sales/people/', 'https://www.linkedin.com/sales/lead/', 'https://www.linkedin.com/pub/' or 'https://www.linkedin.com/in/', and the handle must not start with 'ACo', 'ACw', or 'ACr' (Sales Navigator profile IDs).
A handle is included in linkedin_profile_url. E.g. for 'https://www.linkedin.com/in/{linkedin_profile_handle}'.
Integration
Array of identity UUIDs to use for the action
Mode for identity handling: direct, auto, or managed.
Description
What Extract Sales Navigator Profile ID does
Extract Sales Navigator Profile ID converts a public LinkedIn profile URL or /in/ handle into the Sales Navigator profile ID and both profile URLs. It is the reverse mapping of Extract LinkedIn Profile Handle.
The action runs on the LinkedIn level so you can take a LinkedIn-first list and join it to Sales Navigator searches, lead lists, and SN-native extracts.
How it works
You pass a linkedin.com/in/ or /pub/ URL, or the handle alone. Edges resolves sales_navigator_profile_id, sales_navigator_profile_url, and the matching LinkedIn ID, handle, and URL through your authenticated session.
The operation runs live. Handles that look like ACo/ACw/ACr Sales Navigator IDs are rejected by the input schema — pass a public LinkedIn handle, not an SN identifier.
When to use Extract Sales Navigator Profile ID
Use this when you already have public LinkedIn URLs and need Sales Navigator join keys — SN profile extract, SN connect, or InMail that requires an ACo identifier.
Typical placement is after a LinkedIn search or CRM import, before salesnavigator-extract-people or salesnavigator-connect-profile.
Use cases
- Take a CRM full of linkedin.com/in/ URLs and attach Sales Navigator IDs for SN-native enrichment.
- Prepare identifiers for salesnavigator-extract-people, visit, connect, or InMail.
- Join a LinkedIn-first warehouse table to Sales Navigator lead lists on sales_navigator_profile_id.
- Build a bidirectional ID map alongside Extract LinkedIn Profile Handle.
Best practices
- Cache by linkedin_profile_handle. Re-resolving on every run wastes credits.
- Do not pass Sales Navigator URLs here — use Extract LinkedIn Profile Handle for that direction.
- Chain into salesnavigator-extract-people when you need SN-native person fields such as email, phone, or recently_hired.
- Keep both IDs on the contact so later jobs can pick the cheaper or richer extract without remapping.
Common questions
What do I pass in?
A LinkedIn people URL (linkedin.com/in/ or /pub/) or the handle from that URL. The handle must not start with ACo, ACw, or ACr.
Does this extract the Sales Navigator profile?
No. It returns identifiers and URLs. Use Extract Sales Navigator Profile for the person record.
Do I need a Sales Navigator seat?
You need a connected identity that can resolve SN identifiers. SN-specific downstream actions still require a Sales Navigator seat on that identity.
Get started
Call Extract Sales Navigator Profile ID on LinkedIn URLs you already store, persist the ACo identifier, then compose with Extract Sales Navigator Profile or other SN actions from the library.
// Related
Other ways to work with People.
Try it with 100 free credits.
No card. Copy the snippet, paste your key, hit enter.