Productivity · Integration
BugHerd
Add BugHerd to your product for your customers, and give your AI agents governed access to it.
BugHerd collects website feedback through a sidebar on the client's own site, and its API is versioned in the path as bugherd.com/api_v2/ with .json endpoints such as projects.json and tasks.json, all returning 401 without credentials. Authentication is HTTP Basic with the API key as the username and any placeholder as the password, which trips up clients that expect a bearer token. The object worth understanding is the task: it carries a status_id that maps to a board column rather than a fixed enum, so column names differ per project and a status filter has to resolve columns first through the columns endpoint. Tasks created from the sidebar record the requester as a guest, someone who is not a seat-holding member of the project, so a naive assumption that every requester_id resolves to a user account will produce gaps. Each task also carries the browser, operating system, screen size and a screenshot URL captured at the moment the feedback was left, which is the context that makes BugHerd worth syncing rather than just the text. fastn holds each customer's BugHerd key, handles the Basic auth encoding, and keeps the connection working as the API moves.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own BugHerd account and choose which projects sync into your tracker
Mirror BugHerd tasks into your issue tracker with the browser and screenshot context attached
Resolve column names per project so your UI shows the customer's real board stages
Surface guest requesters as contacts so client feedback can be replied to from your product
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent triage new feedback into a column and add tags, with changes held for review
Have an agent summarise unresolved feedback per project for a weekly client update, audited per tenant
Let an agent group duplicate reports by URL and browser and suggest which to merge
Example prompt
What feedback came in on the checkout page this week, and which browsers were people using?
Set up BugHerd in 4 steps
- 01Enable the BugHerd connector from your fastn dashboard.
- 02Have each customer authorise their own BugHerd account, so calls run under their credentials rather than a shared key.
- 03Decide which work items, assignees and due dates 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 BugHerd integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a BugHerd integration without building it. Your customers connect their own BugHerd account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a BugHerd update is not your on-call problem.
- One integration serves your product and your agents. The same governed BugHerd connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
Jira
Asana
ClickUpOften used alongside
Tools the same teams tend to run next to BugHerd, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceBugHerd integration FAQ
How do I add a BugHerd integration to my product?
Enable the BugHerd connector in your fastn dashboard, then let each customer authenticate their own BugHerd account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no BugHerd client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own BugHerd account?
Yes. Every connection is scoped to the individual customer, so each authorises their own BugHerd account and only ever sees their own work items, assignees and due dates. 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 BugHerd 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 triage new feedback into a column and add tags, with changes held for review
Who maintains the BugHerd integration?
fastn does. When BugHerd 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 my product create and update work in BugHerd automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in BugHerd can trigger your workflows in return.
Does it adapt to each team's own BugHerd setup?
Yes. However a team has configured BugHerd, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the BugHerd integration?
A common starting point: let a customer connect their own BugHerd account and choose which projects sync into your tracker. 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 BugHerd integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding BugHerd does not change your per-connector cost. You can start free with 3 connected accounts.
Add BugHerd to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.