Slack
Get run summaries in Slack, and ask Autonomy questions or start runs without leaving the channel.
Slack is two things in Autonomy: a place evidence gets delivered, and a place you can talk to the platform. Connect it once under Settings → Notifications → Connect Slack and both work.
Notifications
Notify Slack when a run needs attention outside GitHub. Keep the messages short and route them to channels where the owning team can act.
A message should carry the test case, the target environment, pass or fail, an evidence link, and the first actionable failure detail — not a duplicate of the evidence workspace.
Recommended routing:
- Pull request smoke failures go to the repository or product channel.
- Release candidate failures go to the release channel.
- Mobile artifact failures go to the mobile or QA channel.
- Execution health issues go to the platform or infrastructure channel.
Start with failures only. Add passing summaries only for channels that exist specifically for release verification or an audit trail. Event selection and digest scheduling live in Alerts and Reports.
The Slack agent
Autonomy also answers in Slack. Mention @Autonomy in a channel, send it a direct message, open its App Home tab, or use it from the Slack assistant side pane.
It is conversational, not a slash-command grammar — ask in plain language:
@Autonomy what's running right now?
@Autonomy show me the most recent failing runs and what broke
@Autonomy what failed in run run_123?
@Autonomy list the test plans I can run from Slack
@Autonomy start a run for the checkout plan on staging
@Autonomy cancel run run_789What it can do:
| Capability | Example |
|---|---|
| Workspace summary | "Show workspace summary", "What's running right now?" |
| List and filter runs | "Show me recent failing runs" |
| Inspect a run | "What failed in run run_123?" |
| Search test plans | "List test plans for checkout" |
| Start a run | "Run the checkout tests on staging" |
| Cancel a run | "Cancel run run_789" |
The assistant pane offers four starting prompts: Recent failures, Active agents, List plans, and Start a run.
Every request is scoped to the workspace the Slack team is connected to. The agent cannot see or act on another organization's runs.
Upgrading an existing connection
If Slack was connected before the agent shipped, the installation only holds notification scopes. Reinstall from Settings → Notifications to grant the conversational scopes — reading mentions and direct messages, posting, and resolving user identity. Until you reinstall, notifications keep working and mentions do nothing.
Troubleshooting
Notifications arrive but mentions are ignored
The installation predates the agent. Reinstall the Slack app from the dashboard to add the required scopes.
The agent cannot find a test plan by name
Ask it to list plans first. It resolves names against what exists in your workspace and will not guess at a name it cannot match.
The agent says it cannot start a run
Starting a run needs both a resolvable test case or plan and a target. Name the environment explicitly — "on staging" — if the workspace has no default.