Recruiter Lite

The Recruiter Lite actions (rc.*) work in LinkedIn Recruiter Lite on the connected LinkedIn account. They search for candidates with Recruiter's Advanced Search filters, open Recruiter profiles, send InMail and replies, read the Recruiter inbox, and read and manage the seat's projects.

They need the Plus plan, like the Sales Navigator actions. A workflow that contains an rc.* action does not start on a Core seat: it fails with plusPlanRequired (see Executing Workflows).

Actions

People:

  • rc.searchPeople – searches for candidates by keyword, with Advanced Search filters, or from a Recruiter search URL.
  • rc.openPersonPage – opens a candidate's Recruiter profile and reads their details and your seat's activity with them.
  • rc.doForPeople – runs rc.openPersonPage, rc.saveToProject or rc.sendMessage for each candidate that rc.searchPeople finds.

Messages:

  • rc.sendMessage – sends a new InMail to a candidate, or a reply in an existing Recruiter conversation.
  • rc.syncInbox – enables monitoring of the Recruiter inbox, read through inbox polling and webhooks.

Projects:

SDKs, CLI and MCP

The Node and Python SDKs have a method for each Recruiter Lite action that can start a workflow, the CLI a command and the MCP server a tool:

ActionSDK methodCLI commandMCP tool
rc.searchPeoplercSearchPeoplelinkedin recruiter person searchrc_search_people
rc.openPersonPagercFetchPersonlinkedin recruiter person fetchrc_fetch_person
rc.sendMessagercSendMessagelinkedin recruiter message sendrc_send_message
rc.syncInboxrcSyncInboxlinkedin inbox sync --rcrc_sync_inbox
rc.retrieveProjectsrcRetrieveProjectslinkedin recruiter projectsrc_retrieve_projects
rc.retrieveProjectCandidatesrcRetrieveProjectCandidateslinkedin recruiter projects candidatesrc_retrieve_project_candidates
rc.saveToProjectrcSaveToProjectlinkedin recruiter person saverc_save_to_project
rc.createProjectrcCreateProjectlinkedin recruiter projects createrc_create_project
rc.renameProjectrcRenameProjectlinkedin recruiter projects renamerc_rename_project
rc.archiveProjectrcArchiveProjectlinkedin recruiter projects archiverc_archive_project

Each action page shows the call in its Node, Python and CLI tabs. n8n has the same ten actions under its Recruiter Lite resource, and Make has them as modules in its Recruiter Lite group; see n8n's actions and Make's modules.

rc.doForPeople has no method, command or tool. To run actions for each candidate of a search, pass the whole workflow: to customWorkflow in the SDKs, to linkedin workflow run in the CLI, or to the execute_custom_workflow MCP tool.

Recruiter Lite messages come back from inbox polling on every surface, tagged type: "rc", and every surface takes rc as the type filter: pollInbox in the SDKs, linkedin inbox get --type rc in the CLI, the MCP get_inbox tool, Poll inbox in n8n and Poll inbox for new messages in Make.

Seat requirements

  • An active Recruiter Lite subscription on the LinkedIn account.
  • A Recruiter sign-in in the account's cloud browser, once. On the platform Accounts page, choose Open Cloud Browser for the account, open LinkedIn Recruiter there and sign in. While the cloud browser is open, new workflows for the account do not start.
  • Two-step verification on the LinkedIn account. Recruiter requires it. Keep it on: turning it off locks the seat out of Recruiter.
  • A supported LinkedIn interface language for search filters, messages and projects: English, Spanish, German, French or Portuguese. rc.searchPeople with a filter, rc.sendMessage, rc.syncInbox and every project action read Recruiter's labels in the interface language. On any other interface language the workflow fails with languageNotSupported, as it does for every Linked API action, see Checking for result. The Recruiter inbox sync pauses too, see When the sync stops. rc.openPersonPage and a search without filter work in any interface language, but on an interface outside these five, viewerState.connectionDegree can come back null even when Recruiter shows a degree.

Until the seat is ready, the actions fail with one of the account errors below.

One seat, one Recruiter session

A Recruiter seat belongs to one person on one device, and LinkedIn checks it. When the seat is signed in to Recruiter somewhere else as well – your own browser, another device, a colleague – LinkedIn moves the older session to its "Multiple sessions detected on this account" notice and warns that the seat may be suspended. This does not always happen at once: in our tests it came about 20 minutes after the second sign-in. From then on, every Recruiter Lite action fails with recruiterMultipleSessionsDetected.

To fix it:

  1. Sign out of Recruiter everywhere except the account's cloud browser.
  2. Open the account's cloud browser (Open Cloud Browser on the platform Accounts page) and confirm LinkedIn's notice there with Continue to Recruiter.
  3. Retry the workflow.

So while Linked API works on a seat, use that seat's Recruiter only through Linked API. Repeated detections can get the seat suspended, and Linked API stops at this notice instead of retrying.

With the Recruiter inbox sync on, this matters all the time. After rc.syncInbox, Linked API opens Recruiter in the account's cloud browser regularly, even when none of your workflows runs, so any sign-in elsewhere conflicts with it. When the sync meets the notice, it holds: it opens no Recruiter page until you fix the cause and call rc.syncInbox again, which checks the seat and resumes the sync. See When the sync stops.

Account errors

