Automations & notices
Scheduled tasks & automations
Configure triggers and actions, then verify the environment that actually runs the task.
What can you automate?#
Recurring project summaries, source-change reviews or status notifications. Prompt actions invoke a model; webhook actions send a request to a configured HTTP endpoint. Model actions may incur provider charges.
Create a scheduled task#
- Open Automations or Scheduled tasks in the feature rail and add a task with a clear objective.
- Set the time rule and time zone. Where an expression is required, use the five-field cron format supported by the interface.
- Choose an action and review applicable model, project and permission settings.
- Test once with demo material and inspect its run record and resulting conversation.
- Enable the intended rule. Disable or delete it when no longer needed.
Example task description#
Each week, summarize newly recorded material questions in the selected project.
Return unresolved items, sources and next actions.
Summarize only. Preserve originals and do not send the report to clients.
Leave the result for the project lead to review.
Runtime requirements#
A desktop task needs its computer and MATLOOK Agent running. Online actions need their network and service. Sleep or shutdown can cause missed runs; do not assume automatic catch-up. Shutting down a desktop does not migrate its tasks to ECS.
If it did not run#
Check enabled status, schedule and time zone, event conditions, target computer, model and logs. Status/label events differ from time triggers; changing matcher text does not enable a schedule.