nv.retrieveAlerts

Read lead and account alerts from your Sales Navigator home feed. Use the alert's type and timestamp to decide when to reach out, then open its subject with nv.openPersonPage or nv.openCompanyPage.

Sales Navigator raises these alerts for the leads and accounts you save. To start following a subject, save it with nv.saveLead or nv.saveAccount; to stop following it, unsave it with nv.unsaveLead or nv.unsaveAccount. With default filters, alerts about unsaved subjects can still be returned; to read only alerts about subjects you saved, set filter.excludeSuggested to true. An alert's subject.url can be passed to these actions as it is.

An active Sales Navigator subscription is required. By default, the action includes saved and unsaved subjects, as well as subjects with unknown saved state. Set filter.excludeSuggested to true to return only subjects confirmed as saved. This excludes all unsaved and unknown-state subjects, including alerts without a "Suggested" label in Sales Navigator.

Constraints

⏺️ Root Start: allowed.

⬆️ Parent Actions: N/A.

⬇️ Child Actions: N/A.

Parameters

{
  "actionType": "nv.retrieveAlerts",
  "label": "companySignals",
  "limit": 50,
  "sort": "latest",
  "filter": {
    "category": "account",
    "types": ["ACCOUNT_SHARED_UPDATE", "ACCOUNT_SENIOR_HIRE"],
    "since": "2026-10-01T00:00:00Z",
    "excludeSuggested": false
  }
}

const workflow = await linkedapi.nvRetrieveAlerts.execute({
  limit: 50,
  sort: "latest",
  filter: {
    category: "account",
    types: ["ACCOUNT_SHARED_UPDATE", "ACCOUNT_SENIOR_HIRE"],
    since: "2026-10-01T00:00:00Z",
    excludeSuggested: false
  }
});

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

from linkedapi import NvRetrieveAlertsParams

workflow = linkedapi.nv_retrieve_alerts.execute(
    NvRetrieveAlertsParams(
        limit=50,
        sort="latest",
        filter={
            "category": "account",
            "types": ["ACCOUNT_SHARED_UPDATE", "ACCOUNT_SENIOR_HIRE"],
            "since": "2026-10-01T00:00:00Z",
            "exclude_suggested": False,
        },
    )
)

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

linkedin navigator alerts \
  --limit 50 \
  --sort latest \
  --category account \
  --types ACCOUNT_SHARED_UPDATE,ACCOUNT_SENIOR_HIRE \
  --since 2026-10-01T00:00:00Z \
  --json

In AI assistants, the MCP tool is nv_retrieve_alerts. The n8n action is Retrieve alerts in Sales Navigator; the Make module is Retrieve Alerts in Sales Navigator.

All filter conditions are combined with AND. Values within filter.types are alternatives, and so are values within filter.subjects. The action reads additional feed pages when needed to find matching alerts; limit counts matches, not scanned records. Fewer matches, including an empty array, are a successful result when the available feed is exhausted.

For example, an accepted-invitation alert about an unsaved lead is included by default, even if Sales Navigator shows no "Suggested" label. Setting filter.excludeSuggested to true excludes it. Unknown saved state stays null and is included by default; it is excluded when filter.excludeSuggested is true, because it is not confirmation that the subject is saved.

Alerts for a list or for chosen subjects

Two filters narrow the feed to the subjects you care about. Both combine with the other filters by AND.

filter.listId: the members of one list. The action applies Sales Navigator's own list filter, so it returns only alerts about the leads or accounts in that list.

• Any of your lists. Pass the id of one of your lead or account lists from nv.retrieveLists; no list type is needed. A list that is not one of yours, including one someone else shared with you, fails with listNotFound.
• Newest first only. Sales Navigator applies its list filter only to the newest-first feed. Use sort set to latest, the default. A workflow that combines filter.listId with sort set to relevance is rejected with invalidWorkflow before it starts; the sort is never changed for you.
• Read to the end of the list's feed. The action keeps reading the list's alerts until it has limit matches or the list's feed ends. A list feed that cannot be read to its end fails with unexpectedError rather than returning a partial result.
• since with large lists. For a list of up to 189 members (entityCount in nv.retrieveLists), reading stops at the first alert older than filter.since. For a larger list, or one whose entityCount is null, the action reads the list's whole feed and keeps only alerts at or after filter.since, so the call takes longer.

{
  "actionType": "nv.retrieveAlerts",
  "label": "emeaLeadAlerts",
  "limit": 100,
  "filter": {
    "listId": "7420000000000000001",
    "since": "2026-11-01T00:00:00Z"
  }
}

