If you don’t see your preferred webhook provider, you can request support for it.
- Develop and test GitHub webhooks locally without deploying to a public environment or setting up HTTPS.
- Inspect and troubleshoot requests from GitHub in real time via the inspection UI and API.
- Modify and replay GitHub webhook requests with a single click instead of reproducing events manually in GitHub.
- Secure your app with GitHub 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).
- Your GitHub account and a repository.
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
With your app running locally, expose it with 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 GitHub.
3. Configure GitHub to send webhooks
Follow GitHub’s documentation for creating a repository webhook, and set the following:- Payload URL: your ngrok URL (for example,
https://1a2b-3c4d-5e6f-7g8h-9i0j.ngrok.app). - Content type:
application/json. - Events: choose which events trigger the webhook (for this example, Just the push event).
- Secret: set a secret and note it for the verification step below.
Run webhooks with GitHub and ngrok
After you add the webhook, GitHub sends POST requests to your app through ngrok. To compare what GitHub sends with what your app receives, open the webhook’s recent deliveries, select a delivery, and compare its headers and body with what your application received; they should match.The payload your app receives depends on the events you chose.
Because this example uses Just the push event, push changes to the repository to trigger new webhook calls.
You can also redeliver a request from the webhook’s recent deliveries.
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 Traffic Inspector 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 GitHub 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
github_policy.yml. Replace{your secret}with the Secret from your GitHub webhook: -
Restart ngrok with the policy file:
- Resend a delivery from your GitHub webhook.