/v1/actions/salesnavigator-search-saved-people/run/liveSearch Saved People exports the leads you've saved in Sales Navigator as a structured list so you can keep your CRM, outreach tool, and warehouse aligned with what reps curate inside Sales Navigator. You get every saved person plus the metadata Sales Navigator attaches — headline, company, saved-list, tags, notes.
This action runs on the Sales Navigator level and is aimed at sales teams who treat Sales Navigator saved lists as their working queue and need that queue available downstream.
You call Search Saved People against your connected Sales Navigator account. Edges reads the saved-leads index through your authenticated session, paginates through the results, and returns a normalized list with profile URNs attached so you can chain follow-up actions.
The action runs on Edges infrastructure with safe pacing and no browser to manage. For typical saved-lead volumes the run is live; for very large libraries, async mode handles the pagination end to end.
Use Search Saved People when Sales Navigator is where reps curate their working list but the rest of your stack needs the same roster. It slots into the LinkedIn messaging & outreach API use case — the action keeps your outreach platform fed with the exact leads reps have flagged, without manual CSV exports.
It also doubles as the handoff primitive when a rep rotates territories or leaves.
Saved-people indexes are typically thousands of rows and the action paginates the full list. Use a saved-list or tag filter if you only need a slice.
Your connected Sales Navigator seat. Every request is signed with that session, so the export matches exactly what the seat's user sees when they open Sales Navigator.
Yes. A common chain is Search Saved People → Extract LinkedIn Profile for enrichment → Send Sales Navigator InMail or Message LinkedIn Profile for outreach.
Run Search Saved People from the Edges library, wire it into your CRM sync or outreach stack, or call it directly from the Edges API. Browse the full Actions library to see what to chain after the export.
curl -X POST "https://api.edges.run/v1/actions/salesnavigator-search-saved-people/run/live" \
-H "X-API-KEY: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"identity_ids": [
"your-identity-uuid"
],
"identity_mode": "direct",
"input": {
"sales_navigator_profile_search_url": "https://www.linkedin.com/in/example-profile",
"custom_data": "example_value"
},
"parameters": {
"exclude_crm_contacts": true,
"exclude_viewed_leads": true
}
}'[
{
"full_name": "John Doe",
"first_name": "John",
"last_name": "Doe",
"company_name": "Example Name",
"sales_navigator_company_id": "example-123",
"linkedin_profile_id": 42,
"connection_degree": 42,
"job_title": "Software Engineer at Example Corp",
"summary": "example_value",
"profile_image_url": "https://www.linkedin.com/in/example-profile",
"sales_navigator_search_url": "https://www.linkedin.com/in/example-profile",
"sales_navigator_profile_url": "https://www.linkedin.com/in/example-profile",
"linkedin_profile_url": "https://www.linkedin.com/in/example-profile",
"sales_navigator_profile_id": "example-123",
"sales_navigator_company_url": "https://www.linkedin.com/in/example-profile",
"location": "example_value",
"linkedin_people_post_search_url": "https://www.linkedin.com/in/example-profile",
"viewed": true,
"tenure_start": "example_value",
"tenure_end": "example_value",
"tenure_length": "example_value",
"recently_hired": true,
"recently_promoted": true,
"current_company": "example_value"
}
]