# Configuring email and webhook notifications for alerts

## Email notifications <a href="#configuringemailandwebhooknotificationsforalerts-emailnotifications" id="configuringemailandwebhooknotificationsforalerts-emailnotifications"></a>

Use the **Notifications** tab to configure an email channel to inform the right team when the system has triggered an alert.

The alerting system sends an email when the alert threshold is triggered. Based on the configuration, the system can send another recovery email when the alert is no longer active. An alert is no longer active if the system has recovered an alert or the alert is auto-recovered:

* Recovery occurs when the system no longer detects the identified anomaly, meaning that the breached threshold is no longer breached.
* Auto-recovery occurs when Nexthink no longer detects the event.

When a global outage occurs, the platform may trigger several alerts at the same time. To prevent overloading email servers, Nexthink sends email notifications for the first 30 triggers per monitor only, and informs the email recipients. The full list of alerts is still visible using the Nexthink web interface, with a maximum of 500 alerts per monitor trigger.

<figure><img src="/files/BuqhEHzmV2fa48DtHiY8" alt=""><figcaption></figcaption></figure>

### Configuring email notifications

* **Subject**: Provide a meaningful subject for the email.
* **Custom message**: Write the email notification message. This field is optional and the message is appended to the default alert information which contains the monitor name, trigger time, conditions and context of the alert.
* **To**: Enter the recipient’s email address. Add multiple emails separated by a comma. This field is mandatory.
* **Cc**: Enter additional email addresses to receive the alert as a carbon copy.
* **Send email notification for**: Select **Triggered and recovered alerts** to get separate emails for both events. To focus on triggered alerts only and reduce the number of incoming emails, select **Triggered alerts only**.

## Webhook notifications <a href="#configuringemailandwebhooknotificationsforalerts-webhooknotifications" id="configuringemailandwebhooknotificationsforalerts-webhooknotifications"></a>

Use webhooks to channel notifications from the Nexthink platform to other third-party tools. Refer to the [Webhooks](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/webhooks.md) documentation for more information.

Follow the steps below to send notifications to an external system:

* Create a monitor.
* Create an outbound webhook connector. Refer to the [Managing webhooks](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/webhooks/managing-webhooks.md) page for more information.
* Create webhook notifications with a payload from alerts.

### Alert payload in the notification <a href="#configuringemailandwebhooknotificationsforalerts-alertpayloadinthenotification" id="configuringemailandwebhooknotificationsforalerts-alertpayloadinthenotification"></a>

The NQL monitor query also determines what payload is available in the notification.

<table><thead><tr><th width="372">Monitor NQL query</th><th>Email notification</th><th>Webhook notification</th></tr></thead><tbody><tr><td><pre><code>devices
...
| compute &#x3C;metric>
</code></pre></td><td>Device name and metric payload</td><td>Device name and metric payload. Additionally, you can add all properties of the associated device to the notification payload.</td></tr><tr><td><pre><code>users
...
| compute &#x3C;metric>
</code></pre></td><td>User name and metric payload</td><td>User name and metric payload. Additionally, you can add all properties of the associated device to the notification payload.</td></tr><tr><td><pre><code>...
| summarize &#x3C;metric>, ...
  by device.collector.ui
</code></pre></td><td>Device name and metric payload</td><td><p>Device name and metric payload.</p><p>Additionally, you can add all device properties to the notification payload.</p></td></tr><tr><td><pre><code>...
| summarize &#x3C;metric>, ...
  by &#x3C;dimension1>, &#x3C;dimension2>
</code></pre></td><td>dimension1 value, dimension2 value, and metric payload</td><td>dimension1 value, dimension2 value, and metric payload</td></tr><tr><td><pre><code>...
| summarize &#x3C;metric1>, &#x3C;metric2>
</code></pre></td><td>metric1, metric2 payload values</td><td>metric1, metric2 payload values</td></tr></tbody></table>

***

RELATED TOPICS

* [Webhooks](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/webhooks.md)
* [Manage webhooks](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/webhooks/managing-webhooks.md)
* [Nexthink Library](/platform/user-guide/nexthink-library.md)


---

# Agent Instructions: 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:

```
GET https://docs.nexthink.com/platform/user-guide/alerts-and-diagnostics/managing-alerts/configuring-email-and-webhook-notifications-for-alerts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.