> For the complete documentation index, see [llms.txt](https://docs.storychain.ai/storychain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storychain.ai/storychain/community-engagement-system/how-to/connect-your-telegram-group-channel.md).

# Connect your Telegram Group / Channel

{% embed url="<https://www.youtube.com/watch?v=DiSP9UYNDH0>" %}

*Connecting your Telegram group or channel to StoryChain takes just a few seconds!*

To get started, head over to the **Groups** section in your **Settings**.

Here’s how it works:\
1️⃣ First, add **@StoryChainBot** to your Telegram group.\
2️⃣ Then, in the group chat, type `/allowgeneration yourprojectname`.\
3️⃣ After that, you’ll see your Telegram group show up under **Telegram Groups**, waiting for approval. Just click **Approve**, and you’re all set!

Your community can now start creating stories directly from Telegram! It’s that easy.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.storychain.ai/storychain/community-engagement-system/how-to/connect-your-telegram-group-channel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
