Skip to content
CoreWeb · Terminal

Automations


Save a prompt, choose a schedule, and inspect every run.

An automation is a saved prompt with a schedule, an optional project, a time zone, and a run history. Use one for work that should repeat and stay inspectable.

#Create one

Tell Atoi what to do and when, or open the panel's Automations tab and write it yourself. The composer's + menu opens the same tab, and so does g a. Name the outcome, the source, the format you want back, and when to stop. Avoid "the thing we discussed today" unless the automation is bound to a project that holds that context.

#Schedules

TypeRuns
DailyOn chosen weekdays at a time
IntervalEvery N hours, optionally on chosen weekdays
MonthlyOn a day of the month at a time
ManualOnly when you run it

Times use the automation's time zone. Check the next run shown before you save.

Capture pending: The Automations tab with an automation's schedule and run historycapture pendingThe Automations tab with anautomation's schedule and runhistory1440×900/
The Automations tab with an automation's schedule and run history

#Run, pause, edit

Run it now without touching the schedule. Pause it to keep history while stopping scheduled runs. Edits apply to future runs. Deleting asks you to confirm the exact automation.

#Read every run

Each run shows its trigger, schedule, start and finish times, state, result or error, and the task or thread it created. Failed runs stay in the history.

An automation that reaches an approval it cannot resolve waits for you. It never skips an approval because nobody was watching. See Asks and approvals.

Was this useful?