A name, an instruction, a time.
That is the whole form. Write the instruction the way you would say it, choose when it runs, and press Test run to see what it would do. Prefer to talk? Ask SAAM in chat and it fills the same form for you.


A routine is an instruction with a trigger. Every Sunday at 6, look at my week. Every weekday at 8, check this page and tell me. Say it once and SAAM keeps it.
LiveThat is the whole form. Write the instruction the way you would say it, choose when it runs, and press Test run to see what it would do. Prefer to talk? Ask SAAM in chat and it fills the same form for you.


Each one is a sentence and a time.
Check the school page for new notices and tell me.
Draft a five item grocery list for two and post it here.
Look at my week and flag anything that clashes.
Remind me to call the dentist. One-time reminders are made from chat.
Three triggers work today. One is on the way. The rest are not built, and we will not list them as coming.
Every hour, day, weekday, week or month, at an interval, or on a cron line, in your time zone.
LiveA private URL for the routine. Another service posts to it and the routine runs. The key can be rotated.
LiveA GitHub webhook can start a routine when something happens in a repository.
LiveStart a routine from a Slack message. It needs Slack switched on, which it is not yet.
ComingNot yet. A new email or calendar event cannot start a routine today, and neither can Linear, Sentry or PagerDuty alerts.
A routine run is a normal run. If it only looks things up or works on its own computer, it finishes by itself.
If it needs to send, book or change something, it stops at an approval card in the chat and waits for your yes. Runs started by a webhook always ask. You can add an always-allow rule for something you trust, and then it will not wait.
Nothing runs unseen.
Run it now, before it ever fires on its own, and read the result.
Every run is listed, with its result, so you can see what happened and when.
Switch a routine off with the Active toggle. It keeps its settings.
A run that could not finish is shown as failed, so a blocked run never looks like a quiet success.
A short recording from the live app: name a routine, say what it should do, and add a weekday schedule. The routine in the clip is not saved.
Routines are reliable at the clock. They are young at everything else.
On the web you see results in the chat, and a browser notice only while the tab is open. Chat-app alerts arrive when channels open.
A routine that sends something stays paused at its card until you answer it.
SAAM cannot start from a new email or a calendar change today. Use a schedule or a webhook.
When a plan limit is reached, a scheduled run is blocked and shows as failed each time it fires.
Open SAAM and tell your agent what should happen, and when. Press Test run to see it work.