> For the complete documentation index, see [llms.txt](https://developer.celigo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.celigo.com/cli/commands/notifications.md).

# notifications

Manage per-user notification subscriptions — the email and webhook alerts routed on flow, connection, and integration events (errors, status changes, completions).

**REST API**: [Notifications](https://developer.celigo.com/api/api-reference/notifications)

```
celigo notifications <subcommand> [flags]
```

Supports all [global flags](/cli/getting-started/global-flags.md).

***

## Subcommands

| Subcommand    | Purpose                                                                  |
| ------------- | ------------------------------------------------------------------------ |
| `list`        | List every notification subscription in the account.                     |
| `subscribe`   | Subscribe a user to one or more flows, connections, or integrations.     |
| `unsubscribe` | Unsubscribe a user from one or more flows, connections, or integrations. |

***

## `celigo notifications list`

List all notification subscriptions in the account.

**Signature**

```bash
celigo notifications list
```

**Arguments**

None.

**Flags**

None beyond the [global flags](/cli/getting-started/global-flags.md) (`--format`, `--jq`, `--profile`, `--verbose`).

**Example**

```bash
celigo notifications list --format table
```

Default table columns: `_id`, `type`, `_integrationId`, `_flowId`, `_connectionId`, `subscribedByUser.email`, `lastModified`.

**Corresponds to**: [`GET /v1/notifications?users=all`](https://developer.celigo.com/api/api-reference/notifications#get-v1-notifications)

***

## `celigo notifications subscribe`

Subscribe a user to notifications on one or more resources. At least one of `--flow`, `--connection`, or `--integration` must be provided. The CLI builds one subscribe item per ID and batches at 50 items per request.

**Signature**

```bash
celigo notifications subscribe --user <email> [--flow <ids...>] [--connection <ids...>] [--integration <ids...>]
```

**Arguments**

None. Targets are supplied via flags.

**Flags**

| Flag                     | Type      | Required | Description                                                |
| ------------------------ | --------- | -------- | ---------------------------------------------------------- |
| `--user <email>`         | string    | Yes      | Email of the user to subscribe.                            |
| `--flow <ids...>`        | string\[] | No       | One or more flow IDs to subscribe the user to. Repeatable. |
| `--connection <ids...>`  | string\[] | No       | One or more connection IDs. Repeatable.                    |
| `--integration <ids...>` | string\[] | No       | One or more integration IDs. Repeatable.                   |

**Examples**

```bash
celigo notifications subscribe --user jane@example.com --flow 69497fc443fc1f9a03d31bd9
celigo notifications subscribe --user jane@example.com --connection 5e5eb06fdd83ed4f8206a4ea --connection 5efe49fd2c1111472296f389
celigo notifications subscribe --user jane@example.com --integration 62c0b8ab1234567890abcdef --flow 69497fc443fc1f9a03d31bd9
```

**Corresponds to**: [`PUT /v1/notifications`](https://developer.celigo.com/api/api-reference/notifications#put-v1-notifications) (one item per ID, `subscribed: true`)

***

## `celigo notifications unsubscribe`

Unsubscribe a user from notifications on one or more resources. At least one of `--flow`, `--connection`, or `--integration` must be provided. Same batching behavior as `subscribe`.

**Signature**

```bash
celigo notifications unsubscribe --user <email> [--flow <ids...>] [--connection <ids...>] [--integration <ids...>]
```

**Arguments**

None. Targets are supplied via flags.

**Flags**

| Flag                     | Type      | Required | Description                                           |
| ------------------------ | --------- | -------- | ----------------------------------------------------- |
| `--user <email>`         | string    | Yes      | Email of the user to unsubscribe.                     |
| `--flow <ids...>`        | string\[] | No       | One or more flow IDs to unsubscribe from. Repeatable. |
| `--connection <ids...>`  | string\[] | No       | One or more connection IDs. Repeatable.               |
| `--integration <ids...>` | string\[] | No       | One or more integration IDs. Repeatable.              |

**Examples**

```bash
celigo notifications unsubscribe --user jane@example.com --flow 69497fc443fc1f9a03d31bd9
celigo notifications unsubscribe --user jane@example.com --connection 5e5eb06fdd83ed4f8206a4ea --connection 5efe49fd2c1111472296f389
```

**Corresponds to**: [`PUT /v1/notifications`](https://developer.celigo.com/api/api-reference/notifications#put-v1-notifications) (one item per ID, `subscribed: false`)

***

## Gotchas

* **One resource type per item.** Each subscribe/unsubscribe item targets exactly one of `_flowId`, `_connectionId`, or `_integrationId`. Passing multiple target flags on one command is fine — the CLI expands them into separate items.
* **Account-scoped admin op.** `list` passes `users=all`, so it returns subscriptions for every user in the account, not just the caller's own.
* **Per-item results, overall `200 OK`.** The underlying `PUT /v1/notifications` always returns `200 OK` even when individual items fail (e.g. a referenced `_flowId` doesn't exist returns `statusCode: 422` on that item only). Inspect the per-item `statusCode` in the response.
* **Batched at 50.** Large subscribe/unsubscribe requests are chunked; the CLI prints the result of the last batch.
* **The response is not the subscription object.** `PUT` returns a per-item status array — run `celigo notifications list` afterward to read the post-upsert state.

## Related

* [subscriptions](/cli/commands/subscriptions.md) — account-level license/plan subscriptions and usage (unrelated to notification subscriptions despite the name overlap).
* [workspace-users](/cli/commands/workspace-users.md) — manage the users whose emails appear in `--user`.
* [flows](/cli/commands/flows.md), [connections](/cli/commands/connections.md), [integrations](/cli/commands/integrations.md) — the resources you subscribe users to.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.celigo.com/cli/commands/notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.