Which PagerDuty events does this track?

Triggered, acknowledged, and resolved. PagerDuty's broader event catalog (annotations, escalations, priority changes) is accepted but currently treated as a no-op.

What happens if I rotate my signing secret?

The verifier accepts up to two secrets at once, so a rotation window doesn't drop deliveries — add the new secret, then remove the old one once PagerDuty is fully cut over.

No, on-call receivers are on the Business plan.

Does this create or modify anything back in PagerDuty?

No — this is inbound only. It doesn't create or modify PagerDuty escalation policies, schedules, or services.

Observability · Available now

PagerDuty integration.

Turn a triggered PagerDuty incident into a tracked, owned item. The receiver verifies PagerDuty's Webhooks V3 signature, maps triggered/acknowledged/resolved into Planoda's incident lifecycle, and fans it out from there.

Get started — free Browse all integrations

PagerDuty integration in short

The PagerDuty integration connects PagerDuty with Planoda — available now.
Turn a triggered PagerDuty incident into a tracked, owned item. The receiver verifies PagerDuty's Webhooks V3 signature, maps triggered/acknowledged/resolved into Planoda's incident lifecycle, and fans it out from there.
What you can do: Receive PagerDuty Webhooks V3 deliveries, verified with a constant-time HMAC check against your signing secret — with a rotation window that accepts two secrets at once. Map `incident.triggered` / `incident.acknowledged` / `incident.resolved` into Planoda's internal incident lifecycle; anything outside those three is accepted and no-op'd rather than erroring the delivery.
Connect it from Settings → Integrations in a few steps — no code required.

What you can do

Put PagerDuty to work.

Receive PagerDuty Webhooks V3 deliveries, verified with a constant-time HMAC check against your signing secret — with a rotation window that accepts two secrets at once.
Map `incident.triggered` / `incident.acknowledged` / `incident.resolved` into Planoda's internal incident lifecycle; anything outside those three is accepted and no-op'd rather than erroring the delivery.
Dedupe redelivered webhook events by idempotency key, so a PagerDuty retry never double-creates an incident record.
Run through the same verified-webhook pipeline (rate limit → signature → idempotency → fan-out) as Opsgenie, Rootly, and incident.io, so behavior is consistent across on-call tools.

Great for

Where PagerDuty pulls its weight.

Turn a page into a tracked, owned issue automatically instead of a Slack thread nobody closes out.

Setup

Connect PagerDuty in minutes.

Create the webhook subscriptionIn PagerDuty, add a Webhooks V3 subscription pointing at your Planoda on-call integration URL.
Copy the signing secretPagerDuty issues a signing secret at creation — paste it into Settings → Integrations → PagerDuty (shown once).
Send a testTrigger a test incident in PagerDuty to confirm the signature verifies and the incident fans out.

FAQ