Alert channels

A channel is a destination for alerts: an email inbox, a Slack or Discord room, a Telegram chat, your own webhook, or PagerDuty. Channels belong to a project. By default a check notifies every channel in its project, and you can attach specific channels to a check when you want finer control.

Adding a channel

Open Channels in the dashboard and click Add channel. Pick the type and fill in its one or two fields. For Slack, Discord, Telegram, a webhook, or PagerDuty you can click Send test right in the modal to confirm the destination works before you save, and for Telegram the Fetch chat id button finds the chat id for you. You can send another test from a channel's menu at any time, and switch a channel off without deleting it. Email and the phone channels need verifying before they can alert: email confirms through a link, and WhatsApp, voice, and SMS confirm through a one-time code sent to the number. The rest are ready the moment you save, because holding the webhook URL or token is proof enough that you own the destination.

Which channel should I use?

• Email. The simplest option, and where most people start. Needs a one-time verification.
• Slack and Discord. Post alerts into a team room through an incoming webhook. Good for a shared on-call channel.
• Telegram. Send alerts to a personal chat or a group through a bot.
• Webhook. A structured JSON POST to your own endpoint, for anything PingArk does not speak natively.
• PagerDuty. Open and resolve real incidents for on-call escalation, with phone and repeat-until-ack handled by PagerDuty.
• WhatsApp, voice call, and SMS. Premium channels for reaching a phone when a down really matters. They use credits and need the number verified first.

Which channels your plan includes is on the pricing page. Whatever you choose, PingArk sends one alert when a check goes down and one when it recovers, so a channel never floods.