nv.renameList

Rename one of your custom lead or account lists in Sales Navigator. Only the name changes: the list keeps its ID, its description and its leads or accounts.

An active Sales Navigator subscription is required. To find a list's ID and current name, call nv.retrieveLists.

Constraints

⏺️ Root Start: allowed.

⬆️ Parent Actions: N/A.

⬇️ Child Actions: N/A.

Parameters

{
  "actionType": "nv.renameList",
  "label": "renameEmea",
  "listId": "7420000000000000004",
  "name": "EMEA leads 2027"
}

const workflow = await linkedapi.nvRenameList.execute({
  listId: "7420000000000000004",
  name: "EMEA leads 2027"
});

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

from linkedapi import NvRenameListParams

workflow = linkedapi.nv_rename_list.execute(
    NvRenameListParams(
        list_id="7420000000000000004",
        name="EMEA leads 2027",
    )
)

result = linkedapi.nv_rename_list.result(workflow.workflow_id)

linkedin navigator lists rename 7420000000000000004 \
  --name "EMEA leads 2027" \
  --json

In AI assistants, the MCP tool is nv_rename_list. The n8n action is Rename list in Sales Navigator; the Make module is Rename List in Sales Navigator.

A name outside these limits is rejected with invalidWorkflow before the workflow starts. Nothing is ever shortened.

Renaming behaviour

• Only the name. The list keeps its id, its description and its members, so saved listId values keep working.
• One name per type. Sales Navigator itself lets you rename a list to a name another of your lists already has. This action never does, because the save menu used by nv.saveLead and nv.saveAccount shows lists by name only. If another list of the same type that you own already has the new name, the call fails with listAlreadyExists and nothing is renamed. Names are compared as in nv.createList: after removing spaces at the start and end, with letter case counting, and Sales Navigator's system lists included.
• The same name. Renaming a list to the name it already has succeeds without changing anything.
• Custom lists only. Only lists you created, in Sales Navigator or with nv.createList, can be renamed: their source in nv.retrieveLists is MANUAL. Sales Navigator's system lists, such as Recommended Leads and My Current Accounts, fail with listNotRenamable, and nothing is renamed.
• Only your own lists. listId must be a list you own. A list someone else shared with you, or an ID that is not one of your lists, fails with listNotFound.
• English interface only, for now. This is a current limitation: renaming lists works only with an English Sales Navigator interface. On a German, Spanish, French or Portuguese interface, the call fails with interfaceLanguageNotSupported.

Result options

{
  "actionType": "nv.renameList",
  "label": "renameEmea",
  "success": true,
  "data": {
    "id": "7420000000000000004",
    "name": "EMEA leads 2027",
    "type": "lead",
    "url": "https://www.linkedin.com/sales/lists/people/7420000000000000004"
  }
}

label is included only if specified in the action parameters.

Error result

An unsuccessful action returns success: false with an error object:

{
  "actionType": "nv.renameList",
  "label": "renameEmea",
  "success": false,
  "error": {
    "type": "listAlreadyExists",
    "message": "A Sales Navigator list of this type with this name already exists."
  }
}

Possible error.type values:

• noSalesNavigator — the account does not have an active Sales Navigator subscription.
• listNotFound — listId is not one of your lead or account lists. This includes a list that is already deleted and a list someone else shared with you.
• listAlreadyExists — another list of the same type that you own already has this name (see Renaming behaviour). Nothing is renamed.
• listNotRenamable — the list is one of Sales Navigator's system lists, such as Recommended Leads or My Current Accounts. Only custom lists can be renamed. Nothing is renamed.
• interfaceLanguageNotSupported — the account's Sales Navigator interface is German, Spanish, French or Portuguese rather than English. Nothing is renamed; this is a current limitation (see above).
• unexpectedError — the list could not be renamed. It is safe to call again with the same listId and name: if the failed call did rename the list, the new call succeeds without changing anything.