> 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.md).

# Automation and External Reach

Cherry Studio’s automation is not a separate set of “bot settings.” Agent is responsible for doing the work, channels are responsible for sending and receiving messages with external platforms, scheduled tasks are responsible for starting the Agent at specified times, and heartbeats are used to let the Agent periodically check its ongoing work.

<figure><img src="/files/4913f5d239cd41fad83d6407973bc4e0d2849c36" alt="定时任务、心跳或频道触发 Agent 执行并发送结果的自动化关系图"><figcaption><p>Triggering, execution, notification, and run history are different stages; first get the Agent running manually, then connect it step by step.</p></figcaption></figure>

## How the four work together

| Capability      | What it is responsible for                         | Typical uses                                        |
| --------------- | -------------------------------------------------- | --------------------------------------------------- |
| Agent           | Executes tasks and generates results               | Summarization, checking, writing, file processing   |
| Channels        | Receives external messages and sends notifications | Feishu group bot, Telegram direct message           |
| Scheduled tasks | Run the Agent at a specified time                  | Daily reports, weekly reports, one-time reminders   |
| Heartbeat       | The Agent checks ongoing work at intervals         | Monitor long-running processes, check pending items |

<figure><img src="/files/e223660288c412279f29ebf3bd1b4b1d12975ae4" alt="频道设置中的平台列表和添加入口"><figcaption><p>Channels are responsible for connecting the Agent to Feishu, Telegram, QQ, WeChat, Discord, or Slack.</p></figcaption></figure>

## Correct configuration order

{% stepper %}
{% step %}

### 1. First get the task running in \[Work]

Confirm that the Agent’s model, prompt, working directory, and tools can consistently produce the expected results.
{% endstep %}

{% step %}

### 2. Then let the Agent guide channel configuration

In the Agent conversation, explain the platform and purpose, for example: “Connect this Agent to a Feishu group to receive daily report requests.” Follow the prompts to prepare bot permissions and credentials.
{% endstep %}

{% step %}

### 3. Use manual settings to verify status

Open \[Settings] → \[Channels], check the credentials, bound Agent, workspace, allowed session scope, and channel permission mode, then send a test message.
{% endstep %}

{% step %}

### 4. Finally create the scheduled task

You can have the Agent create it directly, or open \[Settings] → \[Scheduled Tasks] → \[New]. Select the verified Agent, workspace, time, and notification channel.
{% endstep %}
{% endstepper %}

## Pre-launch checklist

* Channels only allow the required session or channel IDs;
* External entry points use \[Inherit Agent Settings] or stricter permissions;
* The scheduled task prompt does not include secrets or paths that may change;
* Manually \[Run] it once first and check the run log;
* If it fails, you can find the corresponding task inside Cherry Studio, so “not sent” is not mistaken for “not executed.”

## User case: weekday operations daily report

The “Operations Daily Report” Agent reads data from the working directory and generates daily reports according to team skills. The Feishu channel is responsible for delivering the results to the designated group, and the scheduled task runs every weekday morning. Before going live, first run it manually, then send a message to the bot in Feishu to establish the receiving target, and only then enable the schedule.

<details>

<summary>What is the difference between heartbeat and scheduled tasks?</summary>

Heartbeat has the Agent check ongoing work at intervals, which is suitable for “is there anything new?”; scheduled tasks have a clear execution plan and run history, which is suitable for “what to do at what time every day.” For fixed daily reports, scheduled tasks are preferred.

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