Integrations overview
How BugCapture connects to your tracker, what's free, and what's still dark.
BugCapture files a report straight into the tool your team already uses — no re-typing, no context lost copying a screenshot into a ticket by hand.
The six
| Tracker | Files as | Setup |
|---|---|---|
| Jira | An issue, in your project's own fields | Personal access token |
| GitHub | An issue, in a repository | Personal access token |
| Linear | An issue, on a team | Personal API key |
| ClickUp | A task, in a space and list | Personal API token |
| Notion | A page, in a database | Internal integration secret |
| Slack | A message to a channel | Incoming webhook URL |
Every one of these is free on every plan. There's no tier that gates filing to your tracker — the free plan connects the same six integrations the Team and Business plans do; the plans differ on report volume, seats and recording length, not on which tools you're allowed to file into.
How they connect
All six follow the same shape, covered in Connect your tracker: paste a credential in Settings → Integrations, test the connection, pick a default destination. Credentials are per person — each teammate connects their own account, so issues are attributed correctly and one person disconnecting doesn't affect anyone else.
What's attached
Whichever tracker a report is filed to, the created issue carries the annotated screenshot or recording, the console and network trace, environment info, and a link back to the full report in BugCapture — so the tracker issue is never the first place the technical detail shows up.
Something else?
Book a demo and we'll scope it with you.