> For the complete documentation index, see [llms.txt](https://kizunai.gitbook.io/kizuna-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kizunai.gitbook.io/kizuna-docs/07.-telegram-integration.md).

# 07. Telegram Integration

## Telegram Integration

### Where the Community Already Lives

Telegram is the primary community environment for KIZUNA.

Project communities already communicate, share information, and ask questions inside Telegram. KIZUNA is designed to operate directly within this environment.

The goal is simple:

**BRING THE PROJECT KNOWLEDGE TO THE COMMUNITY.**

Instead of sending community members to different resources every time they need information, KIZUNA provides a direct way to interact with the project's knowledge inside Telegram.

### From Question to Answer

The intended interaction is straightforward.

A community member has a question about the project.

↓

The member asks KIZUNA inside Telegram.

↓

KIZUNA uses the project's connected knowledge and context.

↓

KIZUNA provides a project-specific response.

This creates a simple conversational layer between the project and its community.

### A Native Community Experience

KIZUNA is designed around the environment where the community already communicates.

Community members do not need to leave Telegram to begin interacting with the project-specific AI.

The experience can be summarized as:

**ASK → UNDERSTAND → ANSWER**

The project provides the knowledge.

KIZUNA brings that knowledge into the conversation.

### Supporting the Community

KIZUNA is designed to help project teams handle repetitive information requests by making project knowledge easier to access.

It does not replace the project team.

Instead, it provides an additional community-support layer that can remain available while the team focuses on building and managing the project.

### Project-Specific Conversations

Because each KIZUNA agent is connected to a specific project's identity and knowledge, the community experience is designed around that project.

The agent is not simply answering general questions.

It is intended to help community members access information about the project itself.

### Telegram as the Final Layer

The complete KIZUNA flow comes together inside Telegram:

**PROJECT**

↓

**PROJECT KNOWLEDGE**

↓

**KIZUNA AGENT**

↓

**TELEGRAM**

↓

**COMMUNITY**

This is where project knowledge becomes accessible through conversation.

### Integration Details

KIZUNA's exact Telegram implementation, including API architecture, bot permissions, authentication, moderation capabilities, and other technical details are:

**\[NEEDS CONFIRMATION]**

These details will be documented once the implementation is finalized.

For now, the core product principle remains:

**KIZUNA BRINGS PROJECT KNOWLEDGE DIRECTLY INTO TELEGRAM.**


---

# 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://kizunai.gitbook.io/kizuna-docs/07.-telegram-integration.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.
