nv.unsaveLead

Unsave a lead in Sales Navigator. This is Sales Navigator's own Unsave: the person is no longer a saved lead and is removed from every custom lead list you own. An alert's subject.url from nv.retrieveAlerts can be passed straight to this action.

An active Sales Navigator subscription is required.

Constraints

⏺️ Root Start: allowed, when personHashedUrl parameter is provided.

⬆️ Parent Actions: nv.openPersonPage.

⬇️ Child Actions: N/A.

Parameters

{
  "actionType": "nv.unsaveLead",
  "label": "unsaveLead1",
  "personHashedUrl": "https://www.linkedin.com/in/SInQBmjJ015eLr8"
}

In AI assistants, the MCP tool is nv_unsave_lead. The n8n action is Unsave lead in Sales Navigator; the Make module is Unsave Lead in Sales Navigator.

ParameterDescription
labelOptional label included in workflow completion.
personHashedUrlRequired for root start, forbidden for parent start. LinkedIn URL of the person, in any form nv.openPersonPage accepts: a hashed URL, an alert's subject.url (/sales/lead/…), or a public profile URL (linkedin.com/in/<vanity>), which costs one extra page load. Under nv.openPersonPage, the person whose page is open is unsaved.

Unsaving behaviour

  • Removed from your lists too. Unsaving a lead also removes them from every custom lead list you own. To take a lead out of one list and keep them saved, use nv.removeLeadFromList instead.
  • Safe to repeat. Unsaving a person who is not a saved lead succeeds without changing anything.
  • Not available on search results. This action cannot run under nv.doForPeople. Use it as a root action or under nv.openPersonPage.
  • Changes can take up to a few minutes to appear. Sales Navigator can take up to a few minutes to reflect a change. A call that conflicts with a change you just made through Linked API, such as unsaving a lead you have just saved, may fail with unexpectedError; retry it a little later.
  • English interface only, for now. This is a current limitation: saving and unsaving work only with an English Sales Navigator interface. On a German, Spanish, French or Portuguese interface, the call fails with interfaceLanguageNotSupported.

To save the lead again, use nv.saveLead. To delete a whole lead list and keep its leads saved, use nv.deleteList.

Result options

json
{
  "actionType": "nv.unsaveLead",
  "label": "unsaveLead1",
  "success": true
}

A successful unsave has no data. label is included only if specified in the action parameters.

Error result

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

json
{
  "actionType": "nv.unsaveLead",
  "label": "unsaveLead1",
  "success": false,
  "error": {
    "type": "personNotFound",
    "message": "Provided URL is not an existing LinkedIn person."
  }
}

Possible error.type values:

  • noSalesNavigator — the account does not have an active Sales Navigator subscription.
  • personNotFound — the provided URL is not an existing LinkedIn person. This includes a public profile URL that leads to no LinkedIn profile.
  • interfaceLanguageNotSupported — the account's Sales Navigator interface is German, Spanish, French or Portuguese rather than English. Nothing is changed; this is a current limitation (see above).
  • unexpectedError — the unsave could not be completed. This includes a call that conflicts with a change you just made through Linked API: Sales Navigator can take up to a few minutes to reflect a change, so retry it a little later.