# rc.syncInbox

Enable monitoring of a LinkedIn Recruiter Lite inbox, so you can poll every Recruiter conversation's messages or receive them as webhook events.

> The API Reference is also the SDK and CLI reference. Consecutive code fences marked `tab=HTTP`, `tab=Node`, `tab=Python` and `tab=CLI` are the same call on each surface (a fence marked `tab=HTTP,CLI` is the same text for both), and a block between `:::surface <names>` and `:::` applies only to the surfaces it names. Identifiers in the text are written as in Node and in HTTP JSON (camelCase); the Python SDK spells methods, parameters and result attributes in snake_case (`sendMessage` → `send_message`, `reconnectionLink` → `reconnection_link`), while names inside HTTP JSON stay camelCase.

This action enables **inbox monitoring** for the account's LinkedIn Recruiter Lite inbox. From then on, a background sync captures the messages of your Recruiter conversations, and you read them through [inbox polling](/docs/monitoring-inbox#recruiter-lite-inbox) with `type: "rc"` or receive them as `inbox.*` [webhook events](/docs/webhook-event-types#inbox-events).

The account needs a Recruiter Lite seat, Linked API's Plus plan and a [supported LinkedIn interface language](/docs/recruiter-lite-overview#seat-requirements) – see [Recruiter Lite](/docs/recruiter-lite-overview).

:::surface node,python
In the SDK this is the `rcSyncInbox` method. It takes no parameters (`label` exists only in workflow JSON) and returns no `data`: a failed action comes back in `errors`, with one of the error types below.
:::

:::surface cli
The command is `linkedin inbox sync` with `--rc`, which cannot be combined with `--nv`.
:::

> 💡 **Run it before you send the first InMail.** Only messages from the minute inbox monitoring is enabled onwards are captured, and sending a message with [rc.sendMessage](/docs/action-rc-send-message) never enables it.

Run it once per account. It is separate from the standard and Sales Navigator inboxes, which [st.syncInbox](/docs/action-st-sync-inbox) and [nv.syncInbox](/docs/action-nv-sync-inbox) enable.

## What the sync reads

