Notification routes send alerts about important events in your subscription to the chat tools your team already uses. You choose which connections each event goes to, and one event can go to more than one place. For example, you could send website health alerts to both a Slack channel and a Microsoft Teams channel. You'll find it under **Account → Connections → Notification routing**.

## Before you start

- Only subscription administrators can set up notification routes.
- You need at least one enabled notification connection. Notification routes work with **Slack Webhook** and **Microsoft Teams Webhook** connections. You can create one while you set up a route.
- To create a webhook connection, you need an incoming webhook URL from Slack or Microsoft Teams for the channel you want to post to. Your Slack or Teams administrator can create one.

## Events you can route

The **Notification routing** page lists these events:

- **Service limit reached**: your subscription is approaching or has reached a usage limit. See [Package and add-ons](/account-and-access/package-and-add-ons) to review or raise your allowances.
- **Website health changed**: a monitored website changes status, passing or failing its checks. See [Monitoring your sites](/assure-and-diagnose/monitoring).

## Set up a route

1. Go to **Account → Connections → Notification routing**.
2. Find the event you want to route.
3. Open the **Select** list next to it and choose one or more connections.
4. Your choice saves straight away. There's no separate save button.

To stop sending an event to a connection, remove that connection from the event's list. The change also saves straight away.

Only enabled connections appear in the list. If a connection is missing, check its **Status** on **Account → Connections**.

## Create a notification connection while you set up a route

1. Next to the event, select **Add connection**. The new connection form opens in a new window.
2. Choose **Slack Webhook** or **Microsoft Teams Webhook** as the **Provider**.
3. Give the connection a **Name** that describes the channel, for example "Ops alerts channel".
4. In **Credentials**, paste the **Webhook URL** you got from Slack or Teams.
5. Select **Save**.

When you save, the new connection is added to that event's route automatically. If you see "Popup blocked. Allow popups and try again.", allow pop-ups for Structurell and select **Add connection** again.

You can also create webhook connections first on **Account → Connections**. See [Connecting a provider](/connections/connecting-a-provider).

## Change or remove a webhook

- To send alerts to a different channel, open the connection on **Account → Connections**, enter the new **Webhook URL** and select **Save**. Every event routed to that connection uses the new channel.
- To pause alerts for a connection without changing your routes, set its **Status** to **Disabled**.
- If you delete a connection, it stops receiving every event it was routed to.

## Troubleshooting

- **"Unable to update notification routing."** Your change wasn't saved. The list reloads with the saved routes. Try again.
- **Alerts aren't arriving in Slack or Teams.** Check that the webhook URL is still valid in Slack or Teams, that the connection is enabled, and that it's selected for the event. See [Troubleshooting connections](/connections/troubleshooting-connections).
- **The connection you want isn't in the list.** Only enabled Slack Webhook and Microsoft Teams Webhook connections can be used for notifications.

## Related articles

- [Connecting a provider](/connections/connecting-a-provider)
- [Troubleshooting connections](/connections/troubleshooting-connections)