> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-alerts/managing-alert-notifications.md).

# Managing Alert Notifications for Connected Devices

Configuring notifications is the critical next step after creating an alert rule. An alert is only effective if the right teams are informed when it triggers. This guide explains how to set up notifications using email, webhooks, and integrations to ensure that performance issues are communicated immediately, enabling a faster incident response.

## Choosing Your Notification Method for Connected Devices Alerts

After you define an alert rule's conditions, the next step is to configure how you want to be notified when an alert triggers. Connected Devices supports the following notification methods: email, webhooks, and integrations.

Choose the method that best fits your team's incident response workflow.

* **Email Notifications** Use email for straightforward notifications sent directly to individuals or team distribution lists. This method is ideal for general awareness or for notifying stakeholders who are not part of a formal on-call rotation. For more information, see our main documentation on [Alert Notifications via Email](https://docs.thousandeyes.com/product-documentation/alerts/standard-notification-methods/alert-notifs-via-email).
* **Webhook Notifications** Use webhooks to automate your incident response workflow by integrating with other platforms. Webhooks are the recommended method for sending alerts to:

  * **Incident Management Systems:** Automatically create tickets in platforms like ServiceNow or trigger incidents in PagerDuty.
  * **Team Collaboration Tools:** Send alerts directly to channels in Slack or Microsoft Teams.
  * **Custom Automation Scripts:** Trigger custom scripts or other internal tools.

  To use a webhook, it must first be configured under **Manage > Integrations**. For more information, see our main documentation on [Webhooks for Alert Notifications](https://docs.thousandeyes.com/product-documentation/alerts/standard-notification-methods/classic-webhooks-for-alert-notifs).
* **Integrations** Use native integrations for a simplified, out-of-the-box connection to popular third-party services. This is often the easiest way to send structured alert data to platforms like AppDynamics, PagerDuty, or Splunk. Navigate to **Manage > Integrations** to assign the alert notification to an existing integration.

  For more information, see our main documentation on:

  * [Alert Rule Notifications](https://docs.thousandeyes.com/product-documentation/alerts/alert-notifications#alert-rule-notifications)
  * [Custom-built Integrations](https://docs.thousandeyes.com/product-documentation/integration-guides/custom-built-integrations)


---

# 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://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-alerts/managing-alert-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.