> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Notifications

> How to configure Telegram, event categories and test sending through the panel.

A single notification setting is in **Settings → Telegram**.

## Connect Telegram

1. Open the tab **Telegram**.
2. Enable **to send notifications**.
3. Insert **Bot token** from BotFather.
4. Add the recipient: chat ID and, if the forum is used, topic ID.
5. Select event categories.
6. Press **Save**.

The saved token is not shown back. An empty field means that the current token does not change; a deletion button next to the field deletes it after saving it.

## Learn chat ID and topic ID

In the assistant block, start a helper session, then send a message to the bot from the desired chat. The panel will offer the found chat ID and topic ID - select them for the recipient.

## Categories

The category card notes health, safety, Anti-Abuse, Flow, Agent status, DNS/TLS, and Axosun reports.

Events not selected for Telegram remain in \*\*\*\* and **Audit-Journal**.

## Repeats by category

For each category, you can select **only changes** or repeat after 15, 30, 60, 180, 360 or 1440 minutes. For a category without customization, one hour is used. The interval applies to a specific problem or resource, rather than limiting all chat messages to one timer.

Raising severity to critical can notify immediately; fluctuations between warning and error should not cause alternating repetitions. Before sending, the panel rechecks the urgency of the problem. Changing the Flow version does not in itself turn an old incident into a new one.

Category **Bscheck:** availability uses [saved external reports](https://docs.axottle.com/en/health/bscheck.md). Its background repeats do not run paid checks. The joint loss of communication between the agent and Remnawave is displayed as a possible unavailability of the server; the cause is established by diagnosis, not only by the notification text.

## Relevance of Flow Reports

Before sending a Health notification, the panel double-checks the status, active version, and freshness of the observation. If Flow has already recovered, been deleted, or changed the version, the outdated message may become **Outdated - not sent by**. This is not a Telegram delivery error or a confirmation of sending.

After recovery, check the current Flow and the time of the event, not just the order of the messages, and the Axosun Diagnostic Report should not replace the fresh assessment with the old analysis.

## Check delivery

Click **Send test**. Successful check shows the message **Test message sent**; Telegram error displays next to the buttons.

## Turn it off

* To temporarily turn off the main switch and save the settings.
* For a full revocation, remove the token with a button next to the **Bot token** field and save.
* For one node, use the **button to silence** on its page.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.