Why use Hookfire with PagerDuty?

Instant push notifications

Get notified on your phone the moment a PagerDuty webhook fires. No more checking dashboards.

Subscribe to what matters

Choose exactly which PagerDuty events trigger notifications. Filter out the noise.

Team-wide delivery

Control who on your team gets notified and how: push notifications, record only, or both.

Setup in under 2 minutes

Copy a webhook URL, paste it in PagerDuty, and you're done. No code required.

Supported events

Event	Sample notification
Incident reassigned `incident.reassigned` 👤 Reassigned #2: A little bump in the road API Service - now assigned to User 123	👤 Reassigned #2: A little bump in the road API Service - now assigned to User 123
Incident priority changed `incident.priority_updated` 🔺 P1 on #2: A little bump in the road Tenex Engineer set the priority to P1 - API Service	🔺 P1 on #2: A little bump in the road Tenex Engineer set the priority to P1 - API Service
Incident unacknowledged `incident.unacknowledged` ⚠️ Unacknowledged #2: A little bump in the road The acknowledgement timed out and the incident is open again - API Service	⚠️ Unacknowledged #2: A little bump in the road The acknowledgement timed out and the incident is open again - API Service
Note added to incident `incident.annotated` 📝 New note on an incident Tenex Engineer: I sure am glad we are using PagerDuty!	📝 New note on an incident Tenex Engineer: I sure am glad we are using PagerDuty!
Incident triggered `incident.triggered` 🚨 Incident #2: A little bump in the road Triggered on API Service - high urgency	🚨 Incident #2: A little bump in the road Triggered on API Service - high urgency
Incident resolved `incident.resolved` ✅ Resolved #2: A little bump in the road API Service - resolved by Tenex Engineer	✅ Resolved #2: A little bump in the road API Service - resolved by Tenex Engineer
Incident escalated `incident.escalated` ⏫ Escalated #2: A little bump in the road API Service - escalated under Default	⏫ Escalated #2: A little bump in the road API Service - escalated under Default
Incident reopened `incident.reopened` 🔁 Reopened #2: A little bump in the road API Service - reopened by Tenex Engineer	🔁 Reopened #2: A little bump in the road API Service - reopened by Tenex Engineer
Incident acknowledged `incident.acknowledged` 👀 Acknowledged #2: A little bump in the road Tenex Engineer is on it - API Service	👀 Acknowledged #2: A little bump in the road Tenex Engineer is on it - API Service
Responder requested `incident.responder.added` 🙋 Help requested: A little bump in the road Please help me make the tests pass	🙋 Help requested: A little bump in the road Please help me make the tests pass

How to connect PagerDuty

Step 1: Create an Integration

Go to your organization’s Integrations page.
Click Add Integration and select PagerDuty.
You’ll receive a unique Webhook URL. Copy it.

Step 2: Add the Webhook in PagerDuty

In PagerDuty, go to Integrations → Generic Webhooks (v3).
Click New Webhook.
Paste your Hookfire webhook URL into the Webhook URL field.
Under Event Subscription, pick the events you want (for example incident.triggered, incident.escalated and incident.resolved).
Click Add Webhook.

To limit the webhook to one service instead, open Services → Service Directory, pick the service and use the Webhooks section of its Integrations tab.

Step 3: Copy the Signing Secret

After you click Add Webhook, PagerDuty shows a confirmation with the webhook’s secret. It is only shown once, so copy it straight away.
Go back to your Hookfire integration page and paste it into the Signing Secret field.
PagerDuty signs every delivery with HMAC-SHA256 in the X-PagerDuty-Signature header, and Hookfire verifies it automatically. During a secret rotation PagerDuty sends one signature per secret, and any one matching is enough.

If you missed the secret, delete the webhook and create it again: PagerDuty does not show it a second time.

Step 4: Subscribe to Events

On your Hookfire integration page, toggle on the events you want to receive push notifications for. Triggered and escalated incidents are the ones worth a loud alert; consider marking them high priority.

Step 5: Test

Click the Test button next to an event on your integration page. You can also use Manage → Test → Send Test Event on the webhook in PagerDuty, which sends a pagey.ping event: Hookfire accepts it but does not turn it into a notification.

Supported Events

Event	Description
`incident.triggered`	A new incident was opened
`incident.escalated`	An incident was escalated to the next level
`incident.reassigned`	An incident was reassigned
`incident.acknowledged`	Someone acknowledged an incident
`incident.unacknowledged`	An acknowledgement timed out and the incident is open again
`incident.resolved`	An incident was resolved
`incident.reopened`	A resolved incident was reopened
`incident.priority_updated`	An incident’s priority changed
`incident.responder.added`	A responder was asked to help on an incident
`incident.annotated`	A note was added to an incident

Reference: Verifying webhook signatures and Webhooks overview.

PagerDuty