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

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=telegram)

<CardGroup cols={5}>
  <Card title="7">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="4">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup cols={2}>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (7)">
    ### Monitor performance

    7 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (3 signals)">
        | Signal                       | Alert behaviour | What it tracks                                                                                  |
        | ---------------------------- | --------------- | ----------------------------------------------------------------------------------------------- |
        | **Bot Username**             | Watch only      | getMe.result.username as @username (fallback first\_name when a bot has no username).           |
        | **Can Join Groups**          | Watch only      | getMe.result.can\_join\_groups rendered as Yes/No; whether the bot may be added to group chats. |
        | **Reads All Group Messages** | Watch only      | getMe.result.can\_read\_all\_group\_messages rendered as Yes/No (privacy mode off = Yes).       |
      </Accordion>

      <Accordion title="Control risk and change (2 signals)">
        | Signal                 | Alert behaviour | What it tracks                                                                                                                                                |
        | ---------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Channel Configured** | 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**  | 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 |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal             | Alert behaviour | What it tracks                                                                                                                                           |
        | ------------------ | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Bot Connection** | 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 (aut |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal         | Alert behaviour | What it tracks                                                                                                                                                |
        | -------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Chat Title** | 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\_i |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

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

    #### Build your own automated fixes

    Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **3 read** and **1 write** operations across getchats, getchatmembercounts, getmes, sendmessages on Telegram. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words.

    Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution.

    [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=telegram)

    #### Ready to build your first Telegram workflow

    Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build.

    <Accordion title="Browse the operations you can build with">
      | Resource            | Read operations | Write operations |
      | ------------------- | --------------- | ---------------- |
      | getchats            | 1               | 0                |
      | getchatmembercounts | 1               | 0                |
      | getmes              | 1               | 0                |
      | sendmessages        | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>