Overview
Connect Autonomy to deployment, CI, design, and notification workflows.
Autonomy works best when evidence appears where the team already reviews changes. Use integrations to connect preview deployments, pull requests, CI jobs, design references, and release notifications to the same run evidence.
What connects where
| Integration | Purpose |
|---|---|
| GitHub App | Trigger runs from a pull request comment in plain language; get one auto-updating comment and check run back. |
| GitHub Actions | Trigger runs from a workflow after the preview URL is known. |
| Vercel | Automatically run QA against every Vercel preview deployment and report the result as a deployment check. |
| Netlify | Automatically run QA against every Netlify deploy preview and report the result via your linked GitHub repository. |
| Expo EAS | Automatically run mobile QA against every EAS build and report the result via your linked GitHub repository. |
| Figma | Use design frames as visual baselines for test steps. |
| Slack | Receive run summaries, and ask Autonomy questions or start runs from a channel. |
| Alerts and Reports | Route events to email and webhooks; schedule daily or weekly digests. |
Recommended order
Start with the surface that creates preview URLs. For many teams that is Vercel or GitHub Actions. Add the GitHub App next so reviewers can ask for a run without leaving the pull request. After preview runs are reliable, add Slack notifications for failures and broaden coverage to mobile artifacts, API checks, visual baselines, and protected journeys.
Integration rollout
- Identify the system that creates preview or staging targets.
- Choose one smoke test case that proves a real user journey.
- Store Autonomy secrets in the provider secret store.
- Run manually once, then enable automatic runs.
- Route failed evidence to the team that owns the journey.
What integrations publish
Integrations should publish concise status and evidence links, not duplicate every artifact. Reviewers should be able to open the pull request or Slack message, see whether the run passed, and follow one link to the full evidence workspace.