# rc.createProject

Create a private LinkedIn Recruiter Lite project with a name and get its ID.

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

Create a private project in LinkedIn Recruiter Lite and get its ID. For example, create one project per role, then save candidates into it with [rc.saveToProject](/docs/action-rc-save-to-project).

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 see the projects you already have, call [rc.retrieveProjects](/docs/action-rc-retrieve-projects).

:::surface node,python
In the SDK this is the `rcCreateProject` method. It takes the parameters below except `label`, which exists only in workflow JSON, and returns the result below in `data`.
:::

:::surface cli
The command is `linkedin recruiter projects create`. Its flag is listed below.
:::

## Constraints

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

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

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

## Parameters

```json tab=HTTP
{
  "actionType": "rc.createProject",
  "label": "newProject",
  "name": "Data Engineers – Amsterdam"
}
```

```typescript tab=Node
const workflow = await linkedapi.rcCreateProject.execute({
  name: "Data Engineers – Amsterdam"
});

const { data, errors } = await linkedapi.rcCreateProject.result(workflow.workflowId);
```

```python tab=Python
from linkedapi import RcCreateProjectParams

workflow = linkedapi.rc_create_project.execute(
    RcCreateProjectParams(
        name="Data Engineers – Amsterdam",
    )
)

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

```bash tab=CLI
linkedin recruiter projects create --name "Data Engineers – Amsterdam" --json
```

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

| Parameter | Description |
| --- | --- |
| `label` | Optional. Label included in workflow completion. |
| `name` | Required. Project name on a single line, from 1 to 100 characters after spaces at the start and end are removed. |

:::surface cli
| Flag | Description |
| --- | --- |
| `--name` | Required. Project name on a single line, 1 to 100 characters. |
:::

The project gets only its name. Any other field, such as `description`, is rejected with `invalidWorkflow`: set the description afterwards with [rc.renameProject](/docs/action-rc-rename-project). Job title and location cannot be set.

## Creating behaviour

- **A private project.** The project is created with Recruiter's Private visibility.
- **One click.** The action clicks Create once and never repeats the click. It succeeds once the new project's ID shows in Recruiter's address bar.
- **Check before you call again.** An error that comes back after the Create click does not prove the project was not created: the click may have landed just before a browser stall, or before LinkedIn moved the tab to its multiple-sessions notice (`recruiterMultipleSessionsDetected`). The project may also appear a moment later. So before you retry an `rc.createProject` that failed, check [rc.retrieveProjects](/docs/action-rc-retrieve-projects) for a project with that name. The action does not check for an existing project with the same name itself, and Recruiter Lite can only [archive](/docs/action-rc-archive-project) a duplicate, not delete it.

## Result options

1. **Successful creation:**

```json
{
  "actionType": "rc.createProject",
  "label": "newProject",
  "success": true,
  "data": {
    "projectId": "1700000003",
    "projectUrl": "https://www.linkedin.com/talent/hire/1700000003/overview",
    "name": "Data Engineers – Amsterdam"
  }
}
```

| Field | Meaning |
| --- | --- |
| `projectId` | ID of the new project, a string of digits. Pass it as `projectId` to the other project actions. |
| `projectUrl` | The new project's overview page in Recruiter. |
| `name` | The name read back from the new project's title, or `null` if it could not be read. The project exists either way. |

`label` is included only if specified in the action parameters.

2. **Failed creation:**

```json
{
  "actionType": "rc.createProject",
  "label": "newProject",
  "success": false,
  "error": {
    "type": "unexpectedError",
    "message": "Something went wrong unexpectedly. The team has been notified, we'll fix this as soon as possible."
  }
}
```

Possible `error.type` values:

- `recruiterSignInRequired`, `recruiterTwoStepVerificationRequired`, `recruiterMultipleSessionsDetected` – the seat needs attention, see [account errors](/docs/recruiter-lite-overview#account-errors). The project may still have been created, see [Check before you call again](#creating-behaviour).
- `unexpectedError` – Recruiter did not confirm a new project, which may still have been created. See [Check before you call again](#creating-behaviour).
