Integrations Overview
Agnox connects to the tools your team already uses — from CI/CD pipelines and issue trackers to notification channels and error-monitoring platforms.
Every secret you store in Agnox (API tokens, webhook URLs, signing keys) is encrypted at rest using AES-256-GCM before being written to the database. They are never logged or exposed in API responses.
Why Use Official Agnox SDKs?
Agnox ships official framework adapters — lightweight SDKs and plugins for each major testing ecosystem. These are the recommended way to connect your test suite to Agnox.
You never modify individual test files. Installation is a one-time, configuration-level change.
The Difference in AI Accuracy
How you integrate directly determines the quality of AI Root Cause Analysis (RCA) you receive.
| With an Official Agnox Adapter (Recommended) | Without an Adapter (Fallback Mode) | |
|---|---|---|
| Setup required | Add adapter to config file only. Zero test-code changes. | No setup — raw CI stdout is parsed automatically. |
| Runtime context captured | Automatically at the exact moment of failure: current URL, page title, ARIA DOM snapshot, console errors, and failed network requests (4xx/5xx). | None — only raw stdout/stderr from the CI log is available. |
| AI RCA quality | Hyper-accurate. The AI receives a structured, typed payload: the exact URL that failed, the specific network call that returned 404, and the console error that preceded the crash. It can diagnose routing bugs, API regressions, and visual state errors with surgical precision. | Best-effort. The AI parses unstructured log text. It cannot distinguish a routing bug from a flaky assertion, and has no visibility into network state or the DOM at the moment of failure. |
| Token efficiency | The structured context block is ~200 tokens. The AI processes signal, not noise. | The AI must scan up to 30,000 characters of log text looking for diagnostic clues. |
| Network error detection | Every 4xx/5xx response is captured with URL, method, and status code. | Only if the test framework happened to print it to stdout. |
| DOM state at failure | ARIA accessibility tree snapshot (capped at 8 KB). | Not available. |
If you are starting a new integration, always install the Adapter for your framework first. The improvement in RCA accuracy is immediate and requires no changes to your test code.
Available Official Adapters
| Framework | Package | Language | Status |
|---|---|---|---|
| Playwright | @agnox/playwright-reporter | TypeScript / JS | Available |
| Cypress | @agnox/cypress-plugin | TypeScript / JS | Coming in Phase 8.2 |
| Pytest + Selenium | agnox-pytest | Python | Coming in Phase 8.3 |
| WebdriverIO | @agnox/wdio-service | TypeScript / JS | Roadmap |
Available Integrations
CI/CD & Source Control
GitHub Actions
Trigger hosted runs or stream Playwright results from your own runners. Supports Smart PR Routing.
Configure →
Bitbucket Pipelines
Trigger Agnox runs from Bitbucket Pipelines and post status comments back to pull requests.
Configure →Issue Trackers
Jira
Create Jira issues directly from the Investigation Hub or the AI Auto Bug modal with one click.
Configure →
Linear
Create Linear issues from failed executions. Issue URLs are stored on the execution record for traceability.
Configure →
Monday.com
Create Monday items and post execution updates on your boards automatically after every run.
Configure →Notifications
Slack
Rich Slack messages with AI analysis snippets and direct links to the Investigation Hub.
Configure →
Microsoft Teams
Post colour-coded MessageCard notifications to any Teams channel using an Incoming Webhook URL. Supports per-status toggles and AI analysis snippets.
Configure →Extensibility
🔗 Generic Webhooks
Send execution payloads to any HTTP endpoint, verified with HMAC SHA-256 signatures. Connect to any internal tool your team uses.
Configure →Where to Configure
All integrations are managed from Settings → Connectors in the Agnox dashboard. Each card shows a Connected badge once valid credentials have been stored.
Place SVG logos at static/img/integrations/<name>.svg and they will appear in the cards above. Recommended size: 80 × 80 px (or a square SVG that scales cleanly).