const workflow = await linkedapi.nvRetrieveAlerts.execute({
  limit: 100,
  filter: {
    listId: "7420000000000000001",
    since: "2026-11-01T00:00:00Z"
  }
});

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

from linkedapi import NvRetrieveAlertsParams

workflow = linkedapi.nv_retrieve_alerts.execute(
    NvRetrieveAlertsParams(
        limit=100,
        filter={
            "list_id": "7420000000000000001",
            "since": "2026-11-01T00:00:00Z",
        },
    )
)

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

linkedin navigator alerts \
  --list-id 7420000000000000001 \
  --since 2026-11-01T00:00:00Z \
  --limit 100 \
  --json

filter.subjects: chosen leads or accounts. The action returns only alerts whose subject is one of the leads or accounts you list. It works with both sort orders, and several subjects return alerts about any of them.

• Accepted values. An alert's subject.url (/sales/lead/… or /sales/company/…) or subject.urn, or a hashedUrl from nv.searchPeople, nv.searchCompanies, nv.retrieveListLeads or nv.retrieveListAccounts.
• Matched by identity. A lead's hashed URL matches alerts about that person whichever URL form the alert uses, and the same goes for a company and its numeric ID.
• Rejected values. Public URLs such as linkedin.com/in/<vanity> or linkedin.com/company/<vanity> are rejected with invalidWorkflow before the workflow starts, because resolving each one would cost a page load. So are urn values from search results (urn:li:member:…, urn:li:organization:…): pass the result's hashedUrl instead.

{
  "actionType": "nv.retrieveAlerts",
  "label": "twoAccounts",
  "sort": "relevance",
  "filter": {
    "subjects": [
      "https://www.linkedin.com/sales/company/12345",
      "https://www.linkedin.com/company/67890"
    ]
  }
}

Alert types

The type field preserves Sales Navigator's machine code. Types observed on the live feed include:

This is an open set: other types can appear as Sales Navigator adds signals. Filter on codes returned in type, rather than matching the localized headline. A type filter with no matching alerts returns an empty array.

Result options

{
  "actionType": "nv.retrieveAlerts",
  "label": "companySignals",
  "success": true,
  "data": [
    {
      "id": "urn:li:notificationV2:example-alert",
      "type": "ACCOUNT_SHARED_UPDATE",
      "publishedAt": "2026-10-30T09:00:00.000Z",
      "subject": {
        "type": "account",
        "urn": "urn:li:fs_salesCompany:12345",
        "name": "Example Labs",
        "url": "https://www.linkedin.com/sales/company/12345",
        "saved": true
      },
      "headline": "Example Labs shared an update.",
      "text": "Meet our latest product update.",
      "subline": "Software Development",
      "url": "https://www.linkedin.com/feed/sales-navigator/urn:li:share:1234567890",
      "relatedEntityUrn": "urn:li:share:1234567890"
    }
  ]
}

A lead's subject.url uses /sales/lead/…; an account's uses /sales/company/…. Subject metadata is associated by identity. When an alert describes several entities, a name or saved state belonging to another entity is not attached to the subject.

Retrieval and history

Each call reads the feed currently available to your account. Linked API does not store alerts, track a polling cursor or send alert webhooks. To check for new alerts, call again with filter.since and deduplicate by id; the inclusive timestamp lets you retain events sharing the same publication time.

Sales Navigator controls which alerts remain available. since filters the available feed and does not recover expired or cleared alerts. No fixed history period is guaranteed. Saved-search email notifications and shared-list system notifications are outside this action's lead and account feed.

The action reads alerts without clearing, bookmarking or saving them. With filter.excludeSuggested set to true, an account with no confirmed saved leads or accounts returns an empty result even when Sales Navigator shows suggestions. A missing or unreadable feed response is reported as a failure, not as an empty successful result.

Retrieval resets the home feed's filters and applies the requested sort; with filter.listId, it opens the feed filtered to that list instead. These view settings can remain selected when you next use Sales Navigator. Category and subject filtering is applied to the returned subjects.

Error result

An unsuccessful action returns success: false with an error object. Possible error.type values:

• noSalesNavigator — the account does not have an active Sales Navigator subscription.
• listNotFound — filter.listId is not one of your lead or account lists. This includes a list someone else shared with you.
• unexpectedError — the feed could not be retrieved or parsed, including a list's feed that could not be read to its end.