Notification Channels

Overview

Notification channels are configured per user, not per monitor. A trigger decides who gets told; each recipient's own profile decides how they are told.

Set yours under Account → My Profile → Notifications. Account owners can also set channels on behalf of other users and contacts under Account → Users — see Team & Contacts.

Every channel you fill in receives every alert addressed to you. There is no per-channel filtering by severity or monitor.

Available channels

Channel	What you supply
Email	Nothing — uses your account email. A toggle turns it on or off.
In-app	Nothing — always on
Pushover	Your Pushover user key
Telegram	Your Telegram user ID
Slack	An incoming webhook URL
Microsoft Teams	An incoming webhook URL
Google Chat	A webhook URL
Discord	An incoming webhook URL
Webhook	Any URL that accepts a POST

Email

On by default, sent to your account's email address. Turn it off with the Email Notifications toggle if you would rather be reached another way.

This toggle controls alert email only. It does not affect your weekly and monthly uptime reports, which have their own toggles, and it does not stop transactional email like password resets.

In-app notifications

Alerts appear in the bell menu inside Pingniner. This is always on and needs no setup.

Pushover

Enter your Pushover user key in the Pushover field. You can find it on your Pushover dashboard after signing in.

Pingniner sends alerts at high priority with the "incoming" sound, so they cut through a quiet-hours setting on your device.

Telegram

Enter your Telegram user ID, not your @username. To find it, message IDBot and it will reply with your numeric ID.

WARNING

Telegram will not deliver messages from a bot you have never spoken to. Send any message to Pingniner Bot once, before you expect alerts, or they will silently go nowhere.

Slack

Create an incoming webhook for the channel you want alerts in, then paste the URL into the Slack field.

The webhook URL already encodes the destination channel, so pick the channel when you create it in Slack.

Microsoft Teams

Create an incoming webhook connector on the Teams channel you want, then paste the URL into the Microsoft Teams field.

Google Chat

Create a webhook on the Google Chat space you want alerts in, then paste the URL into the Google Chat field.

Discord

Create an incoming webhook on the Discord channel you want alerts in, then paste the URL into the Discord field.

Alerts arrive as a Discord embed — red for a new incident, green for a recovery — with the monitor, the trigger and a link straight to it in Pingniner. The timestamp is sent in a format Discord renders in each viewer's own timezone, so a shared channel reads correctly for everyone regardless of where they are.

TIP

Discord webhook URLs are channel-specific. Create one per channel you want alerting in, and treat the URL as a secret — anyone holding it can post to that channel.

Custom webhook

Enter any URL and Pingniner will POST JSON to it when an alert fires. Use this to reach anything without a dedicated integration — PagerDuty, Opsgenie, or your own handler.

The request has a User-Agent of Pingniner and a body of:

{
  "message": "Incident: My Website - Offline @ 2026-08-27 14:32:00"
}

The timestamp is rendered in the recipient's own timezone. The same shape is sent when an incident closes, with recovery wording.

SMS

SMS is not currently available to configure. The account settings expose a phone number, and the platform supports Twilio and MessageBird, but the SMS toggle is disabled in the interface and delivery depends on a provider being configured by Pingniner.

Treat SMS as unavailable when planning your alerting. If you need alerts on a phone, use Pushover or Telegram — both push to a mobile device and neither costs per message.

Testing your setup

There is no "send test notification" button. The quickest safe test is:

1. Create a Ping monitor pointing at an address that will not answer, such as 192.0.2.1 — a reserved documentation address.
2. Set its Offline trigger to 1 occurrence and add yourself as a contact.
3. Wait for the check interval, confirm the alert arrives on every channel you configured.
4. Delete the monitor.

Troubleshooting

No notifications at all Check the trigger's Contacts list. A trigger with no contacts opens incidents silently.

Email not arriving Confirm Email Notifications is on in your profile, then check spam. Alerts come from the Pingniner sending domain.

Telegram silent You almost certainly have not messaged the bot yet. See the warning above.

Slack, Teams, Google Chat or Discord silent Webhook URLs stop working when the app, connector or webhook is deleted. Re-create it and paste the new URL. For Discord, deleting the channel also invalidates its webhook.

Too many notifications Raise Occurrences on the noisy trigger, or turn off Repeating notifications. See Triggers & Incidents.

Notifications during planned work Schedule a maintenance period rather than disabling triggers.