Schedule an automation
A schedule runs an agent on a clock, with nobody in the chat. This page sets one up. Prepare the agent first with Create an automation, because a scheduled run cannot ask you anything.
Commit before you schedule
A schedule runs one pinned variant and revision. Commit the agent first, so the schedule can pin the version you want it to run. In the Configuration header, click Commit, keep New version, and confirm.
Open the schedule dialog
Two ways in, both opening the same New schedule dialog.
From the agent. Sidebar > Agents > <agent name>, set Playground mode to Build, scroll the Configuration column to the Triggers heading, and click Add schedule on the Schedules section.
From project settings. Sidebar > Settings > Triggers, then + Schedule on the Scheduled runs section.
Fill in the dialog
1. Name
Type a Schedule name. It is what identifies this schedule in the Scheduled runs table.
2. When should it run?
Pick a cadence, then the days and times.
| Cadence | Use it for |
|---|---|
Hourly | Every hour |
Daily | Once or several times a day |
Weekly | Chosen days of the week |
Monthly | A day each month |
Custom | A cadence the other four do not cover |
Set On these days with the Mon to Sun buttons, then At these times (UTC). To run more than once a day, click Add time and add another time.
Times are UTC. A daily 09:00 schedule fires at 09:00 UTC, not in your local time zone.
A green line under the fields restates the schedule it parsed and the next time it will fire, for example Mon at 09:00 (UTC) · next 2026-08-03 09:00 UTC. Read it before you move on.
If the schedule should only run between two dates, expand Active window and set the start and end.
3. Which version runs?
Choose Pinned, which runs one exact variant and revision, then select the variant. Every run uses that revision, so committing further changes to the agent does not change what this schedule runs.
4. What should the agent do?
Write the message the agent receives on each run, for example Summarize yesterday's support tickets and post the digest to #ops. It arrives as the user message at the start of the run, so it should name the task and where the result goes.
Test it, then switch it on
Click Run in playground in the footer to run the agent with the message you wrote. Once the run does what you want, set the Active toggle and click Create.
To create a schedule without starting it, leave Active off.
Related
- Automations explains what an unattended run needs to be given up front.
- Trigger an automation from an app starts a run from an event instead of a clock.
- Control what an agent can do covers the permissions that decide whether a run finishes on its own.