set up notifications
This guide walks through creating each channel
type. The flow is the same everywhere: go to
/channels → + new channel, pick the type, give it a name, fill in
the type-specific fields, then send test ping to confirm delivery
before you attach it to a rule.
The name is just a human label and must be unique within the org —
something like ops-slack or oncall-sms. It's what shows up when you
pick channels on a rule.
Slack
Two options — an incoming webhook (simplest) or a bot token.
Incoming webhook: in Slack, create an app (or reuse one), enable
Incoming Webhooks, and add a webhook for the channel you want alerts
in. Copy the https://hooks.slack.com/services/... URL. In pngr, paste
it into webhook_url.
Bot token: if you'd rather post via a bot, paste the bot token into bot_token instead. Provide one or the other — not both.
Hit send test ping; a message should land in the Slack channel within a second or two.
Microsoft Teams
In Teams, add an Incoming Webhook connector to the target channel and copy the generated URL. In pngr, paste it into webhook_url. Test ping to confirm.
Telegram
You need a bot token and a chat ID.
- Message @BotFather in Telegram, run
/newbot, and copy the token it gives you → bot_token. - Add the bot to the group (or start a direct chat with it), then find the chat ID — the numeric id of the conversation the bot should post to → chat_id.
Both fields are required. Test ping to confirm the bot can post.
Pick email and optionally set recipient to the address that should receive alerts. Leave it blank to default to your account email.
Email is delivered through a platform-level provider, so the test ping doesn't exercise it — the test only covers self-contained channels (Slack, Teams, Telegram, webhook). The same applies to SMS below. If the deployment's email/SMS provider isn't configured, the channel still saves but delivery is a no-op.
Webhook
For anything custom — a PagerDuty Events API endpoint, your own service, an automation. Pick webhook and paste the destination into url. pngr POSTs a JSON payload describing the alert. Test ping to confirm your endpoint accepts it.
SMS
SMS uses a platform-level Twilio account; the channel only needs the destination. Pick sms and put the phone number in to. As noted above, test ping doesn't cover SMS.
rotating a credential
Channel secrets are write-only — you can't read a stored webhook URL or token back out. To rotate one, open the channel's edit page, type the new value into the field, and save. The non-secret fields (email recipient, Telegram chat ID) pre-fill; the secret fields stay blank until you type a replacement.
next
- Wire these channels into a rule →
- Channel concepts — self-contained vs platform delivery, the enable toggle.