# Sales Navigator List Alerts

The listAlerts signal reports Sales Navigator alerts about the members of one of your lists, by polling or webhook.

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

The `listAlerts` signal watches one of the account's own Sales Navigator lists and reports the alerts Sales Navigator raises about its members: posts, job changes, profile views and company updates such as senior hires or growth.

Each event carries the alert exactly as [`nv.retrieveAlerts`](/docs/action-nv-retrieve-alerts) returns it, plus the member's or company's identity so you can match it to a record in your CRM.

## Events

| Event `type` | Webhook event | What happened |
|---|---|---|
| `alertPublished` | `signal.alertPublished` | Sales Navigator published an alert about a member of the list. |

## Creating

Creating or resuming a `listAlerts` signal requires the [Plus plan](/pricing) and an active Sales Navigator subscription. Read its lists with [`nv.retrieveLists`](/docs/action-nv-retrieve-lists), then pass one list's `id` as `listId`. It must be a **string of digits**, even when the ID looks like a number.

```json tab=HTTP
{
  "type": "listAlerts",
  "listId": "7420000000000000001",
  "label": "crm-accounts"
}
```

```typescript tab=Node
const { data: signal } = await linkedapi.createSignal({
  type: "listAlerts",
  listId: "7420000000000000001",
  label: "crm-accounts",
});
```

```python tab=Python
from linkedapi import CreateSignalParams

result = linkedapi.create_signal(
    CreateSignalParams(
        type="listAlerts",
        list_id="7420000000000000001",
        label="crm-accounts",
    )
)
```

```bash tab=CLI
linkedin signal create --type listAlerts --list-id 7420000000000000001 --label crm-accounts
```

See [Creating a signal](/docs/managing-signals#creating-a-signal) for authorization and the response fields. The response includes the same `listId`. An account can have up to five active `listAlerts` signals; creating the same signal for the same list returns the existing signal.

A custom list of saved leads or accounts gives the most consistent coverage. A system list can contain people who are not saved, for whom Sales Navigator may show only occasional suggested alerts.

Sales Navigator chooses which activity becomes an alert. This signal does not report every post by every list member, and an alert can arrive hours after the activity it describes. Lists of more than 1,000 members are not supported yet: a signal on such a list stops with `listTooLarge` on its first check, or later if the list grows past that size. `entityCount` in [`nv.retrieveLists`](/docs/action-nv-retrieve-lists) shows a list's size.

Checks pause while the account is not on Plus. Active signals keep their status and catch up when Plus returns, as far as Sales Navigator still shows the alerts. Pausing, deleting, listing or getting signals and polling their events still work without Plus.

## First check and resume

The first check reports alerts whose `publishedAt` is at or after the signal's creation time. Older alerts form a silent baseline. The publication time belongs to the **alert**: the post, job change or other activity it describes may have happened earlier.

Pausing preserves what the signal has already seen. After you resume it, the next check reports alerts that appeared while it was paused and are still available in Sales Navigator. It does not create a new baseline or report alerts it already reported. A long pause on a very active list can leave too many alerts to read; in that case the signal stops with `listTooLarge`.

## Event fields

```json
{
  "id": "sigev-5d6e7f8a-9b0c-4d1e-8f2a-3b4c5d6e7f8a",
  "signalId": "sigsub-8f9a0b1c-2d3e-4f4a-9b5c-6d7e8f9a0b1c",
  "signalType": "listAlerts",
  "label": "crm-accounts",
  "type": "alertPublished",
  "detectedAt": "2026-11-19T12:00:00Z",
  "alert": {
    "id": "urn:li:notificationV2:example-alert",
    "type": "ACCOUNT_SHARED_UPDATE",
    "publishedAt": "2026-11-19T09:00:00Z",
    "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"
  },
  "subjectUrn": "urn:li:organization:12345",
  "subjectHashedUrl": "https://www.linkedin.com/company/12345"
}
```

- `alert` – the unchanged alert object from [`nv.retrieveAlerts`](/docs/action-nv-retrieve-alerts#result-options), including its Sales Navigator subject identity and publication time.
- `subjectUrn` – `urn:li:member:<id>` for a person or `urn:li:organization:<id>` for a company, or `null` when unavailable.
- `subjectHashedUrl` – the person's `https://www.linkedin.com/in/<handle>` or the company's `https://www.linkedin.com/company/<id>`, or `null` when unavailable. These are the same forms returned as `hashedUrl` by [`nv.retrieveListLeads`](/docs/action-nv-retrieve-list-leads) and [`nv.retrieveListAccounts`](/docs/action-nv-retrieve-list-accounts).

Use `subjectUrn` or `subjectHashedUrl` to match an event to the list members you already retrieved. The alert's own `subject.urn` and `subject.url` keep their Sales Navigator forms.

:::surface python
In the Python SDK, these fields use snake_case: `subject_urn`, `subject_hashed_url`, `alert.published_at` and `alert.related_entity_urn`. Missing values are `None`.
:::

The common fields – `id`, `signalId`, `signalType`, `label`, `type` and `detectedAt` – are described in [Receiving events](/docs/signal-events#polling). Each alert is reported once per signal. Poll with `signalType: "listAlerts"` or `eventType: "alertPublished"`, or subscribe to the `signal.alertPublished` [webhook event](/docs/signal-events#webhook-events).

## Stopped signals

| `stoppedReason` | Why the signal stopped |
|---|---|
| `targetNotFound` | The list is not one of the account's own lists, including a shared list, or it was deleted. |
| `noSalesNavigator` | The account does not have an active Sales Navigator subscription. |
| `listTooLarge` | The list has more than 1,000 members, or more alerts gathered since the last check than one check can read. |

A signal can stop on its first check or on a later one. Once the cause is resolved, delete it and create a new signal; a stopped signal cannot be resumed. See [Signal status](/docs/managing-signals#signal-status).
