An alert is only useful if it reaches a person who will act on it. This page shows how to set up each channel. Each channel also has its own page with more detail, which this page links to instead of repeating.

Where channels live

Open "Alerts" in the menu. The page is called "Notifications". It has four parts: "Where alerts go", "What you get", "Reports & news", and "History". Open a row under "Where alerts go" to set that channel up.

Only the owner of the account can change channels. Other members see the page read-only.

If your plan does not include a channel, its row says "Not on your plan". If you move to a smaller plan later, the saved address is kept, and the row says "Stopped: not on your plan" until you upgrade again.

Channel Plan
Email Every plan
Telegram Every plan
Discord From Starter
Webhook From Starter
Slack From Business
Microsoft Teams From Business

The "What arrives where" table on the same page shows, for your account, which alert goes to which channel.

Note

The channel pages say whether delivery to the live service has been verified. Where it is marked as not yet verified, treat your own test message as the proof.

Email

Email needs no setup. Each website has an "Alert email" in its settings, and it starts as the address you signed up with. To use a different address, change it in the website settings. The new address has to be confirmed by a link first, and alerts keep going to the old address until then.

To test, open Notifications and press the button that sends a test letter to the address. You can send three test letters per hour. If the letter does not arrive, look in the spam folder.

Telegram

  1. Press "Connect Telegram".
  2. Press "Open Telegram". This opens a chat with the UptimeWire bot.
  3. Press Start in Telegram. The bot answers that it is connected.
  4. Return to your account and reload the page if the card still shows Telegram as not connected.

Telegram links one private chat, not a group. If you block the bot, the chat is disconnected and you have to connect it again. Press "Send a test message" to test it (three per hour). More detail: Telegram.

Discord

  1. In Discord, open the settings of the channel that should receive alerts, then Integrations, then Webhooks.
  2. Press "New Webhook".
  3. Press "Copy Webhook URL".
  4. Paste the address into the Discord row in your account and save it.
  5. Press "Send test message".

More detail: Discord.

Webhook

A webhook sends a signed JSON message to an address you control.

  1. Open the Webhook row and enter an https address. Private or internal addresses are refused.
  2. Press "Save address". UptimeWire shows a signing secret. Store it where your receiving code can read it. "Make a new secret" replaces it, and the old one stops working at once.
  3. Choose the message format. Format 1 sends only outages and recoveries. Format 2 sends every kind of alert.
  4. Press "Send test message", then look at the delivery log, which lists every message.

Your address has to answer with a 2xx status within 5 seconds. Redirects are not followed. A failed message is retried: at once, then after 1, 5, 30, and 120 minutes, and then it is marked as failed. The same message can arrive twice, so make your receiver tolerate repeats. More detail: Webhooks.

Slack

  1. Open "your Slack apps" (api.slack.com/apps) and create an app from scratch.
  2. Turn on Incoming Webhooks and press "Add New Webhook to Workspace".
  3. Choose the channel, allow it, and copy the address that starts with https://hooks.slack.com/services/.
  4. Paste it into the Slack row in your account and press "Connect".
  5. Press "Send test message".

More detail: Slack.

Microsoft Teams

  1. In Teams, open the Workflows app and search for "webhook".
  2. Choose a template that posts to a channel when a webhook request is received, and pick the team and channel.
  3. Save it and copy the address shown on the workflow's page.
  4. Paste the address into the Teams row in your account and save it.
  5. Press "Send test message".

The workflow belongs to the person who made it. If that person leaves, give the workflow a second owner, or the alerts may stop. Old webhook.office.com addresses are refused, because Microsoft stopped that kind of address. More detail: Microsoft Teams.

If an alert does not arrive

  • Look at "History" on the Notifications page. It lists recent alerts.
  • Send a test message on the channel. If the test arrives and a real alert did not, check "What arrives where": it shows whether that kind of alert goes to the channel.
  • Check the plan. A channel your plan does not include shows "Not on your plan".
  • Email: look in the spam folder and check that the alert address of the website is the one you expect.
  • Telegram: make sure you did not block the bot, and reconnect if the card shows it as not connected.
  • Webhook, Slack, Discord, Teams: the receiving address may have been deleted or changed at the other end. Create a new one and save it again.
  • Keep email on as well. No service can promise that an alert arrives, so a second route protects you.

If none of this helps, see Contact Support.