Automations: scheduled, triggered, and on demand
Run work once on request, on a schedule, or when something changes, with approvals and a receipt for every run.
Automations are recurring, governed workflows that AMOS runs across the apps you have connected. You describe the outcome in plain language; you do not wire up a pipeline by hand.
Three ways work gets done
- On demand: ask your AI to do something once, right now ("send that follow-up").
- Scheduled: a standing automation runs on a schedule, such as an interval or a daily or weekly time ("every Monday, chase overdue invoices").
- Triggered: a standing automation runs when something happens, such as a change to a record in AMOS or an incoming signed webhook from another app ("when a lead comes in, do this").
A good pattern is to ask AMOS to do a job once, and when it works, say "do that every Monday".
Setting one up
AMOS Desktop walks you through it: it confirms what should happen, connects any missing apps, shows how fields map from one app to the other, lets you pick the trigger, and previews the steps. A new automation starts as an inactive draft and only runs after it is activated.
Approvals inside automations
- Steps that write to a connected app ask for approval on each run by default.
- An owner or admin can grant one step a standing grant so it runs unattended, but only within limits you set: a time window, a maximum number of runs, a maximum number of consecutive failures, and an expiry date. Grants can be revoked immediately.
- Every run is scoped to your company, checked against policy, and leaves a receipt.
Managing automations
The Automations view in AMOS Desktop shows each automation's status, trigger, steps, runs, failures and any approvals waiting. You can pause, resume, or revoke a grant at any time.
Plans
Standing automations run on paid plans: Starter includes 4, Pro 15, and Compliance 50.