Docs / Search

`search_people`

Search people on ordinary LinkedIn by plain words, a place name and connection degree.

This action only reads. It changes nothing, so it is safe to try.

What you give it

Input	What it is	Where to get it
`keywords` optional	Text, up to 300 characters. Words to search for, e.g. "head of sales fintech".	You write it.
`location` optional	Text, up to 100 characters. A place name, e.g. "Berlin" or "United Kingdom".	You write it.
`network` optional	A list (one of: first, second, third), up to 3. Limit to these connection degrees from you: first, second, third.	You write it.
`limit` optional	A number, 1 to 10. Max people to return (1–10, default 10).	You write it.
`cursor` optional	A cursor. nextCursor from the previous call, to get the next page. Keep the other arguments the same.	The `nextCursor` from the last answer of `search_people`.
`connectionId` optional	A connection id. Which of your LinkedIn accounts to act from (its id from list_linkedin_accounts). Omit to use your first live one.	Run `list_linkedin_accounts` and use `accounts[].id` from its answer. 15 more places to get it `get_my_profile` → `accounts[].connectionId` `list_connections` → `connections[].connectionId` `list_connections` → `summary.accounts[].connectionId` `list_sent_invitations` → `pendingInvitations[].connectionId` `preview_withdraw_invitations` → `breakdown[].linkedinConnectionId` `list_conversations` → `inbox[].linkedinConnectionId` `list_inmail` → `inmail[].connectionId` `get_inmail_credits` → `accounts[].connectionId` `list_sales_navigator_contracts` → `accounts[].connectionId` `who_is_waiting_on_me` → `waitingOnYou[].connectionId` `who_went_cold` → `coldConversations[].connectionId` `connections_never_messaged` → `summary.accounts[].connectionId` `get_usage` → `connectionId` `get_conversation` → `connectionId` `get_inmail_conversation` → `connectionId`

Call it

curl -X POST https://api.heyreagent.com/v1/actions/search_people \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{"keywords":"head of sales"}'

The same call in JavaScript

const response = await fetch("https://api.heyreagent.com/v1/actions/search_people", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_KEY",
    "content-type": "application/json",
  },
  body: JSON.stringify({
    "keywords": "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/search_people",
    headers={"Authorization": "Bearer YOUR_KEY"},
    json={
        "keywords": "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/search_people`
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

{
  "keywords": "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:

`returned`
`total`
`hasMore`
`nextCursor`	A cursor. Other actions take it.
`applied`
`people`
`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

location is a place NAME here; the action looks its id up itself. Every other LinkedIn filter is on search_linkedin_people.
At most 10 rows per call: LinkedIn's page size for this search.

In Claude or ChatGPT

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