Automation and external outreach

Channels, scheduled tasks, heartbeats, and run logs

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.

Triggering, execution, notification, and run history are different stages; first get the Agent running manually, then connect it step by step.

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

Channels are responsible for connecting the Agent to Feishu, Telegram, QQ, WeChat, Discord, or Slack.

Correct configuration order

1

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.

2

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.

3

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.

4

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.

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.

What is the difference between heartbeat and scheduled tasks?

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.