rc.sendMessage

Send a message from LinkedIn Recruiter Lite. There are two forms:

  • A new InMail to a candidate, by their Recruiter profile URL, with a subject and a text. Use it on its own, or under rc.doForPeople for each candidate of a search.
  • A reply in an existing conversation, by its threadId, with a text only.

A message that costs a paid InMail credit is sent only when you set allowPaidCredit to true.

The account needs a Recruiter Lite seat, Linked API's Plus plan and a supported LinkedIn interface language – see Recruiter Lite. To read the replies, enable the Recruiter inbox with rc.syncInbox before you send: sending does not enable it, and the inbox does not import messages from before the minute it was enabled.

Constraints

⏺️ Root Start: allowed, when personUrl or threadId parameter is provided.

⬆️ Parent Actions: rc.doForPeople.

⬇️ Child Actions: N/A.

Parameters

A new InMail:

{
  "actionType": "rc.sendMessage",
  "label": "inmail1",
  "personUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId1",
  "subject": "Data Engineer role in Amsterdam",
  "text": "Hi Jane, I'm hiring a Data Engineer for our Amsterdam team and your pipeline work stood out. Would you be open to a short call next week?"
}

A reply in an existing conversation:

{
  "actionType": "rc.sendMessage",
  "label": "reply1",
  "threadId": "2-RXhhbXBsZVJlY3J1aXRlclRocmVhZA==",
  "text": "Thanks, Jane! Does Thursday at 15:00 work for you?"
}

In AI assistants, the MCP tool is rc_send_message. The n8n action is Send message in Recruiter Lite; the Make module is Send Message in Recruiter Lite.

ParameterDescription
labelOptional. Label included in workflow completion.
personUrlAt the root, the candidate to send a new InMail to. A Recruiter profile URL, https://www.linkedin.com/talent/profile/…, such as recruiterProfileUrl from rc.searchPeople or rc.retrieveProjectCandidates, or the personRecruiterUrl of a Recruiter Lite inbox message. A public profile URL (linkedin.com/in/…) is rejected with invalidWorkflow. Not allowed under rc.doForPeople, which supplies it.
threadIdAt the root, the conversation to reply in, instead of personUrl: the threadId of a Recruiter Lite message from inbox polling or an inbox.* webhook event. Up to 58 characters. Not allowed under rc.doForPeople.
subjectRequired for a new InMail, including under rc.doForPeople. A single line of 1 to 200 characters. Not accepted with threadId: a reply has no subject.
textRequired. Message text, from 1 to 1,900 characters.
allowPaidCreditOptional. true allows the action to spend a paid InMail credit when Recruiter asks for one. Defaults to false. Set it only when the user has explicitly approved spending a paid InMail credit on this message; on inMailCreditRequired, ask the user instead of retrying with it set.

At the root, give exactly one of personUrl and threadId. Both, neither, or a subject with threadId are rejected with invalidWorkflow.

Each successful message counts one rcMessages limit; a refused message does not. Every execution also counts one rcPersonProfileViews, whatever the outcome – a new InMail or a reply, sent, refused or failed. Only a new InMail (personUrl), which opens the candidate's Recruiter profile, checks that limit before it runs: when it is used up, the action fails with limitExceeded and loads nothing. A reply by threadId is not blocked by it.

InMail credits

Recruiter decides whether a message costs a paid InMail credit, and the action reads its decision before it types anything:

  • A new InMail is free only when Recruiter marks it free. Recruiter shows "Free to InMail" in the message window, for example for a 1st-degree connection. Any other InMail costs a credit.
  • A reply in a conversation is free unless Recruiter shows an InMail credit count in that conversation's message window. Then it costs a credit too.
  • A paid message is refused unless allowPaidCredit is true, with inMailCreditRequired. The action closes the empty message window; nothing is typed or sent, and no credit is spent.
  • With allowPaidCredit set to true, the message is sent and the credit is spent. The result says so: creditUsed is true.

If Recruiter's credit information cannot be read, the action fails with unexpectedError and sends nothing.

Who can be messaged

  • One InMail starts the conversation. Once a candidate has a conversation with the seat, Recruiter does not allow a new InMail to them: its Send button is disabled before anything is typed. The action then fails with inMailNotAvailable, even with allowPaidCredit set to true. Reply in the existing conversation with threadId instead. The same refusal can mean the seat has no InMail credits left.
  • A reply works once the candidate has answered. You can reply in a conversation only after the candidate accepted or replied to your InMail. Before that, the reply fails with messagingNotAllowed.
  • The conversation must be in Recruiter's Inbox or Awaiting reply. A threadId that is in neither folder fails with messagingNotAllowed. This includes a conversation archived in Recruiter.

In all these cases nothing is typed or sent.

