Developer Tools · Integration
BugBug
Add BugBug to your product for your customers, and give your AI agents governed access to it.
BugBug's public API is hosted on the app itself at app.bugbug.io, with an OpenAPI schema served from /docs/schema/ and current routes under /api/v2/ while the older /api/v1/ paths still answer with a 401 for unauthenticated calls. The object model is tests made of steps, with components acting as reusable step groups that can be inserted into or unlinked from a test, so refactoring a shared login flow is an API operation rather than a copy-paste. Execution is asynchronous in two flavours: POST creates a testrun or a suiterun, and you then poll /testruns/{id}/status or /suiteruns/{id}/status until it settles, pulling /screenshots for visual evidence or /report/junit when a CI system needs a familiar format. Profiles hold the variable sets that let the same test run against staging and production, so a run is a pairing of a test and a profile rather than a test alone. There is also a visual regression surface with reference screenshots, and a /config/ips endpoint that tells you which addresses cloud runs originate from, which is what you need to allowlist a protected environment. fastn holds each customer's BugBug token, polls run status on your behalf and keeps up with schema changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own BugBug workspace and trigger their suites from your release pipeline
Show test run status and screenshots inside your deployment view instead of sending people to another tab
Pull JUnit reports from completed runs into your existing CI reporting
Let customers choose which profile a triggered run uses so staging and production stay separate
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent start a named suite run for a tenant and report the outcome once polling completes
Have an agent summarise which steps failed across the last week of runs, audited per tenant
Let an agent identify tests that depend on a component that recently changed
Example prompt
Did last night's checkout suite pass, and if not which step broke?
Set up BugBug in 4 steps
- 01Enable the BugBug connector from your fastn dashboard.
- 02Have each customer authorise their own BugBug account, so calls run under their credentials rather than a shared key.
- 03Decide which services, builds and deployments your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the BugBug integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a BugBug integration without building it. Your customers connect their own BugBug account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a BugBug update is not your on-call problem.
- One integration serves your product and your agents. The same governed BugBug connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
GitHub
Azure DevOps
Google CloudOften used alongside
Tools the same teams tend to run next to BugBug, across other categories.
Slack
Snowflake
Airtable
PostgreSQLBugBug integration FAQ
How do I add a BugBug integration to my product?
Enable the BugBug connector in your fastn dashboard, then let each customer authenticate their own BugBug account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no BugBug client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own BugBug account?
Yes. Every connection is scoped to the individual customer, so each authorises their own BugBug account and only ever sees their own services, builds and deployments. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this BugBug integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent start a named suite run for a tenant and report the outcome once polling completes
Who maintains the BugBug integration?
fastn does. When BugBug changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I react to BugBug events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in BugBug?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the BugBug integration?
A common starting point: let a customer connect their own BugBug workspace and trigger their suites from your release pipeline. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the BugBug integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding BugBug does not change your per-connector cost. You can start free with 3 connected accounts.
Add BugBug to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.