Automations and events

Automations run approved work on a schedule or trigger. Events provide inputs and an operating history.

Create an automation

Choose a verified workflow, define its schedule or trigger, select the execution identity, and set the destination. Keep source and tenant scope as narrow as possible.

Inspect runs

Use Automations, Events, and Logs to review status, timing, input, plan, output, and failure detail. Retry only after understanding whether the operation is safe to repeat.

Safe operation

• Use idempotent destinations when possible.
• Bound query size and execution time.
• Alert an owner after repeated failures.
• Pause work when credentials or schemas change.
• Re-verify outputs after semantic changes.

Automations do not remove governance. They repeat the same governed plan under an explicit identity.