Docs / Search

`count_people_sales_navigator`

Count how many people match a Sales Navigator search, without returning them.

This action only reads. It changes nothing, so it is safe to try. It is part of the Agent plan.

What you give it

Input	What it is	Where to get it
`keywords` optional	Text. Free-text keywords searched across all profile fields (title, headline, about, company).	You write it.
`titles` optional	A list (text). Job titles, e.g. ["Chief Technology Officer","VP of Engineering"]. Matched as OR'd keywords — pass variants to go broad.	You write it.
`locations` optional	A list (text). Person locations in plain English, e.g. ["United States","London"]. Resolved to LinkedIn regions automatically.	You write it.
`industries` optional	A list (text). Company industries in plain English, e.g. ["Software","Financial Services"].	You write it.
`companies` optional	A list (text). Current companies by name, e.g. ["Google","Stripe"]. Each name is looked up and the top match used — when you already have LinkedIn company ids (search_companies / list_funding_signals return companyId), pass companyIds instead.	You write it.
`companyIds` optional	A company id. Current companies by LinkedIn company id — the companyId values search_companies / list_funding_signals return (up to 100). Exact: no name lookup, so no same-name mix-ups. Combine with seniorities and changedJobs / postedOnLinkedIn to get the decision-makers at signal companies who just moved / are posting.	Run `search_linkedin_companies` and use `results[].id` from its answer. 5 more places to get it `search_companies` → `companies[].companyId` `list_funding_signals` → `companies[].companyId` `search_linkedin_sales_navigator_companies` → `results[].id` `get_profile_details` → `workExperience[].companyId` `get_company` → `id`
`functions` optional	A list (text). Job functions/departments, e.g. ["Engineering","Sales","Marketing"].	You write it.
`seniorities` optional	A list (text). Seniority levels, e.g. ["CXO","VP","Director","Manager"] (owner/partner, cxo, vice_president, director, experienced_manager, entry_level_manager, strategic, senior, entry_level, in_training).	You write it.
`companyHeadcounts` optional	A list (text). Company size bands. Valid: self-employed, 1-10, 11-50, 51-200, 201-500, 501-1000, 1001-5000, 5001-10000, 10001+.	You write it.
`changedJobs` optional	True or false. Only people who recently changed jobs (buying signal).	You write it.
`postedOnLinkedIn` optional	True or false. Only people who recently posted on LinkedIn (active/reachable signal).	You write it.
`companyMinRevenueMillions` optional	A number. Only people at companies with at least this annual revenue, in millions (e.g. 10 = $10M+) — use it to target companies that can afford the user's price. LinkedIn uses fixed brackets (0, 0.2, 1, 2.5, 5, 10, 20, 50, 100, 500, 1000); other values widen to the nearest one. The companies are matched on the same industries / companyHeadcounts / locations (as HQ location). Revenue is LinkedIn's estimate — companies without one are left out.	You write it.
`companyMaxRevenueMillions` optional	A number. Only people at companies with at most this annual revenue, in millions (e.g. 100 = up to $100M). Same brackets as companyMinRevenueMillions.	You write it.
`revenueCurrency` optional	Text. ISO currency of the revenue band, e.g. "USD" (default), "EUR", "GBP".	You write it.

Call it

curl -X POST https://api.heyreagent.com/v1/actions/count_people_sales_navigator \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{"titles":["Head of Sales"]}'

The same call in JavaScript

const response = await fetch("https://api.heyreagent.com/v1/actions/count_people_sales_navigator", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_KEY",
    "content-type": "application/json",
  },
  body: JSON.stringify({
    "titles": [
      "Head of Sales"
    ]
  }),
});
const answer = await response.json();
console.log(answer);

The same call in Python

import requests

response = requests.post(
    "https://api.heyreagent.com/v1/actions/count_people_sales_navigator",
    headers={"Authorization": "Bearer YOUR_KEY"},
    json={
        "titles": ["Head of Sales"],
    },
)
print(response.json())

The same call in n8n

Add an HTTP Request node and fill it in like this:

Method	`POST`
URL	`https://api.heyreagent.com/v1/actions/count_people_sales_navigator`
Send Headers	On. Name `Authorization`, Value `Bearer YOUR_KEY`
Send Body	On. Body Content Type `JSON`, Specify Body `Using JSON`, then paste the body below

{
  "titles": [
    "Head of Sales"
  ]
}

Put your own key where it says YOUR_KEY. New here? Start with your first call.

What you get back

When it worked, the answer is { "ok": true, "result": { … } }. Inside result:

`total`
`source`
`note`

A field that does not apply to an answer is left out, or is null.

When it did not work, the answer is { "ok": false, "error": "…", "message": "…" }. What each error means.

Good to know

Free, and the same filters as search_people_sales_navigator: use it to size a search before paying for one.

In Claude or ChatGPT

Once connected, ask in your own words. The assistant sees this action as a tool with the same name, count_people_sales_navigator, and the same inputs.