Scheduling a prompt to run on its own
A scheduled job runs a prompt on a cron schedule. It is the same prompt you would type in Slack, fired automatically, which makes it the right tool for digests, reports and monitoring loops.
Creating one
Go to Automations in the sidebar under Agents, open the Scheduled Tasks tab, and choose + Create Task. Once enabled it fires at the next matching time.
The fields
Platform: where the output goes. A Slack channel, a Discord channel, or API-only when the prompt sends its own notifications.
Schedule: a standard five-field cron expression. The form shows you a plain-English translation as you type, and warns you if the expression would fire more than once a minute.
Timezone: an IANA timezone. Get this right before anything else. 0 9 * * 1-5 in UTC is 09:00 UTC, which is the middle of the night on the US east coast. Note also that a job scheduled at 02:00 can be skipped or repeated on the days daylight saving shifts.
Post in thread: for Slack and Discord, whether the output is a top-level message or a threaded reply. Use a thread for a job that runs often. Turn it off for something the team needs to see.
Enabled: pause a job without deleting it.
Prompt: the instruction, exactly as you would type it in chat. There are no template variables, so a prompt that needs to know about "yesterday" has to tell the agent to work that out itself.
Cron examples
0 9 * * 1every Monday at 09:000 9 * * 1-5weekdays at 09:00*/15 * * * *every 15 minutes0 0 1 * *the first of the month at midnight
Checking a job ran
Click the job to see Recent runs, each linking to the full transcript. A failed run is flagged, with the error visible in the transcript.
When nothing happens
Check Enabled is on. Check the timezone is what you assumed. Check the right Slack workspace or Discord server is selected. If the output looks like the agent misunderstood the time period, remember it has to compute that itself. If it is an API job, the prompt has to handle its own notification.