These errors come from the seat, not from the action, so every Recruiter Lite action can return them. None of them is temporary: retrying before you fix the cause fails the same way. In rc.searchPeople they also stop the search and its child actions. In the background inbox sync they pause or hold the Recruiter sync, see When the sync stops.

error.typeCause and fix
recruiterSignInRequiredRecruiter asked to sign in. Sign in to Recruiter in the account's cloud browser, then retry. If the account has no Recruiter Lite subscription, add one first.
recruiterTwoStepVerificationRequiredRecruiter asked for two-step verification. Turn it on for this LinkedIn account.
recruiterMultipleSessionsDetectedLinkedIn detected Recruiter in use from more than one place on this seat. See One seat, one Recruiter session.

The message of each one:

  • recruiterSignInRequired: Sign in to LinkedIn Recruiter in this account's browser, then retry. If the account has no Recruiter Lite subscription, add one first.
  • recruiterTwoStepVerificationRequired: Enable two-step verification in this LinkedIn account to access Recruiter Lite.
  • recruiterMultipleSessionsDetected: LinkedIn detected Recruiter in use from more than one place on this seat and paused it. Sign out of Recruiter in every other browser and device, then open this account's browser, confirm LinkedIn's notice with Continue to Recruiter, and retry. Repeated detections can get the seat suspended.

Other warning screens

LinkedIn has more warning screens in Recruiter, such as the daily profile view limit ("Sorry, you've reached your daily profile view limit."), a security check or a restriction. Linked API does not tell them apart. An action that meets one usually fails with unexpectedError; rc.openPersonPage can return personNotFound instead, and a search whose later page fails returns fewer candidates as a success. Every new call loads Recruiter again. Before you call an action again after one of these results, look at Recruiter in the account's cloud browser (Open Cloud Browser on the platform Accounts page), never in another browser, which starts a second Recruiter session. If it shows a warning, wait until the warning is gone or deal with it there; the profile view limit resets at 00:00 UTC. Close the cloud browser before you call again: while it is open, new workflows for the account do not start.

Limits

Three limit categories cover Recruiter Lite:

  • rcPersonProfileViews – each rc.openPersonPage, each rc.saveToProject, which opens the candidate's profile too, and each rc.sendMessage, a new InMail or a reply, whatever its outcome. Only a new InMail checks this limit before it runs.
  • rcSearchQueries – each rc.searchPeople, however many result pages it reads.
  • rcMessages – each rc.sendMessage that sends a message, a new InMail or a reply.

Except for rc.sendMessage in rcPersonProfileViews, only successful executions count. Their defaults:

Categorydailyweeklymonthly
rcPersonProfileViews6004000120000, not enforced
rcSearchQueries1006003000, not enforced
rcMessages2550, not enforced50

LinkedIn itself allows a Recruiter Lite seat up to 2,000 unique candidate profiles a day, reset at 00:00 UTC, and it counts every new candidate a search shows, not only the profiles you open. rcSearchQueries counts a search once, however many result pages it reads, so these defaults alone do not keep the seat under LinkedIn's limit: at the default limit of 25, 80 searches can already show 2,000 candidates. Keep each search's limit and the number of searches to what you need. At the limit, Recruiter opens no new candidate profiles until the reset, see Other warning screens. Change the defaults on the platform or with limits.set.

A candidate opened with both rc.openPersonPage and rc.saveToProject counts twice, because the profile loads twice. Use rc.saveToProject alone when you only need the save.

Messages

  • InMail credits are spent only when you allow it. rc.sendMessage sends a message free only when Recruiter marks it free. A message that costs a paid InMail credit fails with inMailCreditRequired unless you set allowPaidCredit to true; nothing is typed or sent. See InMail credits.
  • One InMail starts a conversation, replies continue it. Recruiter refuses a new InMail to a candidate who already has a conversation with the seat: inMailNotAvailable. Reply in that conversation with threadId instead. A reply works only after the candidate accepted or replied to your InMail; before that it fails with messagingNotAllowed.
  • Check before you send again. rc.sendMessage clicks Send once and never repeats the click. An error after the click does not prove the message was not sent: it comes back as unexpectedError asking you to check, even when a warning page followed the click. Check the conversation before you retry.
  • The seat's signature. Recruiter adds the seat's own message signature to new InMails. It does not count toward the 1,900 characters.
  • Reading replies. Enable the Recruiter inbox with rc.syncInbox before you send: sending does not enable it, and messages from before the minute it was enabled are not imported. Its messages arrive through inbox polling and the inbox.* webhook events with type: "rc", and their threadId is what rc.sendMessage takes to reply.

Projects

  • Archive, not delete. Recruiter Lite has no way to delete a project. rc.archiveProject archives one, and rc.retrieveProjects lists only active projects.
  • Created with a name only. rc.createProject takes only name and creates a private project. Set the description afterwards with rc.renameProject. Job title and location cannot be set by these actions.
  • Check before you create again. rc.createProject clicks Create once and never repeats the click. An error after the click, recruiterMultipleSessionsDetected included, does not prove the project was not created. Before you retry a failed rc.createProject, check rc.retrieveProjects for a project with that name: a duplicate can only be archived.
  • Project IDs. A project's projectId is the number in its Recruiter URL, https://www.linkedin.com/talent/hire/<projectId>/overview. rc.retrieveProjects and rc.createProject return it.