> For the complete documentation index, see [llms.txt](https://docs.cherryai.com.cn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cherryai.com.cn/docs/en-us/advanced-basic/automation/channels.md).

# Channels

Channels connect an Agent to external messaging platforms. Currently Feishu, Telegram, QQ, WeChat, Discord, and Slack are configurable; the bot credentials and session identifiers required by each platform differ.

{% hint style="success" %}
It is recommended to first tell the Agent in \[Work]: “Configure a Feishu channel for the current Agent to receive group messages and send task results.” The Agent will ask for the necessary information according to the purpose, which is faster than dealing with all platform fields directly. When precise modifications are needed, use \[Settings] → \[Channels].
{% endhint %}

<figure><img src="/files/44c6860a8e8daa7e3a18a170407dd9bfc28b7ec2" alt="频道设置中的飞书、Telegram、QQ、微信、Discord 和 Slack 平台入口"><figcaption><p>First select the platform to connect, then click [Add]; different platforms require different accounts and credentials to be prepared.</p></figcaption></figure>

## Manual configuration path

\[Settings] → \[Channels] → select platform → \[Add].

{% stepper %}
{% step %}

### 1. Prepare a platform account

Create a bot or app according to the platform rules. If Feishu and WeChat support QR-code-related flows, you can complete them by following the on-screen prompts after enabling the channel; for other platforms, fill in the corresponding Token or app credentials.
{% endstep %}

{% step %}

<figure><img src="/files/15a9f7bc7f3efd7be7c982685de171ae9e28d9c5" alt="飞书频道配置中的 Agent、应用凭据、允许聊天范围和权限模式"><figcaption><p>First bind a tested Agent and restrict the allowed chat scope; only expose the parts of the credentials and permissions needed to complete the task.</p></figcaption></figure>

### 2. Bind the Agent and workspace

Select an Agent that has already been verified to work, and specify a workspace for channel messages. External messages will run in this context; do not choose a directory that contains unrelated sensitive files.
{% endstep %}

{% step %}

### 3. Restrict message sources

Fill in the allowed Chat ID, channel ID, or user ID. Leaving it blank may mean allowing all; refer to the current platform field description for details. You can first send the bot `/whoami` to obtain the correct identifier format.
{% endstep %}

{% step %}

### 4. Choose permission mode and enable

By default, \[Inherit Agent Settings] is used. Public groups, multi-user groups, or untrusted sources should use a stricter mode. After enabling, first send a test message with no side effects.
{% endstep %}
{% endstepper %}

## Recommended configuration

| Configuration item      | Product default                | Suggested starting point                        | Effect                                | Applicable scenario                         | Notes                                              |
| ----------------------- | ------------------------------ | ----------------------------------------------- | ------------------------------------- | ------------------------------------------- | -------------------------------------------------- |
| Bind Agent              | Selection required             | Prepare a separate Agent for the channel        | Decides who handles the messages      | Group chats, bot direct messages            | Do not mix with high-privilege development Agents  |
| Workspace               | Selection required             | Use a dedicated directory without private data  | Limit the files that can be processed | Collect in the group, deliver daily reports | Do not select the user's home directory            |
| Allowed message sources | Depends on the platform fields | First allow only test accounts or test groups   | Restrict who can trigger the Agent    | Internal testing, team groups               | Read the field description before leaving it blank |
| Permission Modes        | \[Inherit Agent Settings]      | Use stricter approval for external entry points | Control tool operations               | Public groups, multi-user groups            | Not recommended to use \[Full Access]              |

## Use case: team on-call group

Create an Agent that only handles the on-call handbook, bind a knowledge base that has passed recall testing and a dedicated workspace, and allow only the on-call group to trigger it. First test the two kinds of messages “check a policy” and “couldn't find the answer”, then test generating a handoff summary that does not contain sensitive information.

### Completion criteria

Non-allowed sources cannot trigger tasks; replies can be sent back to the specified group; when the knowledge base has no content, it should state that clearly; file writes will still request approval.

## Platform configuration focus

| Platform      | Primary credentials                 | Session scope focus                               |
| ------------- | ----------------------------------- | ------------------------------------------------- |
| Feishu / Lark | App ID, App Secret, or QR-code flow | Chat ID and domestic/international domain names   |
| Telegram      | Bot Token                           | Chat ID                                           |
| QQ            | App ID, Client Secret               | Private chat, group, or channel identifier format |
| WeChat        | QR-code login or credential path    | Allowed user IDs                                  |
| Discord       | Bot Token                           | Channel or private chat ID                        |
| Slack         | Bot Token, App Token                | Socket Mode and channel ID                        |

{% hint style="danger" %}
Bot Token, App Secret, and verification token are equivalent to account passwords. Do not write them into the Agent's long-term memory, task prompts, screenshots, or public Issues; if leaked, immediately revoke and regenerate them on the platform.
{% endhint %}

<details>

<summary>What should I do if I can't select a channel as the destination for a scheduled task?</summary>

First send a message to the bot proactively on the corresponding platform so Cherry Studio records the available Chat ID, then go back to the scheduled task and choose the notification target.

</details>

<details>

<summary>What should I do if the channel is connected but doesn't reply?</summary>

Check the allowed session ID, bound Agent, workspace, and permission mode, then check the channel logs. If the platform received the message but the Agent did not execute, continue by checking the API gateway and the Agent task status.

</details>


---

# 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.cherryai.com.cn/docs/en-us/advanced-basic/automation/channels.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.