> For the complete documentation index, see [llms.txt](https://docs.ispecalgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ispecalgo.com/en/isa-terminal/baza-znanii/kak-poluchat-uvedomleniya-v-telegram.md).

# Telegram notifications

ISA Terminal can send Telegram messages about terminal and bot activity, useful when it runs on a remote computer. Event details are available in [logs](/en/isa-terminal/baza-znanii/logirovanie-v-isa.md).

## What you need

A Telegram account, your own Telegram bot, its token (the key allowing the terminal to send messages as that bot), and the numeric Telegram ID of the private chat or group receiving notifications.

## 1. Create a Telegram bot

1. Open the official [@BotFather](https://t.me/BotFather).
2. Send **/newbot**.
3. Set a bot name and short searchable username.
4. Save the issued token for ISA Terminal settings.
5. Open your new bot and press **Start**.

Keep the token private: it allows control of your bot.

## 2. Choose a chat

For a **private chat**, open your bot and press **Start**; it cannot message you first without this. For a **group**, add your bot and allow it to send messages.

## 3. Find the Telegram ID

The ID is a number, not a username or chat link. [@myidbot](https://t.me/myidbot) can show your ID or a group ID. Open it, press **Start** and follow its instructions for the required chat. Copy the entire number, including a leading minus sign if present.

Finding an ID does not require your bot's token. Do not send that token to the ID bot.

## 4. Configure ISA Terminal

1. Click the account icon at the top right.
2. Open **Settings → Notifications**.
3. Enter the BotFather token in the Telegram bot token field.
4. Enter the chosen chat's number in the Telegram ID field.
5. Select the events you want to receive.
6. Save the settings.

Available events include order and position actions, connection errors, bot operation checks and others listed in settings.

On save, the terminal checks the token and attempts to send a connection-success message. There is no separate test button. Check that it arrives in the intended chat, even if settings saved successfully.

## If messages do not arrive

Check that you pressed **Start** with your own bot, copied the full token, entered the ID without spaces and with any minus sign, used the group's ID for a group, added the bot with message permission, selected at least one event and have internet access.

After changing the token or ID, save again. Sending errors appear in the [general terminal logs](/en/isa-terminal/baza-znanii/logirovanie-v-isa.md).

## Protect the token

Enter it only in ISA Terminal settings. Hide the field in screenshots or screen sharing. If someone else obtains it, replace it through BotFather.