HackenProof Docs
  • Welcome
    • HackenProof
      • Services we provide
      • Our resources
    • Integrations
      • Slack
      • Discord
      • Telegram
      • Zapier (Webhook)
        • Zapier -> Lark
        • Zapier -> Linear
        • Zapier -> Jira Service Management
        • Zapier -> PagerDuty
        • Zapier -> Google Chat
        • Zapier -> ClickUp
      • Jira Software
      • GitHub Issue
      • GitLab Issue
      • VDP iFrame
    • FAQ
      • Audit & Bug Bounty (BB)
      • Crowdsourced Audit & BB
      • Penetration testing & BB
    • Emergency
      • Reset 2FA
    • Code of Conduct
    • Referral Program
  • Bug Bounty
    • Bug Bounty process
    • How to start Bug Bounty
    • How to create a VDP
    • Vulnerability classification
      • Web & Mobile
        • Out-of-Scope Bugs
      • Smart contracts
      • Blockchain protocols
    • Reports Basics
      • Points Guide
      • Crafting a well-readable report
  • Dashboard
    • Company dashboard
      • Manage programs
      • Manage reports
      • Share report
      • Labels
      • E2E report encryption
      • Reports decrypting with Mailvelope
      • Users and roles
      • Program/Report Assignee
      • Replenish your balance
      • Integrations
    • Hacker dashboard
      • 👉How to start
      • Submit a report
      • Reports Basics
      • Vulnerability classification
      • 👮‍♂️KYC
      • Сreate a crypto wallet
      • 💸Withdraw bounty
      • Hacker Leaderboard
      • Reset 2FA
      • 🍕HackenProof community
      • Report ID
      • Private Program
      • Contact support
    • Company-Auditor dashboard
      • How to start
      • Add members
      • Submit report
      • Contact support
  • Crowdsourced audit
    • Audit process
    • How to start Audit
    • Supported tech
    • Vulnerability classification
    • Reports Basics
    • Qualified Auditors
    • Judging / Triaging
      • Targets
      • Team
    • Fee & Payments
  • DualDefense Audit
    • What is DualDefence Audit
    • How DualDefence Audit goes
    • DualDefence Audit — researchers' perspective
  • good to know
    • Changelog
    • Branding
    • Vulnerability Disclosure
  • Education
    • Courses
    • Tools
    • Useful sources
Powered by GitBook
On this page
  • Step 1. Generate your Zapier Webhook URL
  • Step 2. Add the copied Zapier Webhook URL to HackenProof
  • Step 3. Connect your Lark Suite
  1. Welcome
  2. Integrations
  3. Zapier (Webhook)

Zapier -> Lark

Get notifications in Lark from HackenProof about new reports

PreviousZapier (Webhook)NextZapier -> Linear

Last updated 1 month ago

How the connection HackenProof -> Zapier Webhook works

This guide explains how our 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 processing.

Once you connect your bug bounty program to your, 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

  • 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.

In this guide, we are going to use . 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.

Lark Suite
Zapier
different stages of reports
Zapier account