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

# Telegram on Vortex IQ

> Monitor Telegram performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Telegram performance signals, run automated checks, and prepare approved work through Vortex IQ.

No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls.

| 7                   | 0                | 0              | 0                | 4              |
| ------------------- | ---------------- | -------------- | ---------------- | -------------- |
| performance signals | automated checks | prepared fixes | proven workflows | API operations |

## Monitor performance

7 performance signals. Signals with an alert band can raise Nerve Centre alerts; every signal supports a merchant-configured watcher.

| Signal                       | Outcome                 | Alert behaviour | What it tracks                                                                                                                                                                     |
| ---------------------------- | ----------------------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Bot Connection**           | Protect revenue         | Watch only      | getMe.username (fallback first\_name) rendered as 'Connected as @username'. When the token is revoked getMe fails and the card degrades to no\_data (auth\_failed).                |
| **Bot Username**             | Run operations          | Watch only      | getMe.result.username as @username (fallback first\_name when a bot has no username).                                                                                              |
| **Can Join Groups**          | Run operations          | Watch only      | getMe.result.can\_join\_groups rendered as Yes/No; whether the bot may be added to group chats.                                                                                    |
| **Channel Configured**       | Control risk and change | Watch only      | Whether the optional chat\_id credential is set, rendered as Configured / Not configured. Derived from credential presence, no API call.                                           |
| **Chat Member Count**        | Control risk and change | Watch only      | getChatMemberCount.result for the configured chat\_id. Degrades to no\_data reason chat\_id\_required when no chat\_id is set, or bot\_not\_in\_chat when the API call fails (bot  |
| **Chat Title**               | Catalogue quality       | Watch only      | getChat.result.title (fallback first\_name/id) for the configured chat\_id. Same gating as the member count: chat\_id\_required with no chat\_id, bot\_not\_in\_chat on API failur |
| **Reads All Group Messages** | Run operations          | Watch only      | getMe.result.can\_read\_all\_group\_messages rendered as Yes/No (privacy mode off = Yes).                                                                                          |

## Audit risks and opportunities

No automated checks are defined for Telegram yet; performance signals above cover the monitoring layer, and checks arrive with the connector's audit module.

## Automate approved work

The Telegram connector exposes **3 read** and **1 write** operations to Vortex IQ workflows. Changes follow the merchant's configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution.

Workflow templates for this connector arrive once proven against a live account; monitoring and audits above are available now.

***

*Generated from the connector capability graph. Counts reflect the servable registry after alias normalisation and de-duplication, and refresh automatically when the registry changes.*