# rc.renameProject

Change the name and, optionally, the description of a LinkedIn Recruiter Lite project.

> 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.

Change the name of a LinkedIn Recruiter Lite project and, optionally, its description. This is also how a project created with [rc.createProject](/docs/action-rc-create-project) gets its description.

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). To find a project's ID, call [rc.retrieveProjects](/docs/action-rc-retrieve-projects).

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

:::surface cli
The command is `linkedin recruiter projects rename`. Its argument and flags are listed below.
:::

## Constraints

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

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

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

## Parameters

```json tab=HTTP
{
  "actionType": "rc.renameProject",
  "label": "rename1",
  "projectId": "1700000003",
  "name": "Data Engineers – Amsterdam (2027)",
  "description": "Senior data engineers for the logistics platform team.\nStart date: Q1."
}
```

```typescript tab=Node
const workflow = await linkedapi.rcRenameProject.execute({
  projectId: "1700000003",
  name: "Data Engineers – Amsterdam (2027)",
  description: "Senior data engineers for the logistics platform team.\nStart date: Q1."
});

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

```python tab=Python
from linkedapi import RcRenameProjectParams

workflow = linkedapi.rc_rename_project.execute(
    RcRenameProjectParams(
        project_id="1700000003",
        name="Data Engineers – Amsterdam (2027)",
        description="Senior data engineers for the logistics platform team.\nStart date: Q1.",
    )
)

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

```bash tab=CLI
linkedin recruiter projects rename 1700000003 \
  --name "Data Engineers – Amsterdam (2027)" \
  --description $'Senior data engineers for the logistics platform team.\nStart date: Q1.' \
  --json
```

In AI assistants, the MCP tool is `rc_rename_project`. The n8n action is **Rename project in Recruiter Lite**; the Make module is **Rename Project in Recruiter Lite**.

| Parameter | Description |
| --- | --- |
| `label` | Optional. Label included in workflow completion. |
| `projectId` | Required. Project ID, a string of digits, from [rc.retrieveProjects](/docs/action-rc-retrieve-projects) or [rc.createProject](/docs/action-rc-create-project). |
| `name` | Required. Project name on a single line, from 1 to 100 characters after spaces at the start and end are removed. To change only the description, pass the current name. |
| `description` | Optional. Project description, up to 2000 characters. Line breaks are allowed. Omit it to leave the description as it is. |

:::surface cli
| Arg | Required | Description |
| --- | --- | --- |
| `project-id` | yes | Project ID, from `linkedin recruiter projects` or `linkedin recruiter projects create` |

| Flag | Description |
| --- | --- |
| `--name` | Required. New project name on a single line, 1 to 100 characters. To change only the description, pass the current name. |
| `--description` | Optional. Project description, up to 2000 characters. Omit it to leave the description as it is. |

The example passes the line break in the description with Bash's `$'…'` quoting.
:::

## Saving behaviour

- **Saved on the settings page.** The action opens the project's settings in Recruiter, saves the name, then the description if you gave one, as you would by hand.
- **Read back.** Each value is checked after it is saved: the name must show as the project's name, and the description editor is reopened to read the saved text in full. A value that does not read back fails the action.
- **Repeating is safe.** Calling again with the same values saves the same name and description again.

## Result options

1. **Successful change:**

```json
{
  "actionType": "rc.renameProject",
  "label": "rename1",
  "success": true
}
```

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

2. **Failed change:**

```json
{
  "actionType": "rc.renameProject",
  "label": "rename1",
  "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 a project with this ID: Recruiter answers with its page-not-found. Nothing was changed.
- `recruiterSignInRequired`, `recruiterTwoStepVerificationRequired`, `recruiterMultipleSessionsDetected` – the seat needs attention, see [account errors](/docs/recruiter-lite-overview#account-errors).
- `unexpectedError` – a value could not be saved or did not read back. 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. The name may already be saved when the description fails, so call again with both.
