Slack, Discord & Telegram Alerts Setup

PingPing alerts you as soon as a downtime is confirmed by a second check. You can receive those alerts by email, SMS (via Vonage), Slack, Discord, Telegram, or a webhook of your own. Every channel is included on every plan - there is no per-channel upcharge. Channels are configured once at the account level and then apply to all your monitors.

This page covers the three most-requested chat integrations. For email it is on by default; for SMS see the SMS notifications FAQ; for custom integrations see Webhooks.

Slack

PingPing posts alerts to a Slack channel through an incoming webhook. Setup takes about a minute.

  1. In Slack, open the workspace you want alerts in. Visit https://api.slack.com/apps and click Create New App → From scratch. Name it “PingPing” and select your workspace.
  2. Enable Incoming Webhooks in the app settings, then Add New Webhook to Workspace. Pick the channel (for example #alerts) and copy the webhook URL Slack gives you (it starts with https://hooks.slack.com/services/).
  3. In PingPing, open Account → Notification channels → Slack, paste the webhook URL, and click Test to confirm. A test message appears in the chosen Slack channel.

That is the whole setup: once saved, the channel receives alerts for every monitor on your account.

Alerts post with the monitor name and URL, the status code and failure reason, when the downtime started, and which locations detected and verified it. If the monitor is on a status page, the alert links to that too.

Discord

Discord uses the same incoming-webhook model as Slack.

  1. In Discord, open the server and channel where alerts should appear. Click the channel settings cog → Integrations → Webhooks → New Webhook. Give it a name and copy the webhook URL (it starts with https://discord.com/api/webhooks/).
  2. In PingPing, open Account → Notification channels → Discord, paste the webhook URL, and click Test. A test alert appears in the Discord channel. From then on the channel receives alerts for all your monitors.

PingPing formats Discord alerts as rich embeds with color-coded status (red for down, green for recovered) so they stand out in chat.

Telegram

Telegram uses a bot rather than a webhook URL.

  1. In Telegram, message @BotFather, send /newbot, and follow the prompts. BotFather replies with an HTTP API token that looks like 123456789:ABC-DEF1234ghIkl-zyx57W2v1u123ew11. Copy it.
  2. Create or pick the chat where alerts should land. For a personal chat, just message your new bot once. For a group, add the bot to the group and send any message so the bot can see it.
  3. Get the chat id. Open https://api.telegram.org/bot<TOKEN>/getUpdates in a browser (substitute your token). Find the "chat":{"id":...} value in the response - that is the chat id you need.
  4. In PingPing, open Account → Notification channels → Telegram, paste the bot token and chat id, click Test. The test alert lands in Telegram. From then on the channel receives alerts for all your monitors.

If you regenerate the bot token in BotFather, update the value in PingPing too - otherwise alerts will silently fail.

Using more than one channel

You can configure as many channels as you like, and PingPing fires all of them in parallel once a downtime is confirmed. Channels are account-wide: every channel receives the alerts for every monitor, and there is currently no way to route a specific monitor or severity to a specific channel.

What you can tune per monitor is the notification threshold (in the monitor’s settings): how long a downtime must last before PingPing alerts at all, from immediately up to 30 minutes. A short threshold on your production site and a longer one on staging keeps your phone quiet on transient blips without touching the channels themselves.

When alerts do not arrive

  • Test from the channel settings first. The Test button in PingPing bypasses the monitor logic and sends a synthetic alert. If that does not arrive, the integration itself is broken.
  • Check the webhook URL or token. Slack and Discord webhooks can be revoked from their respective UIs; Telegram tokens change if you regenerate them in BotFather.
  • Check the monitor’s notification threshold. An alert only goes out after the downtime has lasted longer than the threshold set in the monitor’s settings; a short outage under the threshold sends nothing on any channel.
  • Check IP whitelisting if you have any in front of Slack or Discord proxies. PingPing’s outbound IPs are the same ones listed in this FAQ.

If you need PingPing to alert into a tool we do not natively integrate with (PagerDuty, Opsgenie, an internal incident tool), use Webhooks and route from there.