- Develop and test PagerDuty webhooks locally without deploying to a public environment or setting up HTTPS.
- Inspect and troubleshoot requests from PagerDuty in real time via the inspection UI and API.
- Modify and replay PagerDuty webhook requests with a single click instead of reproducing events manually in your PagerDuty account.
- Secure your app with PagerDuty webhook validation provided by ngrok. Invalid requests are blocked by ngrok before reaching your app.
What you’ll need
- An ngrok account and your authtoken.
- The ngrok agent installed.
- Node.js installed (for the sample app, or use your own app).
- A PagerDuty account.
1. Start your app
For this tutorial, you can use the sample Node.js app on GitHub. To install the sample, run the following in a terminal:http://localhost:3000.
The app logs request headers and body in the terminal and shows a message in the browser.
2. Expose your app with ngrok
Once your app is running locally, you’re ready to put it online securely using ngrok.- Copy your ngrok authtoken from the dashboard.
-
Start ngrok:
- Copy the URL ngrok displays. Your app is now exposed at that URL for use with PagerDuty.
3. Configure PagerDuty to send webhooks
PagerDuty can send webhook requests to your app when events occur in your account. To register for those events:- Sign in to PagerDuty.
- Click Integrations and then Generic Webhooks.
- On Your Webhooks, click + New Webhook for your application.
- On New Webhook, enter your ngrok URL in WEBHOOK URL (for example,
https://1a2b-3c4d-5e6f-7g8h-9i0j.ngrok.app). - Select Service as SCOPE TYPE, select a service for SCOPE, click Select all under EVENT SUBSCRIPTION, and click Add Webhook.
- In the Webhook subscription created popup, click Copy to copy the webhook payload signing secret for verification, then click OK.
- Click your new webhook, scroll to Test, click Send Test Event, and Yes, Send Event.
Run webhooks with PagerDuty and ngrok
PagerDuty sends different request body contents depending on the event. To trigger new calls from PagerDuty to your app:- Go to Services and Service Directory, then + New Service.
- Create a service (click Next until Integrations, then Create service without an integration).
- On the service page, click New Incident, select your service, enter a title, set Urgency to Low, and click Create Incident.
Inspecting requests
ngrok’s Traffic Inspector captures all requests made through your ngrok endpoint to your localhost app. Select any request to view detailed information about both the request and response.To avoid exposing secrets, accounts only collect traffic metadata by default.
You must enable full capture in the Observability section of your account settings to capture complete request and response data.
- Validate webhook payloads and response data
- Debug request headers, methods, and status codes
- Troubleshoot integration issues without adding logging to your app
Replaying requests
Test your webhook handling code without triggering new events from your service using the Traffic Inspector’s replay feature:- Send a test webhook from your service to generate traffic in your Traffic Inspector.
- Select the request you want to replay in the traffic inspector.
-
Choose your replay option:
- Click Replay to send the exact same request again
- Select Replay with modifications to edit the request before sending
- (Optional) Modify the request: Edit any part of the original request, such as changing field values in the request body.
- Send the request by clicking Replay.
Secure webhook requests
ngrok can verify that incoming requests are from your PagerDuty webhook so only that traffic reaches your app.Webhook verification is limited to 500 validations per month on free accounts.
If you need more, you can upgrade to Hobbyist or Pay-as-you-go.
See TPU Pricing for details.
-
Create a Traffic Policy file named
pagerduty_policy.yml. Replace{your webhook payload signing}with the value you copied when creating the webhook: -
Restart ngrok with the policy file:
- Create a new incident in PagerDuty to trigger the webhook.