> For the complete documentation index, see [llms.txt](https://docs.hackenproof.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackenproof.com/welcome/integrations/zapier-webhook/zapier-greater-than-pagerduty.md).
# Zapier -> PagerDuty
This guide explains how to send notifications through [Zapier](https://zapier.com/) 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](/bug-bounty/reports-basics.md) 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)
In this version, we don't send information about changes in reports like Report Status or Report Severity
### 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:
* Program name:
* Report ID:
* Report URL:
* Report Severity:
* Report Status:
* Specify Incident Key. You can use Report ID as Incident Key.
Specify your PagerDuty Integration Key as a custom field!
* 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:
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.hackenproof.com/welcome/integrations/zapier-webhook/zapier-greater-than-pagerduty.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
