rc.searchPeople

Search for candidates in LinkedIn Recruiter Lite: by keyword, with Recruiter's Advanced Search filters, or by running a search you set up in Recruiter yourself. Add rc.doForPeople to open each candidate's profile or save them to a project.

The account needs a Recruiter Lite seat and Linked API's Plus plan, and a search with filter needs a supported LinkedIn interface language – see Recruiter Lite.

Constraints

⏺️ Root Start: allowed.

⬆️ Parent Actions: N/A.

⬇️ Child Actions: rc.doForPeople.

Parameters

{
  "actionType": "rc.searchPeople",
  "label": "backendSearch",
  "term": "kubernetes",
  "limit": 50,
  "filter": {
    "jobTitles": ["Backend Engineer", "Platform Engineer"],
    "jobTitlesScope": "current",
    "locations": ["Berlin, Germany"],
    "skills": ["Go", "PostgreSQL"],
    "yearsOfExperience": { "from": 3, "to": 10 },
    "seniority": ["senior", "manager"],
    "profileLanguages": ["en", "de"],
    "hidePreviouslyViewed": true
  },
  "then": { ... }
}

In AI assistants, the MCP tool is rc_search_people. The n8n action is Search people in Recruiter Lite; the Make module is Search People in Recruiter Lite.

ParameterDescription
labelOptional. Label included in workflow completion.
termOptional. Keywords, as you would type them in Recruiter's search box. Must contain a character other than a space.
filterOptional. Advanced Search filters, see Filters.
customSearchUrlOptional. URL of a Recruiter search results page, https://www.linkedin.com/talent/search?…, copied from the address bar after you set up the search in Recruiter. Runs that search as it is. Cannot be combined with term or filter.
limitOptional. Number of candidates to return, from 1 to 1000. Defaults to 25.
thenOptional. rc.doForPeople, to run actions for each candidate.

Give term, a filter with at least one value, or customSearchUrl. term and filter can be combined. A request with none of them, or with customSearchUrl next to term or filter, is rejected with invalidWorkflow. A scope such as jobTitlesScope, or a flag set to false, is not a value on its own.

Filters

All fields are optional. Several values in one field find candidates who match any of them; several fields together narrow the search, as in Recruiter's Advanced Search. Names are matched against Recruiter's suggestions – see How filters are applied.

FieldTypeFinds candidates
jobTitlesarray of stringswith these job titles
jobTitlesScopestringwhose jobTitles are currentOrPast (current or past), current, pastNotCurrent (past but not current) or past
locationsarray of stringsin these locations
locationsScopestringwhose locations are current, currentOrOpenToRelocate (current, or open to relocate there) or openToRelocateOnly (open to relocate there only)
postalCodeobjectnear a postal or ZIP code: code (required) and radiusMiles (optional): 1, 5, 10, 25, 50, 100 or 200
skillsarray of stringswith these skills
hasPassedSkillAssessmentbooleantrue: who passed a LinkedIn skill assessment
companiesarray of stringsat these companies
companiesScopestringwhose companies are currentOrPast, current, pastNotCurrent or past, as for jobTitlesScope
currentCompaniesarray of stringscurrently at these companies
pastCompaniesarray of stringsformerly at these companies
companySizesarray of stringsat companies of these sizes: selfEmployed, 1-10, 11-50, 51-200, 201-500, 501-1000, 1001-5000, 5001-10000, 10001+
schoolsarray of stringswho studied at these schools
graduationYearsobjectwho graduated in this range: from and to, years from 1900 to 2100
industriesarray of stringsin these industries
jobFunctionsarray of stringsin these job functions, see the list below
seniorityarray of stringsat these seniority levels: unpaid, training, entry, senior, manager, director, vp, cxo, partner, owner
yearsOfExperienceobjectwith this much experience: from and to, whole years from 0 to 30
firstNamesarray of stringswith these first names
lastNamesarray of stringswith these last names
profileLanguagesarray of stringswhose profile is in these languages, as LinkedIn language codes, such as en or es, see Profile languages
recentlyJoinedarray of stringswho joined LinkedIn recently: 1day, 2to7days, 8to14days, 15to30days, 1to3months
networkRelationshipsarray of stringsat these network distances from you: 1st, 2nd, 3rd+, groupMembers
isMilitaryVeteranbooleantrue: who are military veterans
groupsarray of stringsin these LinkedIn groups
recruitingActivityobjectwith this activity on your seat: type (required) and period (optional), see below
projectsarray of stringsin these projects of yours, by project name
notesarray of stringswhose notes on your seat contain these words
hidePreviouslyViewedbooleantrue: leaves out candidates your seat has already viewed, as Recruiter's Hide previously viewed option does
  • Ranges. yearsOfExperience and graduationYears need from, to or both, with from no greater than to.
  • false flags. hasPassedSkillAssessment, isMilitaryVeteran and hidePreviouslyViewed set to false add no filter.
  • recruitingActivity. type is messages, notes, projects, resumes or reviews. period is anytime (the default), pastDay, pastWeek, pastTwoWeeks, pastThreeMonths, pastSixMonths, pastYear or pastTwoYears.
  • Scopes. A scope applies to every value of its field. Without it, Recruiter's own default for that filter applies.
  • jobFunctions takes these values: Accounting, Administrative, Arts and Design, Business Development, Community and Social Services, Consulting, Customer Success and Support, Education, Engineering, Entrepreneurship, Finance, Healthcare Services, Human Resources, Information Technology, Legal, Marketing, Media and Communication, Military and Protective Services, Operations, Product Management, Program and Project Management, Purchasing, Quality Assurance, Real Estate, Research, Sales.

A value outside these lists or ranges is rejected with invalidWorkflow before the workflow starts.

Profile languages

profileLanguages takes LinkedIn's language codes, as Recruiter's Profile languages filter uses them, in lower case. A language name such as English is rejected with invalidWorkflow. The filter lists these languages:

CodeLanguage
csCzech
daDanish
deGerman
enEnglish
esSpanish
frFrench
inBahasa Indonesia
itItalian
jaJapanese
koKorean
msMalay
nlDutch
noNorwegian
plPolish
ptPortuguese
roRomanian
ruRussian
svSwedish
trTurkish
_oOthers

Two codes are not what you might expect: Indonesian is in, not id, and _o is the filter's Others option. A code the filter does not list fails the search with filterNotApplied.

How filters are applied

The action fills in Recruiter's Advanced Search as a person would and clicks Search. Each value must then appear as a filter pill that names it.

  • Companies, schools, skills, groups and projects take Recruiter's suggestion with exactly the name you gave. Failing that, a suggestion that continues your text at a word boundary is taken, such as Acme Robotics for Acme. Anything else fails the search.
  • Job titles take the suggestion with exactly the title you gave. Otherwise the title goes in as free text, which Recruiter searches for as typed: a longer title or LinkedIn's nearest one would be a different job.
  • Locations, industries and postal codes take the suggestion with the name you gave, or else LinkedIn's first suggestion for the full text.
  • First names, last names and notes go in as free text.
  • What was sent. After Search, the action also checks the search request Recruiter sent: the scopes of each value, the postal-code radius, and the recruiting-activity type and period.

A value Recruiter does not offer or did not apply fails the action with filterNotApplied, which names the field and the value, and no candidates are returned. Correct or remove the value: retrying the same request fails the same way.

Results and paging

  • Pages. Recruiter shows 25 candidates per page. The action reads pages until it has limit candidates or the results end.
  • No results. A search that finds nobody succeeds with an empty data array.
  • A later page fails. The action returns the candidates it has collected so far, as a success. If the failure is one of the account errors, the action fails with that error instead.
  • With child actions. Under rc.doForPeople, the child actions run for each candidate in turn, one after another. The search stops at the first child action that fails and returns the candidates collected so far; the last one carries the failed result in then. A candidate who was on the results page a moment ago cannot be missing, so a failed child action means a Recruiter page failed – possibly a warning screen that every further page load would make worse. The one exception is an InMail that Recruiter refuses for one candidate (inMailCreditRequired or inMailNotAvailable from rc.sendMessage): the search goes on with the next candidate.

Result options

  1. Successful search:
