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
    • [CA] Bounty Distribution Rules
    • Fee & Payments
  • DualDefense Audit
    • What is DualDefence Audit
    • General Guidelines
    • How DualDefence Audit goes
    • Contest Phases
    • Vulnerability classification
      • [DD] Smart Contracts
    • [DD] Bounty Distribution Rules
  • good to know
    • Changelog
    • Branding
    • Vulnerability Disclosure
  • Education
    • Courses
    • Tools
    • Useful sources
Powered by GitBook
On this page
  • How the connection HackenProof -> Telegram works
  • Good to know
  1. Welcome
  2. Integrations

Telegram

Get notifications in Telegram from HackenProof about new reports, report status, and report severity changes

PreviousDiscordNextZapier (Webhook)

Last updated 1 year ago

How the connection HackenProof -> Telegram works

This guide explains how our Telegram bot can help companies when they run a bounty program at HackenProof.

Note! Telegram bot works only for the individual Telegram account, so if 5 people from your team want to get notifications in Telegram - all 5 people have to connect to the Telegram bot.

As you know, HackenProof uses a ticket-based system that has processing.

Once you connect your bug bounty program to your Telegram account, the bot will send notifications about the following:

  • new reports (that includes the Program name, Report title, Report severity, and Report URL)

  • report status changes

  • report severity changes

Note! The Telegram bot will re-send a message when changes happen with the specific report.

Good to know

  1. Telegram bot works only for the individual Telegram account, so if 5 people from your team want to get notifications in Telegram - all 5 people have to connect to Telegram bot.

  2. If you have a HackenProof account that is related to a few companies - you will get notifications from all those companies.

different stages of reports