Sending behaviour

  • One click. The action clicks Send once and never repeats the click.
    • A new InMail counts as sent once Recruiter closes the message window and shows its "message sent" notice for this candidate.
    • A reply counts as sent once your new message appears in the conversation with your text.
  • Check before you send again. An error that comes back after the Send click does not prove the message was not sent: the click may have landed just before a browser stall, or before LinkedIn moved the tab to a warning page. So from the click on, every failure comes back as unexpectedError with a message that asks you to check, listed below. So does a send that was lost because the browser worker stopped or timed out. If LinkedIn moved the tab to a warning page right after the click, that message ends with Recruiter then showed <type>., for example recruiterMultipleSessionsDetected. Before you retry an rc.sendMessage that failed with unexpectedError, check the conversation. Look at the candidate's Messages in the account's cloud browser (Open Cloud Browser on the platform Accounts page), never in another browser, which starts a second Recruiter session, or poll the inbox after its next sync if rc.syncInbox is enabled. Otherwise the candidate may get the message twice.
  • The seat's signature. Recruiter adds the seat's own message signature, a Recruiter setting, to new InMails. The recipient sees it. It does not count toward the 1,900 characters, and the action neither adds nor removes it.
  • The candidate's public profile. When a new InMail opens a Recruiter profile that links to the candidate's public LinkedIn profile, Linked API remembers that link. Inbox polling by the candidate's public URL can then find their Recruiter conversation.

Result options

  1. Successful sending:
json
{
  "actionType": "rc.sendMessage",
  "label": "inmail1",
  "success": true,
  "data": {
    "creditUsed": false
  }
}
FieldMeaning
creditUsedtrue if the message spent a paid InMail credit, which happens only with allowPaidCredit set to true; false if it was free.

label is included only if specified in the action parameters.

  1. Failed sending:
json
{
  "actionType": "rc.sendMessage",
  "label": "inmail1",
  "success": false,
  "error": {
    "type": "inMailNotAvailable",
    "message": "Recruiter does not allow a new InMail to this person right now. If you already have a conversation with them, reply in it with threadId; otherwise the seat may have no InMail credits left."
  }
}

Possible error.type values:

  • inMailCreditRequired – the message costs a paid InMail credit, and allowPaidCredit is not true. Nothing was sent and no credit was spent. Under rc.doForPeople, the search goes on with the next candidate.
  • inMailNotAvailable – Recruiter does not allow a new InMail to this candidate now. If you already have a conversation with them, reply in it with threadId; otherwise the seat may have no InMail credits left. Nothing was sent. Under rc.doForPeople, the search goes on with the next candidate.
  • limitExceeded – the account reached its rcMessages limit, or, for a new InMail, its rcPersonProfileViews limit. Nothing was sent.
  • messagingNotAllowed – with threadId only. The conversation is not in Recruiter's Inbox or Awaiting reply, or the candidate has not accepted or replied to your InMail yet. Nothing was sent.
  • personNotFound – Recruiter could not open a profile at this URL. Nothing was sent.
  • recruiterSignInRequired, recruiterTwoStepVerificationRequired, recruiterMultipleSessionsDetected – the seat needs attention, see account errors. These come before the Send click, so nothing was sent. A warning page that appears right after the click comes back as unexpectedError instead.
  • unexpectedError – the message could not be prepared as given, something failed from the Send click on, or the send itself was lost, for example when the browser worker stopped or timed out. In the last two cases the message may have been sent: the error's message says so, and ends with Recruiter then showed <type>. when a warning page followed the click. See Check before you send again.

The message of the errors specific to this action:

  • inMailCreditRequired: This message requires a paid InMail credit, so nothing was sent. Retry with allowPaidCredit set to true only if the user approves spending a credit on it.
  • inMailNotAvailable: Recruiter does not allow a new InMail to this person right now. If you already have a conversation with them, reply in it with threadId; otherwise the seat may have no InMail credits left.
  • messagingNotAllowed, conversation not found: This Recruiter conversation could not be opened
  • messagingNotAllowed, no answer yet: You can reply in this Recruiter conversation once the candidate accepts or replies to your message.
  • personNotFound: Recruiter profile was not found
  • unexpectedError from the Send click on, for a new InMail: Recruiter message send was not confirmed. Check Messages before resending.
  • unexpectedError from the Send click on, for a reply: Recruiter message was not confirmed, check the thread before resending.
  • unexpectedError when the send itself was lost, possibly after the Send click: Recruiter message may have been sent. Check Messages before resending.

When LinkedIn moved the tab to a warning page right after the click, either message ends with the page's error type, for example Recruiter message send was not confirmed. Check Messages before resending. Recruiter then showed recruiterMultipleSessionsDetected.

Usage example

Workflow – send an InMail to the first 5 candidates of a search, free messages only:

{
  "actionType": "rc.searchPeople",
  "limit": 5,
  "filter": {
    "jobTitles": ["Data Engineer"],
    "locations": ["Amsterdam, North Holland, Netherlands"],
    "networkRelationships": ["1st"]
  },
  "then": {
    "actionType": "rc.doForPeople",
    "then": {
      "actionType": "rc.sendMessage",
      "subject": "Data Engineer role in Amsterdam",
      "text": "Hi, I'm hiring a Data Engineer for our Amsterdam team. Would you be open to a short call next week?"
    }
  }
}

Each candidate in the completion carries the result of their rc.sendMessage in then. A candidate refused with inMailCreditRequired or inMailNotAvailable gets no message, and the search goes on with the next one. Any other failure stops the search, see rc.doForPeople.