- **Two Recruiter folders.** The sync reads Recruiter's **Inbox**, which holds the conversations where the candidate replied, and **Awaiting reply**, which holds your messages that have no answer yet. So an InMail you send shows up as a `sender: "us"` message, with an `inbox.messageSent` event, before the candidate replies. When the reply moves the conversation to Inbox, the reply shows up as `sender: "them"`, and your earlier message does not appear a second time.
- **The 30 most recent conversations of each folder.** Each sync looks at the 30 most recent conversations in Inbox and the 30 most recent in Awaiting reply, and opens only those that are new or changed since the previous sync. A new message from either side changes a conversation, so a reply you send in it – with [rc.sendMessage](/docs/action-rc-send-message) or typed in Recruiter – shows up as `sender: "us"` after the next sync. A conversation further down a folder than its 30 most recent is not read at all, until new activity brings it back up.
- **Not the other folders.** Scheduled and Archived are not read. A conversation you archive in Recruiter stops syncing.
- **Only new messages.** The cut-off is the minute inbox monitoring was enabled: messages from before that minute are not imported, and there is no action to load a Recruiter conversation's earlier history.
- **Every 30 minutes at most.** The sync reads the Recruiter inbox at most once every 30 minutes per account, within the account's [working hours](/docs/working-hours). The first messages appear after the next sync, not when this action completes.
- **No profile visits.** Unlike the standard and Sales Navigator sync, the Recruiter sync never opens a candidate's profile. A Recruiter message always carries the candidate's Recruiter profile URL as `personRecruiterUrl`, but their public URL only when [rc.openPersonPage](/docs/action-rc-open-person-page) or [rc.sendMessage](/docs/action-rc-send-message) has already seen it on their Recruiter profile – see [Recruiter Lite inbox](/docs/monitoring-inbox#recruiter-lite-inbox).

## Every call checks the seat

Each call opens one Recruiter page to check that the seat is usable, and enables the sync only if the page is clean. Otherwise it fails with one of the errors below, and a first call enables nothing.

Calling it again on an account where the sync is already enabled is safe. It keeps the original start, so no messages are lost or imported twice. It is also how you resume a sync that stopped, see [When the sync stops](#when-the-sync-stops).

## The sync keeps Recruiter open

With the sync enabled, Linked API opens Recruiter in the account's cloud browser regularly, even when none of your workflows runs. So the [one-session rule](/docs/recruiter-lite-overview#one-seat-one-recruiter-session) applies at all times: while the sync is on, do not sign in to the seat's Recruiter anywhere else. A second sign-in leads to LinkedIn's multiple-sessions notice, and repeated detections can get the seat suspended.

## When the sync stops

When the Recruiter sync meets one of the states below, it stops reading Recruiter. The standard and Sales Navigator inbox syncs of the same account go on.

- **A sign-in page, a two-step verification page, or a LinkedIn interface language that is not supported** pauses the Recruiter sync for 6 hours. After that, it tries once more by itself. A clean pass ends the pause; if that try fails too, the Recruiter sync is held until a call to `rc.syncInbox` whose check is clean, like the multiple-sessions hold below. Sign in to Recruiter in the account's cloud browser, turn two-step verification back on, or switch the interface to a [supported language](/docs/recruiter-lite-overview#seat-requirements), as the [account errors](/docs/recruiter-lite-overview#account-errors) describe. Calling `rc.syncInbox` once the seat is ready ends a pause or a hold right away.
- **Any other failure** of the Recruiter sync, for example a LinkedIn page it does not recognise, also pauses it for 6 hours, with the same single retry: a second failure with no clean pass in between holds it until a call to `rc.syncInbox` whose check is clean.
- **LinkedIn's multiple-sessions notice** holds the Recruiter sync: it opens no Recruiter page at all until you call `rc.syncInbox` and its check finds the seat clean. Fix the cause first, as [One seat, one Recruiter session](/docs/recruiter-lite-overview#one-seat-one-recruiter-session) describes, then call `rc.syncInbox`. If the notice is still there, the call fails with `recruiterMultipleSessionsDetected` and the sync stays held.

Linked API does not report these stops anywhere else. **If Recruiter messages stop arriving, call `rc.syncInbox`:** it checks the seat, and either resumes the sync or returns the error that blocks it.

## Constraints

> ⏺️ **Root Start:** allowed.

> ⬆️ **Parent Actions:** N/A.

> ⬇️ **Child Actions:** N/A.

## Parameters

```json tab=HTTP
{
  "actionType": "rc.syncInbox",
  "label": "enableRcInbox"
}
```

```typescript tab=Node
const workflow = await linkedapi.rcSyncInbox.execute({});

const { errors } = await linkedapi.rcSyncInbox.result(workflow.workflowId);
```

```python tab=Python
workflow = linkedapi.rc_sync_inbox.execute()

result = linkedapi.rc_sync_inbox.result(workflow.workflow_id)
```

```bash tab=CLI
linkedin inbox sync --rc --json
```

In AI assistants, the MCP tool is `rc_sync_inbox`. The n8n action is **Sync inbox in Recruiter Lite**; the Make module is **Sync Inbox in Recruiter Lite**.

| Parameter | Description |
| --- | --- |
| `label` | Optional. Label included in workflow completion. |

This action takes no other parameters.

## Result options

1. **Successful enabling:**

```json
{
  "actionType": "rc.syncInbox",
  "label": "enableRcInbox",
  "success": true
}
```

The action returns no `data`. `label` is included only if specified in the action parameters.

2. **Failed enabling:**

```json
{
  "actionType": "rc.syncInbox",
  "label": "enableRcInbox",
  "success": false,
  "error": {
    "type": "recruiterMultipleSessionsDetected",
    "message": "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."
  }
}
```

Possible `error.type` values:

- `recruiterSignInRequired`, `recruiterTwoStepVerificationRequired` – the seat needs attention, see [account errors](/docs/recruiter-lite-overview#account-errors). On an account where the sync is already enabled, the Recruiter sync also pauses for 6 hours, or is held if it was already paused.
- `recruiterMultipleSessionsDetected` – LinkedIn's multiple-sessions notice is on the seat. On an account where the sync is already enabled, the Recruiter sync is held until a call to this action succeeds. See [One seat, one Recruiter session](/docs/recruiter-lite-overview#one-seat-one-recruiter-session).
- `unexpectedError` – Recruiter could not be checked. On an account where the sync is already enabled, the Recruiter sync also pauses for 6 hours, or is held if it was already paused; a later call whose check is clean ends either. LinkedIn's [other warning screens](/docs/recruiter-lite-overview#other-warning-screens) end here too, so check Recruiter in the account's cloud browser before you call again.
