This guide explains how to send notifications through Zapier WebHook to the PagerDuty app
How the connection HackenProof -> Zapier Webhook works
This guide explains how our Zapier WebHook can help companies when they run a bounty program at HackenProof.
Please note! It's Zapier Webhook integration, not Zappier App
As you know, HackenProof uses a ticket-based system that has different stages of reports processing.
Once you connect your bug bounty program to your Zapier account, the bot will send notifications about the following:
new reports (that includes the Program name, Report title, Report severity, and Report URL)
Step 1. Generate your ZapierHook URL
Navigate to the Zapier dashboard
Create a new Zap
Choose Trigger: Webhooks by Zapier
Choose the Event type: Catch Hook
Press the Continue button:
Pick off a Child Key and press Continue. Here you can name it as you wish.
Copy the ZapierHook URL:
Step 2. Add the copied ZapierHook URL to HackenProof:
Navigate to your Program integration section and choose Zapier:
Paste your copied ZapierHook URL and press Connect button
Press Test Webhook:
Step 3. Connect your PagerDuty app to send notifications about incoming HackenProof reports
So now you need to find your App
Now, you need to find and connect Zapier to your PagerDuty space
Choose your PagerDuty account and event type: Add Trigger Event. Then press the Continue button
Specify your PagerDuty Integration Key (Note! you can add it as a custom field):
Integration Key can be found in the PagerDuty space: Service -> Service Directory -> Navigate to your Service space -> Integration tab
Open the settings of the created Zapier integration and copy the Integration Key
If you don't have Zapier integration yet, then press the Add an integration:
find Zapier App and press the Add button:
Add Description. Here you can all the necessary information that ZapierHook offers you, for example:
Specify Incident Key. You can use Report ID as Incident Key.
Add optional fields if it's required by your team and press the continue button:
Now you can test your connection and publish the Zap
Here is how the result looks like in our demo space: