Your GTM belongs in gitRegister
Skills
Find the accounts and the people · One-off

Extract sales navigator search

Extract a Sales Navigator search that is bigger than one extraction can hold: count it, split it under the cap, merge the pieces back to the fewest searches, and load them into a handful of models, for accounts (1,000 per search) or people (2,500 per search).

Installation
Install extract-sales-navigator-search and follow its SKILL.md, starting from https://api.getcargo.io/INSTALL.md
Paste it into Claude Code, Cursor, Codex, Gemini CLI, Devin or Replicas.

No account needed to install. A new Cargo account starts with 100 free credits, no card.

Say this to your agent

Extract every software company with 51–200 employees in the US from Sales Navigator.

Illustrative output #

Fictional records, to show the shape of what comes back.

Search after mergingCount
Software · 51–200 · California excl. San Francisco · growth -100..5941
Software · 51–200 · California excl. San Francisco · growth 5..1000702
Software · 51–200 · San Francisco873
Software · 51–200 · Texas, Florida, Georgia948
Software · 51–200 · New York, Massachusetts932
Software · 51–200 · Washington, Illinois, Pennsylvania, Virginia811
Software · 51–200 · rest of US · growth -100..0908
Software · 51–200 · rest of US · growth 0..1000726

6,841 counted, 8 searches in one model, 6,567 rows extracted. 24 count calls (6 credits) and 1,313.4 credits of extraction (6,567 × 0.2).

What it costs #

ActionCredits
salesNavigator.searchCompanyMetrics0.25
salesNavigator.searchPersonMetrics0.25
Extraction through fetchAccountSearch or fetchLeadSearch, per row returned0.2

Counting is cheap; extraction is the bill. A 50,000-account market costs a few hundred count calls and ~10,000 credits of extraction. People models run three times, and each run bills the rows it returns, so budget up to three times the count for people until the sample below shows what a re-run actually bills.

Never run this across a full list on the first attempt. Run steps 1–4 (counting only), then extract one small search (a few hundred rows) to confirm the URLs extract as counted. Show the user the number of searches, models and expected rows with the credit estimate, and get the go before the full step 5.

Worth knowing #

  • Workspace limits are separate from the per-search cap. A workspace has a rolling 24-hour allowance of Sales Navigator search requests, shared by counts and extraction pages (~25 rows a page). A model that hits it errors and keeps only its preview; a rerun starts over. Before a large run, estimate the requests (one per count, one per ~25 extracted rows, times three for people) and ask Cargo to confirm or raise the allowance.
  • An error saves nothing. Extraction is all or nothing per model run, so smaller models lose less when something breaks.
  • number_employees on an extracted account is the page’s own label, not the headcount Sales Navigator filtered on. Re-measure size downstream if it matters.
  • A union never exceeds its parts. That is what makes packing by sum safe without re-counting every candidate merge; step 4 re-counts the winners.
Version1.0.0
LicenseMIT
Source
For
  • RevOps
  • GTM engineering
  • Sales development
Integrations

Give your agents a runtime

Bring the agents you have.Start free, deploy in one command.