Automations

An automation is the same task anyone could type, minus waiting for someone to type it. It names a person it runs as — the run inherits exactly that person’s connectors and budgets, nothing more.

• Triggers — a schedule (weekdays / weekly / monthly at a local time) or an event (for example, a security alert at a chosen severity, or repeated manual work detected).
• Body — a process (with parameter defaults) or free-standing instructions.
• Runs are sessions — each firing creates an ordinary session; the Recent runs strip on the Automations page and the Automations fired recently digest on the home page link straight to them.

Delivering results somewhere (Slack, email, a tracker) is part of the instructions — “…and post the summary to #treasury” — executed through the run-as person’s connectors, and therefore visible in the audit trail.