As the core module of agents' automation capabilities, Scheduled Task can be used to add periodically-triggered backend tasks to configured agents. This can allow agents to automatically execute operations (such as data summarization, report generation, and anomaly alert) without requiring users to actively ask questions, and push results to target users through multiple channels, upgrading business analysis from passive Q&A to proactive services.
Daily data is regularly collected and organized, and pushed to targeted business and management personnel.
Periodic statistical reports, such as daily/weekly/monthly/annual reports, are automatically generated.
Data anomalies (if any) are monitored in real time, and quickly trigger anomaly alerts and message pushes.
(1) Pushed to the platform
Taking the scheduled push of sales risk alert in sales scenarios as an example, the following figure shows the effect.
(2) Pushed to a personal chat window on an IM platform (using WeCom as an example)
(3) Pushed to a group chat window on an IM platform (using WeCom as an example)
Dora Version
Functional Change
V0.6
/
V1.5
Added Content to Push.
Added the pushing methods Chat Group and Webhook.
Scheduled tasks can be configured through the following two entries:
Enter Admin Console, go to the agent configuration page, and click the + button in the Scheduled Task module to enter the creation process.
When using an agent on the frontend, click Scheduled Task in the left navigation bar to enter the scheduled task management page for the current agent.
There are two methods to create a scheduled task: creation from blanks or creation by a recommended template.
Creation from blanks is suitable for scenarios with clear custom requirements, which requires all configuration items to be set manually. In the Add Scheduled Task dialog box, click Start from Blank to enter the task configuration page.
Currently, the following two scenario templates are provided. The templates already contain structured task prompts and default execution frequencies. Users only need to modify the appropriate template content and supplement the target users and pushing channels to complete the creation.
Weekly Operation Report
Data Alert
The following table lists task configuration items.
Configuration Item
Mandatory or Not
Description
Task Name
Mandatory
Identifier name of the task. You are advised to use a name that clearly expresses the purpose of the task, for example, Daily Store Sales Analysis Report.
Task Prompt
Complete instructions received by the agent during task execution, which determine the agent's behavior and output content. For details, see section "Prompt Writing Guide for Scheduled Tasks" below.
Content to Push
Text and Attachments
Text Only
Scheduled Execution Frequency
Time cycle and specific time point for the automatic task execution.
Pushing Method
Personal: Select the target receiver and pushing channel.
Chat Group: Select a chat group on the connected IM platform to which messages are pushed.
Webhook: Push messages via a Webhook URL.
A well-structured prompt should include three parts: task goal, core rules, and output requirements.
Structured Template for Scheduled Task Prompts
Task goal: [Describe the core task the agent needs to complete in one sentence.]
Core rules:
1. [Rule 1: Specify the core content the agent needs to analyze or process.]
2. [Rule 2: Specify the dimensions the agent needs to deeply disassemble or compare.]
3. [Rule 3: Specify the direction the agent needs to identify or judge.]
Output requirements:
1. Title: [Specify the title format of the output content.]
2. Content: [Specify the scope the output content needs to cover.]
3. Tone: [Specify the language style and expression method of the output content.]
Prompt Example: Weekly Operation Report Task
Task goal: Generate a weekly report based on this week's business data to clearly display business progress, core issues, and optimization suggestions.
1. Core metric review: Display the completion status of core metrics, for example, [Sales Amount], for this week.
2. Key business analysis: Disassemble the top three contributing channels/regions/categories, and analyze the core reasons for growth/decline.
3. Risk and opportunity identification: Identify potential business risks in this week.
1. Title: [XX Business Line] Weekly Operation Report
2. Content: All content specified in the core rules
3. Tone: Concise and professional, with conclusions in front, data to support opinions, and no redundant descriptions
The following two types of content can be pushed:
Text and Attachments: Push the text results generated by the agent and related attachments.
Text Only: Push only the text results, without the attachments generated by the task.
(1) Procedure
Select the target receiver and select one or more pushing channels for this user. Supported channels include the platform, DingTalk, Feishu, Lark, WeCom, Teams, Telegram, and LINE. The actual available channels depend on the IM connection configurations completed in the system.
(2) Effect Demonstration
Taking how to push messages to a WeCom individual as an example, the following figure shows the effect.
Task results can be pushed to Feishu, DingTalk, or WeCom chat groups. The steps are as follows:
(1) Toggle on the Chat Group switch in Pushing Channel and select a connected IM platform.
(2) Select the target chat group on the IM platform. If the chat group ID cannot be found in the list, you can copy the command on the page and send it by mentioning (@) the bot in the target WeCom group to obtain the ID, or you can manually enter the group chat ID and remarks to add the group.
(3) Effect Demonstration
Taking how to push messages to a WeCom chat group as an example, the following figure shows the effect.
Currently, webhook pushing supports only Feishu, DingTalk, and WeCom. You can add multiple Webhook URLs to push scheduled task results to different targets simultaneously.
External System Type
Webhook Source
Signature Verification
Dora Configuration Requirement
Feishu
Feishu group's custom bot
Supported
If signature verification is enabled in Feishu, it must also be enabled in Dora with the same signature key entered.
DingTalk
DingTalk group's custom bot
Only additional signatures supported now
If an additional signature is enabled in DingTalk, it must also be enabled in Dora with the key starting with SEC entered.
WeCom
WeCom group message pushing
No configuration required
Just enter the Webhook URL.
Toggle on the Webhook switch in Pushing Channel, enter the Webhook URL of the external system obtained through any of the following methods, and complete the connection test:
WeCom - Adding Message Pushes to Chat Groups
Feishu - Adding Custom Bots to Chat Groups
DingTalk - Adding Custom Bots to Chat Groups
Taking how to push messages to a DingTalk chat group via DingTalk webhook as an example, the following figure shows the result.
(1) Scheduled tasks rely on the Chat Subscription skill. This skill must also be added to the agent where the scheduled tasks are configured.
(2) Scheduled tasks of all agents can be managed under Admin Console > Agent Supervision > Scheduled Task.
(3) At least one channel must be selected. Otherwise, the task execution results cannot be pushed to users.
(4) Before messages are pushed to WeCom, the WeCom connection must be configured in the Connected IM Tool module first. Otherwise, the push will not take effect.
(5) Scheduled tasks added on the agent configuration page in Admin Console will be marked as Configured Within Agent. Scheduled tasks added on the frontend agent use page will be marked as Added by Me.
(6) Webhook URLs and signature keys are sensitive credentials. Do not publish them to public documents, code repositories, or logs.
(7) After the group bot is modified or reset, the original webhook URL or key may become invalid, requiring the configuration in Dora to be updated accordingly.