Alerts and Reports
Route run events to email, Slack, and webhooks, and schedule daily or weekly digests.
Autonomy notifies on run events and can summarize activity on a schedule. Both are configured under Settings → Notifications, which has three surfaces: Personal, Workspace (admins), and Webhooks.
Events
The following events can trigger a notification:
| Event | Fires when |
|---|---|
runStarted | A run begins. |
runCompleted | A run reaches a terminal state. |
runFailed | A run fails. Cannot be silenced entirely. |
reportReady | A compiled report is available. |
thresholdBreach | A configured threshold is crossed. |
memberJoined | Someone joins the workspace. |
memberRemoved | Someone leaves the workspace. |
runFailed always reaches you somewhere: disable both email and Slack for it and one channel is switched back on. Everything else is yours to tune.
Personal preferences
The Personal tab controls what reaches you, independent of the workspace defaults:
- Per-event channel choices.
- Quiet-hours presets.
- Digest mode —
realtime,daily, orweekly, with the delivery hour, minute, and day of week.
Choosing daily or weekly replaces per-event mail with a scheduled digest. Start on realtime for failures while you are stabilizing a suite, then move to a digest once the signal is trustworthy.
Every email carries an unsubscribe link that lands on these settings.
Digests
- Daily — yesterday's pass rate, run count, failures, and a pass-rate chart.
- Weekly — the seven-day range, run totals, pass-rate trend, execution duration, and the test cases failing most often.
Use the weekly digest as the artifact you bring to a release or quality review. Use the daily one to notice a suite degrading before someone reports it.
Workspace defaults
Admins set organization-wide triggers on the Workspace tab and connect the outbound channels. Members inherit these unless they override them personally.
Webhooks
The Webhooks surface configures HTTP delivery for teams that want events in their own systems.
- An endpoint URL and a subscribed event set.
- An HMAC signing secret, rotatable in place.
- Delivery history, and a test-event button.
- Automatic retries on failure.
Deliveries are signed with Standard Webhooks headers — webhook-id, webhook-timestamp, and webhook-signature. Verify the signature and reject anything that does not match; the timestamp is there so you can reject replays.
Slack
Slack has its own page — both the passive notification routing and the conversational agent. See Slack.
Choosing what to route
Start with failures only, to the team that owns the journey. Add passing summaries only where a channel exists specifically for release verification or an audit trail. A channel that receives every run outcome is a channel nobody reads.