> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/superagents/channels/telegram.md).

# Telegram

Message a superagent through a Telegram bot.

With a Telegram channel, you message a superagent through its own Telegram bot.

## Set up the channel

{% stepper %}
{% step %}

### Create a bot

In Telegram, create a new bot with **@BotFather** and copy the **bot token** it gives you.
{% endstep %}

{% step %}

### Add the channel in Zerve

Open the superagent's [settings](/zerve-docs/superagents/settings.md), go to **Channels**, and add **Telegram**. Paste the bot token.

Zerve connects to the bot automatically. There's nothing to configure on the Telegram side.
{% endstep %}

{% step %}

### Allow people to message it

Add the **Telegram user IDs** of the people who should be able to message the superagent. Until you do, it won't respond to anyone.
{% endstep %}
{% endstepper %}

## Using it

Open a chat with the bot in Telegram and send it a message. Each Telegram chat appears as a conversation in the superagent's **Zerve AI** panel in Zerve.

See [Channels](/zerve-docs/superagents/channels.md) for how access and conversations work across all channels.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zerve.ai/zerve-docs/superagents/channels/telegram.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.