Notification channels

This page explains where alerts go and how to add, test, and manage each channel. Channels belong to a project and are managed on its Notifications page by the project's owner or an admin.

#Push to your devices

Push notifications are always on. Every alert for a project's monitors reaches the devices its owner is signed in to with the UptimeX app. The Notifications page lists them as Your devices. There is nothing to configure.

#Channels

A project can have one channel of each kind. Every channel carries every alert for every monitor in the project, and it starts enabled.

#Add a channel

1. Open the project's Notifications page and choose the channel kind.
2. Paste the URL. For Slack, create an incoming webhook in your Slack workspace and copy its URL. For Discord, create a webhook on the channel and copy its URL. For email, choose Turn on, and the channel is created with your account's email address.
3. Save. The destination is encrypted at rest and never shown again. The list shows only its host, or a masked address for email.

#Send a test

Open a saved channel and choose Send test. UptimeX sends the text UptimeX test alert: this channel is wired up correctly. and shows whether the destination accepted it. Unsaved changes have to be saved first, since the test goes to the stored destination.

#Switch off, change, or delete

Each channel has a switch. A switched-off channel receives nothing until you switch it back on. Open a channel to change its URL or address. Deleting a channel takes effect at once and cannot be undone, since UptimeX cannot show you the destination again.

#What a webhook receives

A webhook channel gets a POST with Content-Type: application/json and this body:

{
  "event": "monitor.status_change",
  "text": "Public API is down: HTTP 503",
  "monitor": "Public API",
  "monitor_id": "abcdefghijklmnopqrst",
  "from": "up",
  "to": "down",
  "detail": "http_503",
  "http_status": 503,
  "downtime_sec": null,
  "at": 1730000000000
}

from and to are up, down, or slow. detail is the raw check detail, such as timeout, http_503, slow_4123ms, or a JSON object for a failed content rule. downtime_sec is set on recovery alerts. at is the time in milliseconds since the Unix epoch. A test alert sends only text.

The request carries no signature. Keep the URL secret, and treat it as the credential.

#What the alert text says

The reason after is down is the check's detail in words: Request timed out, Couldn't connect, SSL certificate problem, HTTP 503, Got HTTP 200, expected 201, or the content rule that failed. Push notifications use the same wording as a title and body. Email uses it as the subject, with the detail, the HTTP status, the downtime, and a View monitor link in the body.

#Email limits

Email channels send up to 30 messages a day and 500 a month on Pro, and 100 a day and 1,500 a month on Team, counted per account across its projects. When a limit is reached, one notice email tells you so and further email alerts wait until the next day or month. Push and the other channels are unaffected.

#Notification settings

The gear on the Notifications page opens the settings that decide which events alert at all:

• This project: Down, Slow, and Recovery. Each follows your account's setting unless you override it here.
• Your account: Certificate expiry and Domain expiry, which control the push warnings from SSL and domain expiry.

#What's next?

• When alerts fire: the rules that turn a failed check into one of these messages.
• Incident policy: the timing that every alert follows.