> 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-lark.md).
# Zapier -> Lark
How the connection HackenProof -> Zapier Webhook works
This guide explains how our[ Zapier](https://zapier.com/) WebHook can help companies with notifications 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](https://docs.hackenproof.com/bug-bounty/reports-basics) processing.
Once you connect your bug bounty program to your[ Zapier account](https://zapier.com/), the Zapier will send notifications about the new reports (that include the Program name, Report title, Report severity, Report URL etc.)
### Step 1. Generate your Zapier Webhook URL
* Navigate to your Zapier dashboard.
* Create a new Zap.
* Choose Trigger: Webhooks by Zapier.
* Choose the Event type: **Catch Hook.**
* Click the '**Continue'** button.
* Pick off a Child Key and press the '**Continue'** button. **You can name Child Key as you wish.**
* Copy the Zapier Webhook URL.
### Step 2. Add the copied Zapier Webhook URL to HackenProof
* Navigate to your Program Integrations section and choose Zapier.
* Paste your copied Zapier Webhook URL and **press the Connect button.**
* Press the **Test WebHook** button to test the connection (it will send the latest report data to Zapier).
* Back to your Zapier and click the '**Test Trigger'** button.
* As a result, you will see a data record. Click the '**Continue with the selected record'** button**.**
### Step 3. Connect your Lark Suite
* In this guide, we are going to use [Lark Suite](https://www.larksuite.com/). Before starting working with Lark, you need to connect your Lark account in the Zapier App: Navigate to your Zapier Account and make sure you have the necessary connected app.
* Now navigate to your ZAP to continue creating it: choose Action.
* Find and add Lark.
* Chose the event type **Create New Lark Task (or other event).**
* Click the **'Continue'** button.
* **Action**. Now specify, please, data about your Lark project (the data in the screenshot is just an example).
* In the Summary and Description fields, you can add pre-description as shown on the screenshot:
* Report Title
* Program name:
* Report ID:
* Report URL:
* Report Severity:
* Report Status:
* Report Target Type
* Specify data in other required and optional fields, and click the '**Continue'** button.
* Now you can Test the Zap.
* If everything works for you, Publish the ZAP.
* Check your Lark project.
* If you open any issue ticket you can see the requested data.
---
# 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-lark.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.
