Channels and scheduled daily reports

The operations team wants to automatically aggregate designated materials every weekday morning, generate a daily report, and send it to the team channel. Before automating, first run one manually to quickly uncover missing data, path errors, and notification destination issues.

What to prepare first

• A daily report Agent that has already been validated in [Work];
• A clear data source and a working directory containing only the required materials;
• Fixed-format content can be turned into a skill;
• A channel that has been connected and whose message scope has been restricted;
• A weekday scheduled task.

First bind the daily report to a tested channel, then select it as the notification target for the scheduled task.

After the first automatic run, check the Agent status and run records to see whether the task was actually completed.

1) The task has been enabled and shows the next run time; 2) The prompt clearly specifies the four-part structure, missing-data handling, and channel-sending conditions.

Configuration steps

1

1. Manually generate a daily report

Require the Agent to output four sections: "Progress, Metrics, Risks, To-do." Check whether missing data is stated clearly instead of inventing content.

2

2. Configure the notification channel

First tell the Agent which platform and group to connect to, then go to [Settings] → [Channels] to verify credentials, allowed session ID, workspace, and permission mode.

3

3. Create a scheduled task

Have the Agent create a weekday schedule, or open [Settings] → [Scheduled Tasks] → [New]. Select the daily report Agent, working directory, execution time, and notification channel.

4

4. Test immediately

After saving, click [Run] and check the generated session, run history, and channel messages. Don't wait until the next day to discover a path or destination error.

5

5. Observe and adjust

For the first few runs, check the time required, usage, and failure reasons. When the data source or team format changes, update the skill or task prompt; do not maintain conflicting rules in multiple places.

Example task prompt

Read the data added yesterday in the current working directory and generate a Chinese operations daily report. It must always include Progress, Key Metrics, Exceptions, and Today's To-dos. If no data is found, write "No data available" and list the missing files; do not make up any numbers. Send the result to the configured team channel and keep a Markdown file in the working directory.

Failure handling

Symptom	Check location
Not running	Scheduled task status, next run time, system sleep
Run failed	[Run History] → [View Session]
File was not generated	Working directory, permission requests, and the Agent file tool
Message was not delivered	Channel status, receiving target, and platform logs
Duplicate content	Whether heartbeat and multiple identical schedules are enabled at the same time

Recommended combination and completion criteria

Item	Recommended approach
Agent	First manually run the same daily report successfully, then hand it over to the scheduled task
Schedule	Prefer [Every day] or [Weekdays], and confirm the next run time
Channels	Send to a test session first, then switch to the production group
Completion criteria	Run history is successful; the report file can be opened; the channel receives only one message; when data is missing, no results are fabricated

Scheduled tasks run unattended. Before going live, keep the file scope minimal and permissions appropriate to avoid handing high-risk writes or external modifications over to full-access mode.

The demo environment in the screenshot is not bound to an external channel, so it only shows tasks that have already been saved and enabled. For production use, you still need to click [Run], confirm that [Run History] is successful, and see one real message in the test channel before putting it into daily operation.