Integrations · PagerDuty

PagerDuty incident notifications on your phone

A push when an incident is triggered, acknowledged or resolved on a service, with the incident's title and urgency and the incident one tap away.

PagerDuty's own page was read on 12 September 2026 for every step below. If a menu has moved since, write to hello@youlmk.com and it is corrected the same day.

What PagerDuty sends

Version 3 webhooks: incident.triggered, incident.acknowledged, incident.resolved and the rest, as JSON with the event type and the incident's title, status, URL and urgency.

What arrives in the inbox

Title
The incident's title
Priority
normal; set the source's Reach for how loud an incident should be
Group
the event type
Button
The incident's page

Set it up

In YouLMK, create a source of type webhook named after the service, and copy its webhook URL: youlmk.com/w/k_7hq2nk3f9qd8w4 with your own key. Then:

  1. In PagerDuty, open Services, then Service Directory, then the service, then the Integrations tab, and scroll to Webhooks.
  2. Click Add or manage webhooks for this service, then New Webhook.
  3. Paste your source's webhook URL from YouLMK as the Webhook URL, choose the events under Event Subscription, then Add Webhook.

Make it quiet where it should be

Everything above lands with the source's own rules: its Reach (Silent, Badge, Banner, Break through), whether quiet hours hold it, and grouping of repeats into one card. Set them once on the source, in the app or at app.youlmk.com; the service never has to change. Unknown fields arrive as rows on the card, up to six; the whole request is capped at 8 KB (Webhooks).

Try it

The trial is 10 notifications and 3 watches, no card. Get your key, or read the webhooks reference first.

Source

support.pagerduty.com/docs/webhooks, read 12 September 2026.