Skip to main content
Bugzy integrates with the tools your team already uses. Each integration gives Bugzy access to a part of your development workflow — where your code lives, how your team communicates, where bugs are tracked, and how deployments happen.

Give Bugzy access to your tools

Where Bugzy works

GitHub — repository access, webhook events, test artifact commits, PR comments.

How Bugzy communicates

Slack and Microsoft Teams — test results, team interaction, disputed findings.

Where Bugzy reports bugs

Jira, Azure DevOps, Asana, Linear — automatic bug filing for triaged failures.

Where Bugzy learns

Notion and Confluence — product documentation for better test generation.

Where Bugzy manages test cases

Azure Test Plans and Zephyr Scale — manage test cases and execution records in your existing test management system.

How Bugzy fits your pipeline

GitHub Actions, deployment hooks, scheduled runs — trigger Bugzy from CI/CD.

How Bugzy joins meetings

Zoom, Google Meet, Microsoft Teams — listen for QA-relevant discussions.

Available integrations

Email notifications are always available — no configuration needed. Email is not listed as a configurable integration because it’s pre-configured for every project.

How connections work

1

Open project connections

Navigate to Dashboard > Projects > [Your Project] > Connections.
2

Click Connect

Select the integration you want to enable. For OAuth integrations, this opens the provider’s authorization flow.
3

Authorize access

Grant the requested permissions. Credential-based integrations such as Azure DevOps ask for their provider URL and token in the secure connection form.
4

Done

The connection is active. OAuth tokens are managed and refreshed automatically by Nango — no manual token handling required.
Connection credentials are encrypted at rest and never exposed after setup. Nango manages OAuth refresh for providers that use OAuth.

Architecture

The unified agent loads only the selected provider skills and command surfaces for each run. Connection credentials are projected into the isolated runtime.
Each project maintains its own set of connections.