Alerts → Channels → Add channel. A channel is one destination. It receives alerts for every monitor in the account unless you select monitors or groups on its page, and you can have as many channels as you like.
The ten types
| Type | What you give us | Confirmed by |
|---|---|---|
| an address | a link in a confirmation email; press the button on that page | |
| Telegram | nothing: open the Connect Telegram link, or add the bot to a group and send /start <token> there |
the bot replying "Connected to …" |
| Slack | an incoming-webhook URL from Slack | a "PingWise is connected" message |
| Microsoft Teams | a Workflows webhook URL (the old Office 365 connector and logic.azure.com links are refused) | the same |
| Discord | a channel webhook URL | the same |
| Google Chat | a space webhook URL | the same |
| PagerDuty | a 32-character Events API v2 integration key; tick EU service region if your account is there | a change event, which pages nobody |
| Pushover | your user or group key; optionally your own app token, one device, and Emergency priority | a test message |
| ntfy | the topic URL, and an access token if the topic needs one | a test message |
| Webhook | an https URL without a username or password; private and reserved addresses are refused | created at once; see Webhooks |
Chat services must be given their official webhook URLs, over https; a URL the service refuses means the channel is not created. Keys and URLs are stored encrypted and never shown again: to change one, remove the channel and add it again.
Pushover emergency priority repeats the message every 60 seconds for up to an hour until someone acknowledges it on their phone, and the repeat is cancelled when the monitor recovers.
Per-channel settings
- Delay: alert immediately, or only after the monitor has been down for 2, 5, 10, 15, 30 or 60 minutes. If it recovers inside the delay, neither the outage nor the recovery is sent.
- Reminders while down: never, or every 5, 10, 15, 30 or 60 minutes, or every 4 hours, at most 15 per outage. PagerDuty never gets reminders; it has its own escalation.
- Also alert when a WAF blocks our probes: on by default.
- Monitors and groups: leave empty for every monitor, or pick some. A group covers monitors added to it later.
- Resellers can tick Also alert for my customers' monitors.
On the channel page
Send test once the channel is ready (on PagerDuty it opens a real incident and resolves it at once), Enable / Disable, Remove, and a log of the last 20 alerts sent to it. An email address that bounces or is marked as spam stops receiving until you press Try again.
What is not there
No SMS, no voice calls, no acknowledgement inside PingWise, no quiet hours and no escalation chains: for those, hand the alert to PagerDuty or Pushover, which do them well.
Last change: 31 October 2026.