Skip to content
AtoiDocumentation
Use Atoi

Automations

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

A saved prompt on a schedule produces runs that create a Thread or Task, or wait for an approval01Saved promptoutcome, source, format02Schedulein its own time zone03RunThread or Taskthe work it madeWaiting on youan approval it holdsdaily, interval, monthly, manualRun historytriggertimesstateresult or errora failed run stays in the history
Every run is a row you can read, including the ones that failed.

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 belongs to a project that holds that context.

#Pick a schedule

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: An automation's schedule and controls in the panelcapture pendingAn automation's schedule andcontrols in the panel1440×900/
An automation's schedule and controls in the panel

#Run, pause, or edit it

Run it now without touching the schedule. Pause it to keep the 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.

Read Asks and approvals next.

Was this useful?