Automated Tasks
When work needs to repeat on a schedule or run after a notification from an external system, assign it to an automated task. Define the task, responsible Digital Workers, and execution plan; the system runs it when the conditions are met. Results remain in the execution records, where you can continue the conversation or push them to IM.
Work triggered by business events can also be assigned to automated tasks, which run when the event occurs.
Recommended Workflow
- Creating an Automated Task
Describe a recurring task in a chat or enter its details on the Tasks page.
- Configuring the Execution Plan
Configure manual, scheduled, or external-notification triggers.
- Records And Outputs
Review each execution status and result file, then continue the conversation from the result.
- Pushing Results to IM
Automatically send task results to a connected IM Channel.
About This Capability
The core components of an automated task:
| Component | Role |
|---|---|
| Execution Plan | Decides when to run — manual execution, scheduled execution (daily ／ weekly ／ monthly ／ custom Cron), or external notification |
| Task Description | Decides what to run — tell the AI what to do in a natural-language sentence; use @ to add context and / to invoke Skills |
| Related Objects / Semantics / Skills | Explicitly lock in the "must-use objects and must-use Skills" beyond the natural language, keeping the AI from drifting |
Select one Digital Worker to run an automated task independently, or select up to five to form a team. The lead worker breaks down the task and assigns work to team members.
After the task runs, a record with status, outputs, and logs is kept in "Execution History" — Success / Failed / Pending / Running / Terminated. On failure you can pinpoint which step went off track, and retry with one click.