rc.saveToProject
Save a candidate to one of your LinkedIn Recruiter Lite projects. The candidate is added to the project's first stage. Use it on its own with a Recruiter profile URL, or under rc.doForPeople for each candidate of a search.
The account needs a Recruiter Lite seat, Linked API's Plus plan and a supported LinkedIn interface language – see Recruiter Lite. To find a project's ID, call rc.retrieveProjects.
In the SDK this is the rcSaveToProject method. It takes the parameters below except label, which exists only in workflow JSON, and returns the result below in data.
The command is linkedin recruiter person save. Its argument and flag are listed below.
Constraints
⏺️ Root Start: allowed, when
personUrlparameter is provided.
⬆️ Parent Actions: rc.doForPeople.
⬇️ Child Actions: N/A.
Parameters
{
"actionType": "rc.saveToProject",
"label": "save1",
"personUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId1",
"projectId": "1700000001"
}In AI assistants, the MCP tool is rc_save_to_project. The n8n action is Save to project in Recruiter Lite; the Make module is Save to Project in Recruiter Lite.
| Parameter | Description |
|---|---|
label | Optional. Label included in workflow completion. |
personUrl | Required at the root, not allowed under rc.doForPeople, which supplies it. A Recruiter profile URL, https://www.linkedin.com/talent/profile/…, such as recruiterProfileUrl from rc.searchPeople. A public profile URL (linkedin.com/in/…) is rejected with invalidWorkflow. |
projectId | Required. Project ID, a string of digits, from rc.retrieveProjects or rc.createProject. |
| Arg | Required | Description |
|---|---|---|
url | yes | Recruiter profile URL of the candidate, https://www.linkedin.com/talent/profile/… |
| Flag | Description |
|---|---|
--project-id | Required. Project ID, from linkedin recruiter projects or linkedin recruiter projects create. |
Saving behaviour
- Opened in the project. The action opens the candidate's profile in the project's context, so it counts one
rcPersonProfileViewslimit view. Do not open the same candidate with rc.openPersonPage first just to save them: that loads the profile twice and counts twice. - Already there. If the candidate is already in the project, nothing is clicked and the result has
alreadyInProjectset totrue. The action reads the project membership twice, a second apart, and acts only when both reads agree. - One click. Otherwise it clicks Save once and requires Recruiter to show the candidate as saved. It never clicks a second time, so a failed call does not leave a double save.
- Repeating is safe. Calling again for the same candidate and project returns
alreadyInProjectset totrue.
Result options
- Successful saving:
{
"actionType": "rc.saveToProject",
"label": "save1",
"success": true,
"data": {
"alreadyInProject": false
}
}| Field | Meaning |
|---|---|
alreadyInProject | true if the candidate was already in the project and nothing was changed; false if this call saved them. |
label is included only if specified in the action parameters.
- Failed saving:
{
"actionType": "rc.saveToProject",
"label": "save1",
"success": false,
"error": {
"type": "projectNotFound",
"message": "The Recruiter project could not be opened or no longer exists."
}
}Possible error.type values:
projectNotFound– the seat cannot open the project: Recruiter dropped it from the profile's address and showed that you may not have access to it. Nothing was clicked.recruiterSignInRequired,recruiterTwoStepVerificationRequired,recruiterMultipleSessionsDetected– the seat needs attention, see account errors.limitExceeded– the account reached itsrcPersonProfileViewslimit.unexpectedError– the candidate could not be saved, or Recruiter did not confirm the save. LinkedIn's other warning screens end here too, so check Recruiter in the account's cloud browser before you call again. If the save went through, the new call returnsalreadyInProjectset totrue.
Under rc.doForPeople, a failure stops the search at that candidate – see Results and paging.