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

# Notifications

Configure email alerts for important workspace events. Each notification type has its own activation and recipients.

Go to **Platform → Settings → Notifications** to manage these alerts.

***

### 🔹 Configure notifications

1. Turn on the event you want to monitor.
2. Select recipients when the event supports them.
3. Save your changes.

Settings apply to the current workspace only. When you enable an event without recipients, workspace owners are selected automatically where recipient selection is available.

Email addresses are normalized and deduplicated before delivery.

{% hint style="info" %}
**New message in human ticket** uses automatic recipients. You cannot select recipients for this event.
{% endhint %}

***

### 🔔 Available events

#### New message in human ticket

Sends an email when a user messages a chat with an open human ticket.

The channel owner receives the email. If the channel has no owner, the ticket assignee receives it instead.

Alerts are limited to one email per chat every five minutes.

#### Human ticket opened

Sends an email when a human ticket is created.

If the ticket has an assignee, that member receives the email. Otherwise, the event's configured recipients receive it.

#### Low credits

Sends an email when workspace consumption reaches 90% or more. It can also send after the limit is reached.

The email shows the consumed percentage. It does not show the remaining credit count.

Alerts are limited to one email per workspace every 24 hours.

#### Agent execution failure

Sends an email when an agent execution fails.

Choose the workspace members who receive these alerts. Failures are grouped for five minutes before delivery.

The email links to **Executions** for investigation.

#### Workflow execution failure

Sends an email when a workflow execution fails.

Choose the workspace members who receive these alerts. Failures are grouped for five minutes before delivery.

The email links to **Executions** for investigation.

{% hint style="warning" %}
Workflow node tests can currently trigger this alert. This also applies to non-production tests.
{% endhint %}

#### Channel disconnection

Sends an email when a connection disconnects. This includes authentication failures and similar connection errors.

Choose the workspace members who receive these alerts. The email includes the connection, provider, affected channels, and reason.

***

### 🔗 Email links and branding

Operational emails use a consistent layout and localized content. Each recipient receives the email in their selected language.

The email button opens the relevant platform area:

* Execution failures open **Executions**. A specific execution opens when available.
* Human ticket alerts open **Tickets**. The correct pending or ongoing ticket opens when available.
* Channel disconnections open **Channels**.
* Low-credit alerts open **Settings → Credits**.

Links preserve the workspace and version context. This ensures the destination opens in the right workspace.

For Whitelabel workspaces, emails use the active brand and custom domain. The link also opens on that domain when configured.

***

### 🔹 Delivery behavior

Disabled events never send emails. Events without valid recipients are skipped safely.

Recipient selection is available for all events except **New message in human ticket**. That event always follows its automatic routing rules.