> For the complete documentation index, see [llms.txt](https://docs.decube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decube.io/data-quality-v2/alerts/alert-channels.md).

# Alert channels

The destinations an alert rule can deliver to, and what each one needs before it will work.

## Alert channels

An alert rule delivers through one or more channels, added in **Set up alert channels** while you build the rule. Email works with nothing but an address. The other three connect Decube to a system you own, so each needs a one-time setup on that side before the rule can reach it.

| Channel             | What you enter on the rule                    | Set up first                                           |
| ------------------- | --------------------------------------------- | ------------------------------------------------------ |
| **Email**           | The address to notify                         | Nothing                                                |
| **Slack**           | The channel to post in                        | Authorize your Slack workspace, once per organization  |
| **Webhook**         | An `https://` endpoint, plus optional headers | An endpoint that accepts our payload                   |
| **Microsoft Teams** | The Teams webhook URL                         | A Workflow on the Teams channel that produces that URL |

One rule can carry several channels, including more than one of the same type, so a single incident can post to Slack and email a team at the same time. Use **Add a new channel** to keep adding rows, and the minus control on a row to remove one.

### Email

Select **Email** on a channel row and enter the address to notify. Each email covers one incident and gives you the monitor that failed, the asset it watches, the evidence captured at the moment of failure, and a link through to the case.

{% hint style="success" %}
**Suggested best practice:** For a team, point the rule at a distribution list or shared inbox rather than individual addresses. People join and leave teams more often than rules get revisited.
{% endhint %}

If Decube reports the alert as delivered and nothing reaches the inbox, the message is being filtered on the receiving side. Ask your email administrator to allow Decube's alert sender `alerts@decube.io`.

### Test alert

Every channel row has a **Test alert** button. It sends a fixed sample message through the real delivery path, so a message arriving confirms the destination is wired up correctly. A test send skips rule evaluation and carries no incident data, so it tells you the plumbing works rather than whether your rule matches anything.

{% hint style="success" %}
Test every channel before you rely on the rule. A wrong Slack channel or a stale Teams URL only shows up when an incident fires, which is the worst moment to find out.
{% endhint %}

### Where delivery is recorded

Every case shows the destinations its alerts went to and whether each delivery succeeded, so you can tell a rule that never matched from a channel that refused the message.

<figure><img src="https://1779874722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTw0qpCVzfrIXqS4FEg4T%2Fuploads%2FXGb5Njlhyzy7yoGxQDW1%2FSCR-20260917-pgmd.png?alt=media&amp;token=f653fde5-1149-48f9-815d-921c8adf63bf" alt=""><figcaption></figcaption></figure>

### Set up a channel

{% content-ref url="/pages/HrMGKTwkBMb5gDZUISmS" %}
[Slack](/data-quality-v2/alerts/alert-channels/slack.md)
{% endcontent-ref %}

{% content-ref url="/pages/KBNNdttvd7aXoPLSP7nL" %}
[Microsoft Teams](/data-quality-v2/alerts/alert-channels/microsoft-teams.md)
{% endcontent-ref %}

{% content-ref url="/pages/SA220yjyDeBFzEEnlAYa" %}
[Webhook](/data-quality-v2/alerts/alert-channels/webhook.md)
{% endcontent-ref %}