> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sequenzy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Account Notifications

> Get an email when someone subscribes or when a campaign finishes sending.

Account notifications are emails Sequenzy sends **to you** about your workspace, as opposed to the emails you send to your subscribers.

Two events are available:

| Event                | When it fires                                                                   |
| -------------------- | ------------------------------------------------------------------------------- |
| `new_subscriber`     | A contact joins through a form, landing page, popup, the API, or an integration |
| `campaign_completed` | A campaign finishes sending, with its final sent and failed counts              |

## Modes

Each notification is set independently:

* **`instant`** - one email per occurrence
* **`daily`** - one summary per day, listing who joined (new subscribers only)
* **`off`** - no email

Both notifications default to `off` - turn on the ones you want in **Settings → Notifications**.

`campaign_completed` does not support `daily`. A campaign finishes once, so a daily rollup would almost always be a list with a single row in it.

## What does not trigger a new-subscriber notification

**Imports never notify.** Uploading a CSV or running a migration creates thousands of contacts, and none of them produce an email. This holds even when you turn **Enroll in sequences** on for the import - that setting decides what happens to the contacts, not whether you hear about each one. The same applies to any bulk operation that skips automation triggers.

Only live signups count: form and popup submissions, landing pages, the subscribers API, and integration syncs that represent a real customer action.

**With double opt-in on, you are notified when the contact confirms, not when they sign up.** Someone who requests the confirmation email and never clicks it never produces a notification, so what lands in your inbox matches who actually joined your list. A confirmation is a real person clicking a link, so it notifies even if the pending contact originally arrived in an import.

## The daily cap

If you are set to `instant` and your workspace passes **50 signups in one UTC day**, per-signup emails stop for the rest of that day. You get one email explaining the switch, and the remainder arrive as a single summary.

This keeps a viral day from turning into hundreds of emails. Nothing is lost - the summary reports the true total for the day, including the signups that were not sent individually.

## Per person, not per workspace

These settings belong to you, not to the workspace. Each teammate chooses their own, and changing yours never changes anyone else's. Members with **restricted** (link-only) access do not receive account notifications at all.

If you belong to several workspaces, you configure each one separately.

## Changing your settings

<Tabs>
  <Tab title="Dashboard">
    Go to **Settings → Notifications**.
  </Tab>

  <Tab title="CLI">
    ```bash theme={null}
    sequenzy notifications get

    # Switch to a daily summary before a big launch
    sequenzy notifications set --new-subscriber daily

    # Silence everything
    sequenzy notifications set --new-subscriber off --campaign-completed off
    ```

    Add `--json` to either command for machine-readable output.
  </Tab>

  <Tab title="API">
    ```bash theme={null}
    curl "https://api.sequenzy.com/api/v1/notification-preferences" \
      -H "Authorization: Bearer API_KEY"
    ```

    ```bash theme={null}
    curl -X PATCH "https://api.sequenzy.com/api/v1/notification-preferences" \
      -H "Authorization: Bearer API_KEY" \
      -H "Content-Type: application/json" \
      -d '{"notificationPreferences": [{"event": "new_subscriber", "mode": "daily"}]}'
    ```

    Both endpoints act on the API key's own user. There is no way to read or change a teammate's notification settings through the API.
    Reading requires `account:read`; changing preferences requires `companies:manage`.
  </Tab>

  <Tab title="MCP">
    Use the `get_notification_preferences` and `update_notification_preferences` tools.
  </Tab>
</Tabs>

## Sending this somewhere other than email

For Slack, Zapier, or your own service, use an [outbound webhook](/integrations/outbound-webhooks) on the `subscriber.created` event instead. Unlike the notification above, that event fires for **every** created contact, including imports, and carries a `source` field you can filter on.