> 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/telegram.md).

# Telegram

## How the connection HackenProof -> Telegram works <a href="#h_96139c2b18" id="h_96139c2b18"></a>

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

<mark style="background-color:purple;">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.</mark>

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

<figure><img src="https://downloads.intercomcdn.com/i/o/642793766/080469e38ca9ce1bea459edb/image.png" alt=""><figcaption></figcaption></figure>

<mark style="background-color:purple;">Note! The Telegram bot will re-send a message when changes happen with the specific report.</mark>

### Good to know <a href="#h_e2e1bcf5eb" id="h_e2e1bcf5eb"></a>

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.


---

# 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/telegram.md?ask=<question>&goal=<endgoal>
```

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