json
{
  "actionType": "rc.searchPeople",
  "label": "backendSearch",
  "success": true,
  "data": [
    {
      "name": "Jane Example",
      "recruiterProfileUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId1",
      "headline": "Senior Backend Engineer at Example Cloud",
      "location": "Berlin, Germany",
      "avatarUrl": "https://media.licdn.com/dms/image/v2/C4D03AQExample/profile-displayphoto-shrink_100_100/0/1600000000000",
      "viewerState": { "connectionDegree": "2nd" },
      "then": [ ... ]
    },
    {
      "name": "Alex Sample",
      "recruiterProfileUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId2",
      "headline": "Platform Engineer",
      "location": "",
      "avatarUrl": null,
      "viewerState": { "connectionDegree": null },
      "then": [ ... ]
    }
  ]
}
FieldMeaning
nameCandidate's full name.
recruiterProfileUrlCandidate's Recruiter profile, https://www.linkedin.com/talent/profile/…, without query parameters. Pass it as personUrl to rc.openPersonPage or rc.saveToProject. It opens in Recruiter, not on the public LinkedIn site.
headlineHeadline as the results show it, or an empty string.
locationLocation as the results show it, or an empty string.
avatarUrlProfile photo URL, or null without a photo.
viewerState.connectionDegree1st, 2nd or 3rd+, as Recruiter shows it next to the name, or null when it shows none or when the interface language is not supported.
thenOnly with child actions: an array with the result of each child action run for this candidate, in order.

label is included only if specified in the action parameters.

  1. Failed search:
json
{
  "actionType": "rc.searchPeople",
  "label": "backendSearch",
  "success": false,
  "error": {
    "type": "filterNotApplied",
    "message": "The following filters could not be applied: companies (\"Example Nonexistent Co\": LinkedIn offered no matching option). Remove or correct them and retry."
  }
}

Possible error.type values:

  • filterNotApplied – a filter value could not be applied; the message names each field and value. See How filters are applied.
  • recruiterSignInRequired, recruiterTwoStepVerificationRequired, recruiterMultipleSessionsDetected – the seat needs attention, see account errors.
  • limitExceeded – the account reached its rcSearchQueries limit.
  • unexpectedError – the search could not be completed.

Usage example

Workflow – open the profile of each of the first 2 candidates and read their details:

{
  "actionType": "rc.searchPeople",
  "term": "kubernetes",
  "limit": 2,
  "filter": {
    "jobTitles": ["Platform Engineer"],
    "locations": ["Berlin, Germany"]
  },
  "then": {
    "actionType": "rc.doForPeople",
    "then": {
      "actionType": "rc.openPersonPage",
      "basicInfo": true
    }
  }
}

Completion:

json
{
  "actionType": "rc.searchPeople",
  "success": true,
  "data": [
    {
      "name": "Jane Example",
      "recruiterProfileUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId1",
      "headline": "Platform Engineer at Example Cloud",
      "location": "Berlin, Germany",
      "avatarUrl": null,
      "viewerState": { "connectionDegree": "2nd" },
      "then": [
        {
          "actionType": "rc.openPersonPage",
          "success": true,
          "data": {
            "name": "Jane Example",
            "recruiterProfileUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId1",
            "headline": "Platform Engineer at Example Cloud",
            "location": "Berlin, Germany",
            "avatarUrl": null,
            "viewerState": { "connectionDegree": "2nd" },
            "publicUrl": "https://www.linkedin.com/in/jane-example",
            "industry": "Software Development"
          }
        }
      ]
    },
    {
      "name": "Alex Sample",
      "recruiterProfileUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId2",
      "headline": "Platform Engineer",
      "location": "Berlin, Germany",
      "avatarUrl": null,
      "viewerState": { "connectionDegree": "3rd+" },
      "then": [
        {
          "actionType": "rc.openPersonPage",
          "success": true,
          "data": {
            "name": "Alex Sample",
            "recruiterProfileUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId2",
            "headline": "Platform Engineer",
            "location": "Berlin, Germany",
            "avatarUrl": null,
            "viewerState": { "connectionDegree": "3rd+" },
            "publicUrl": "https://www.linkedin.com/in/alex-sample",
            "industry": null
          }
        }
      ]
    }
  ]
}