Search Saved Companies

Read companies saved in Sales Navigator to sync account lists with your CRM or outreach tools.

Edges is not related to LinkedIn and is not an official LinkedIn product.

API Endpoint

POST/v1/actions/salesnavigator-search-saved-companies/run/live

Parameters

Request parameters

Input Parameters

Integration Parameters

Guide

What Search Saved Companies does

Search Saved Companies reads the account list you've saved in Sales Navigator and returns it as a structured array so you can sync your ABM accounts to the CRM, outreach tools, or a warehouse. You get every saved company along with the metadata Sales Navigator attaches: industry, size, location, and the saved-list it belongs to.

This action runs on the Sales Navigator level and targets revenue and RevOps teams who manage target accounts inside Sales Navigator but need that list available everywhere else.

How it works

You call Search Saved Companies against the Sales Navigator account you connected to Edges. Edges reads your saved-accounts index through that authenticated session, paginates through the list, and returns a normalized payload — one row per saved company, with the Sales Navigator company ID attached so you can chain further actions.

It runs on Edges infrastructure, browser-less and rate-limited safely. Async mode is available for large saved lists; for typical volumes, live execution returns in a single round trip.

When to use Search Saved Companies

Use Search Saved Companies when Sales Navigator is the source of truth for your ABM list but downstream systems need that list too. It plugs into the LinkedIn people & companies data API use case — a single primitive that keeps CRM, warehouse, and outreach in sync with what reps save in Sales Navigator.

It also works as a recurring job that flags new saves to the rest of the stack.

Use cases

  • CRM sync. Mirror your saved Sales Navigator accounts to Salesforce or HubSpot on a nightly schedule, with the saved-list name mapped to a CRM tag.
  • Warehouse ingestion. Pipe saved companies into Snowflake or BigQuery to join with product telemetry or intent data.
  • ABM tier enforcement. Split saved lists by tier (Tier 1, Tier 2) and route outreach workflows off the list name.
  • Handoff cleanup. When a rep leaves, export their saved companies before the seat is reassigned.
  • Signal fan-out. When a saved company trips a signal, enrich it with other Edges actions immediately.

Best practices

  • Use list filters. Pass a saved-list filter so you only pull the rows your current workflow needs — it's faster and cleaner than post-filtering.
  • Chain into company extraction. Follow Search Saved Companies with Extract Company to hydrate each row with richer firmographics.
  • Schedule deltas. Run daily and diff against yesterday's output to capture only newly saved accounts.
  • Pair with people search. Hand the company IDs to Search Sales Navigator Company Employees to map the buying committee for each saved account.

Common questions

How many saved companies can I return per run?

The action paginates through the full saved index for the account, typically thousands of rows. For very large lists, filter by saved-list name to keep runs tight.

Does Search Saved Companies use my Sales Navigator account or a shared pool?

Your own seat. Edges signs the request with the Sales Navigator account you connected, so the saved list returned is exactly what that user sees when they open Sales Navigator.

Can I chain Search Saved Companies with other Edges actions?

Yes. Common chains include Search Saved Companies → Extract Sales Navigator Accounts List for extra metadata, or → Search Sales Navigator Company Employees to fan out into people lists per account.

Get started

Run Search Saved Companies from the Edges library, wire it into your CRM sync job, or call it directly from the Edges API. Browse the full Actions library to see what to chain after the sync.

Code Examples

bash
curl -X POST "https://api.edges.run/v1/actions/salesnavigator-search-saved-companies/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_company_search_url": "https://www.linkedin.com/in/example-profile",
    "custom_data": "example_value"
  }
}'

Output Example

[
  {
    "sales_navigator_search_url": "https://www.linkedin.com/in/example-profile",
    "company_name": "Example Name",
    "sales_navigator_company_url": "https://www.linkedin.com/in/example-profile",
    "description": "example_value",
    "category": "example_value",
    "number_employees": "example_value",
    "sales_navigator_employees_url": "https://www.linkedin.com/in/example-profile",
    "sales_navigator_company_id": "example-123"
  }
]

Explore More Actions

Discover other powerful LinkedIn automation actions in our library.