If you don’t see your preferred webhook provider, you can request support for it.
- Develop and test Airship webhooks locally without deploying to a public environment or setting up HTTPS.
- Inspect and troubleshoot requests from Airship in real time via the inspection UI and API.
- Modify and replay Airship webhook requests with a single click instead of reproducing events manually in your Airship account.
- Secure your app with Airship 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).
- An Airship 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 Airship.
3. Configure Airship to send webhooks
Airship sends webhooks through Open Channels. Follow Airship’s documentation for configuring an Open Channel, and set the following:- Webhook URL: your ngrok URL (for example,
https://1a2b-3c4d-5e6f-7g8h-9i0j.ngrok.app). - Display Name and Name: label the Open Channel (for example,
My Local Webhook) so you can select it when sending a message and secure it later.
Run webhooks with Airship and ngrok
Airship sends different request bodies depending on the event that is triggered. To trigger a webhook call, send a message to your Open Channel from Airship, selecting it as the delivery channel. Confirm your app receives the notification and logs the headers and body in the terminal.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 Airship 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.
- In your Airship app, go to Settings, Open Channels under Channels, and click Edit on the My Local Webhook tile.
-
Select Signature in Authentication, enter a value in Secret Key (for example,
12345), and click Update. -
Create a Traffic Policy file named
airship_policy.yml. Replace{your secret}with the value from Secret Key: -
Restart ngrok with the policy file:
- Create a new message in Airship to trigger a webhook.