Integration guides &
setup tutorials
Connect your development and QA toolchain to file actionable bug reports with zero manual typing.
Pre-flight Verification Engine Built-In
Every integration in BugSnap features a non-mutating 'Test Connection' probe. It validates your tokens, project keys, and database permissions using read-only API calls -without spamming your issue trackers with fake test tickets or consuming chat prompt quotas.
Aksora
Issue TrackerConnect your Aksora QA Workspace to push bug tickets directly.
Configured Fields
- Instance URL:(Required)
- API Key / Token:(Required)-Generate an API key with write permissions from Aksora > Settings > API Keys.
Permissions & Scope
Aksora QA Workspace API Key with write ticket permissions.
Step-by-Step Setup Guide
- 1In your Aksora instance, navigate to Settings > Workspace > API Keys.
- 2Generate an API token with 'captures:write' and 'tickets:create' scope.
- 3Enter your Aksora Instance URL (e.g. https://qa.aksoraproject.my.id) and API key in BugSnap Settings.
- 4Click 'Test Connection' to verify workspace pairing and token validity.
Delivered Payload Preview
{
"data": {
"title": "[BugSnap] Checkout button unresponsive",
"project": "General",
"relatedFeature": "BugSnap Capture",
"category": "Bug Fix",
"status": "todo",
"priority": "P1",
"description": "Bug report captured via BugSnap with full DevTools telemetry.",
"acceptanceCriteria": "Verify bug reported in BugSnap capture is resolved.",
"evidence": "https://bugsnap.akusaraproject.my.id/v/cap_9a8f2"
}
}Common Issues & Resolutions
Check if the API key in Aksora has expired or has been revoked by a workspace administrator.
SnapTest AI
AI & AutomationForward captures directly into automated test suites and test runs.
Configured Fields
- Runner / Server URL:(Required)
- API Key / Token:(Optional)
Permissions & Scope
SnapTest AI Runner endpoint or automated test executor URL.
Step-by-Step Setup Guide
- 1Launch your SnapTest AI Runner server or cloud endpoint (e.g. https://runner.snaptest.ai or local runner).
- 2Obtain your runner authentication token (optional for local endpoints).
- 3In BugSnap Settings > SnapTest AI, configure the Runner URL and Token.
- 4Click 'Test Connection' -BugSnap queries the runner health endpoint (/health or /api/status) to verify connectivity.
Delivered Payload Preview
{
"captureId": "cap_9a8f2",
"title": "Checkout button unresponsive",
"description": "User clicks checkout button but total taxes fail to calculate.",
"type": "video",
"driveUrl": "https://bugsnap.akusaraproject.my.id/v/cap_9a8f2",
"siteUrl": "https://app.example.com/checkout",
"os": "Windows 11",
"browser": "Chrome 132.0.0",
"devLogs": [
{ "type": "console", "level": "error", "message": "calculateTaxes is undefined" }
]
}Common Issues & Resolutions
Ensure your runner server is running and accessible over HTTP/HTTPS from the BugSnap dashboard server.

Slack
Chat & AlertsSend bug captures and reports directly to Slack channels.
Configured Fields
- Incoming Webhook URL:(Required)-Create an Incoming Webhook in your Slack App configurations.
- Default Channel:(Optional)
Step-by-Step Setup Guide
- 1Go to api.slack.com/apps and click 'Create New App' > 'From scratch'.
- 2Select 'Incoming Webhooks' under Features, toggle 'Activate Incoming Webhooks' to On.
- 3Click 'Add New Webhook to Workspace', choose the channel (e.g. #bugs or #qa-alerts), and click Allow.
- 4Copy the Incoming Webhook URL (starts with https://hooks.slack.com/services/...).
- 5In BugSnap Settings > Slack, paste the Webhook URL and optional default channel. Click 'Test Connection' to receive a verification alert in Slack.
Delivered Payload Preview
{
"text": "[BugSnap] Screenshot - Checkout button unresponsive",
"blocks": [
{
"type": "section",
"text": { "type": "mrkdwn", "text": "*[BugSnap]* Screenshot - *Checkout button unresponsive*\n<https://bugsnap.akusaraproject.my.id/v/cap_123|View Capture & DevTools Diagnostics>" }
}
]
}Common Issues & Resolutions
Ensure the webhook was authorized for the correct channel and has not been archived or deleted.
Webhooks
Chat & AlertsSend capture alerts to custom Slack, Discord, Zapier, or HTTP endpoints.
Configured Fields
- Webhook URL:(Required)-We POST a JSON payload with capture URL, thumbnail, DevTools error diagnostics, and system metadata.
Permissions & Scope
Any HTTP POST endpoint (Discord Webhooks, Zapier, Make.com, n8n, or internal servers).
Step-by-Step Setup Guide
- 1Discord: Open Server Settings > Integrations > Webhooks > 'New Webhook' > Copy Webhook URL.
- 2Zapier / Make / n8n: Create a 'Catch Hook' trigger and copy the generated webhook endpoint URL.
- 3Custom Server: Create an HTTP POST route that accepts JSON payloads.
- 4In BugSnap Settings > Webhooks, enter your destination URL.
- 5Click 'Test Connection' -BugSnap validates SSRF safety and sends a ping payload. Click 'Save Configuration'.
Delivered Payload Preview
{
"event": "capture.created",
"content": "**[BugSnap]** Screenshot - Checkout button unresponsive",
"embeds": [
{
"title": "Checkout button unresponsive",
"url": "https://bugsnap.akusaraproject.my.id/v/cap_123",
"color": 15680580,
"fields": [
{ "name": "Platform", "value": "Windows / Chrome", "inline": true },
{ "name": "URL", "value": "https://app.example.com", "inline": true },
{ "name": "Errors", "value": "2", "inline": true }
]
}
],
"capture": {
"id": "cap_123",
"title": "Checkout button unresponsive",
"site_url": "https://app.example.com",
"dev_logs": [ ... ]
}
}Common Issues & Resolutions
Webhooks must resolve to publicly routable internet domains or IPs. Internal IP addresses (127.0.0.1, 192.168.x.x, 10.x.x.x) are blocked for safety.

GitHub
Issue TrackerOpen GitHub issues directly from bug captures with diagnostic data.
Configured Fields
- Personal Access Token (PAT):(Required)-Requires 'repo' scope or fine-grained token with 'Issues: Read and Write'.
- Repository (owner/repo):(Required)-e.g. your-org/frontend-app
Permissions & Scope
Personal Access Token (classic) with 'repo' scope, or Fine-grained PAT with 'Issues: Read and write' on target repositories.
Step-by-Step Setup Guide
- 1Navigate to GitHub Settings > Developer settings > Personal access tokens.
- 2Select 'Tokens (classic)' or 'Fine-grained tokens'. For classic tokens, check the 'repo' scope. For fine-grained tokens, grant 'Issues: Read and write' on your repository.
- 3Copy the generated token (starts with ghp_ or github_pat_).
- 4In BugSnap Workspace Settings > Integrations > GitHub, enter your PAT and target repository in owner/repo format (e.g. your-org/frontend-app).
- 5Click 'Test Connection' to verify repository access without creating an issue, then click 'Save Configuration'.
Delivered Payload Preview
## [BugSnap Bug Report] #142 - Checkout button unresponsive **Environment:** Windows 11 · Chrome 132.0.0 · 1920x1080 **Source URL:** https://app.example.com/checkout **Direct Capture Link:** https://bugsnap.akusaraproject.my.id/v/cap_9a8f2 ### Console Diagnostics (2 Errors) - [Uncaught TypeError] Cannot read properties of undefined (reading 'calculateTaxes') at checkout.js:142 - [Network 500] POST https://api.example.com/v1/charge - HTTP 500 Internal Server Error
Common Issues & Resolutions
Your token has expired or was revoked. Generate a new token at github.com/settings/tokens.
Verify the repository name format is strictly 'owner/repo'. If using fine-grained tokens or SSO-protected organizations, ensure SAML SSO authorization is approved for the token.

Linear
Issue TrackerCreate Linear issues from bug captures with full metadata instantly.
Configured Fields
- Linear API Key:(Required)-Generate from Linear Settings > Account > Security & API.
- Team Key or ID:(Required)
Step-by-Step Setup Guide
- 1Open Linear and go to Settings > Account > Security & API.
- 2Under 'Personal API keys', click 'Create key' and give it a descriptive label (e.g. 'BugSnap Integration').
- 3Copy the generated API key (starts with lin_api_).
- 4Find your Team Key or Team UUID in Linear (e.g. 'ENG', 'FRONTEND', or the 36-character team UUID). BugSnap automatically resolves team keys like 'ENG' to their UUID.
- 5In BugSnap Workspace Settings > Linear, paste the API key and Team Key/ID, test the connection, and save.
Delivered Payload Preview
mutation IssueCreate {
issueCreate(input: {
title: "[BugSnap] Checkout button unresponsive"
teamId: "4b92c1de-..."
description: "Captured via BugSnap with full DevTools logs and environment telemetry..."
}) { success issue { id identifier url } }
}Common Issues & Resolutions
Confirm your team key exactly matches the team identifier shown in Linear issue prefixes (e.g. 'ENG-101' -> use 'ENG').
Ensure your Linear account has permission to view and file issues inside the specified team.

Jira
Issue TrackerCreate Jira issue tickets automatically from captured bugs.
Configured Fields
- Atlassian Site URL:(Required)
- Atlassian Account Email:(Required)
- Atlassian API Token:(Required)-Generate from id.atlassian.com/manage-profile/security/api-tokens.
- Jira Project Key:(Required)
Permissions & Scope
Atlassian API Token with Jira Cloud REST API access.
Step-by-Step Setup Guide
- 1Log into Atlassian Account Security and click 'Create API token'.
- 2Label it 'BugSnap' and copy the token (starts with ATATT3...).
- 3Collect your Atlassian Site URL (e.g. https://yourcompany.atlassian.net) and your account email address.
- 4Find your Jira Project Key (e.g. 'PROJ' or 'BUG').
- 5In BugSnap Settings > Jira, fill in Host URL, Email, API Token, and Project Key. Click 'Test Connection' to verify project existence.
Delivered Payload Preview
{
"fields": {
"project": { "key": "BUG" },
"summary": "[BugSnap] Checkout button unresponsive",
"description": "Full capture link, environment details, console stack trace, and network failures...",
"issuetype": { "name": "Bug" }
}
}Common Issues & Resolutions
Check that the email address exactly matches the Atlassian ID account used to generate the API token.
Verify the Project Key in Jira. Ensure your user account has 'Create Issues' and 'Browse Projects' permissions in that project's permission scheme.

GitLab
Issue TrackerOpen GitLab issues from bug captures instantly.
Configured Fields
- GitLab Host URL:(Required)-Leave as https://gitlab.com or provide self-hosted URL.
- Personal / Project Access Token:(Required)-Requires 'api' scope.
- Project Path or ID:(Required)
Permissions & Scope
Personal, Project, or Group Access Token with 'api' or 'read_api + write_repository' scope.
Step-by-Step Setup Guide
- 1In GitLab, go to Preferences > Access Tokens (or Project Settings > Access Tokens).
- 2Create a token with the 'api' scope enabled.
- 3Specify your GitLab Host URL (leave as https://gitlab.com for cloud or provide your self-hosted instance URL).
- 4Enter your Project Path (e.g. my-group/my-project) or numeric Project ID.
- 5Paste your token in BugSnap Settings > GitLab, click 'Test Connection', and save.
Delivered Payload Preview
{
"title": "[BugSnap] Checkout button unresponsive",
"description": "Bug report captured via BugSnap.\n\n### Environment\n- OS: Windows 11 · Chrome 132.0.0\n- URL: https://app.example.com/checkout\n\n### Console Diagnostics (2 Errors)\n- [Uncaught TypeError] Cannot read properties of undefined at checkout.js:142\n- [Network 500] POST https://api.example.com/v1/charge\n\n[View BugSnap Capture](https://bugsnap.akusaraproject.my.id/v/cap_9a8f2)",
"labels": "bug"
}Common Issues & Resolutions
Check whether your project is private. If private, the access token must belong to a member with at least Reporter or Developer role.
Ensure your self-hosted GitLab instance has a valid CA-signed SSL certificate reachable from public networks.

Notion
Productivity & DocsLog bug captures as database pages in your Notion workspace.
Configured Fields
- Internal Integration Secret:(Required)-Create at notion.so/my-integrations and connect it to your database.
- Database ID:(Required)
Permissions & Scope
Internal Integration Secret connected to your target Notion database.
Step-by-Step Setup Guide
- 1Visit notion.so/profile/integrations and click '+ New integration'.
- 2Name it 'BugSnap', select your workspace, and save to receive an 'Internal Integration Secret' (starts with secret_).
- 3Open your target Bug/Task Database in Notion. Click the '...' menu in the top-right corner > 'Connections' > search and connect 'BugSnap'.
- 4Copy the 32-character Database ID from the database page URL (the characters between notion.so/ and the ?v= query parameter).
- 5Paste the Secret and Database ID into BugSnap Settings > Notion, run 'Test Connection', and save.
Delivered Payload Preview
{
"parent": { "database_id": "32_character_hex_database_id" },
"properties": {
"Name": {
"title": [{ "text": { "content": "[BugSnap] Checkout button unresponsive" } }]
}
},
"children": [
{
"object": "block",
"type": "paragraph",
"paragraph": {
"rich_text": [{ "type": "text", "text": { "content": "Bug report captured via BugSnap with full DevTools logs and environment telemetry..." } }]
}
}
]
}Common Issues & Resolutions
You must connect the integration to the database page: click '...' > 'Connections' > select your BugSnap integration.
BugSnap automatically splits descriptions and stack traces exceeding Notion's 2,000-character block limit into sequential paragraph blocks.

ClickUp
Issue TrackerCreate ClickUp tasks from captures.
Configured Fields
- Personal API Token:(Required)-Generate from ClickUp Settings > Apps > API Token.
- List ID:(Required)-Found in your ClickUp List URL.
Permissions & Scope
ClickUp Personal API Token with workspace task creation rights.
Step-by-Step Setup Guide
- 1In ClickUp, open your Workspace Settings > Apps > API Token.
- 2Click 'Generate' and copy your Personal API Token (starts with pk_).
- 3Open the target ClickUp List in your browser. The List ID is the numeric ID at the end of the URL (e.g. app.clickup.com/.../v/l/li/123456789 -> List ID is 123456789).
- 4Enter your Token and List ID in BugSnap Settings > ClickUp.
- 5Click 'Test Connection' to verify list access and task creation permissions.
Delivered Payload Preview
{
"name": "[BugSnap] Checkout button unresponsive",
"description": "Bug report captured via BugSnap.\n\n### Environment\n- OS: Windows 11 · Chrome 132.0.0\n- URL: https://app.example.com/checkout\n\n### Console Errors\n- [error] Uncaught TypeError in checkout.js:142\n\n[View BugSnap Capture](https://bugsnap.akusaraproject.my.id/v/cap_9a8f2)",
"priority": 2
}Common Issues & Resolutions
Verify that the token was copied completely without trailing whitespaces.
Ensure you are using the List ID (not the Folder ID or Space ID).

Asana
Issue TrackerCreate Asana tasks and attach captures automatically.
Configured Fields
- Personal Access Token:(Required)-Generate from Asana Developer Console.
- Project GID:(Required)-Found in your Asana project URL.
Step-by-Step Setup Guide
- 1Go to Asana Developer Console (app.asana.com/0/my-apps).
- 2Under 'Personal access tokens', click '+ New access token'.
- 3Label it 'BugSnap' and copy the token (starts with 1/...).
- 4Open your target project in Asana. The Project GID is the numeric string in the URL (e.g. app.asana.com/0/1234567890/list).
- 5In BugSnap Settings > Asana, enter the token and Project GID, test the connection, and save.
Delivered Payload Preview
{
"data": {
"name": "[BugSnap] Checkout button unresponsive",
"notes": "Bug report captured via BugSnap.\n\nEnvironment: Windows 11 · Chrome 132.0.0\nSource URL: https://app.example.com/checkout\nDirect Capture Link: https://bugsnap.akusaraproject.my.id/v/cap_9a8f2\n\nDevTools: 2 console errors detected.",
"projects": ["1234567890"]
}
}Common Issues & Resolutions
Verify the user account that created the PAT is a member of the target Asana project and workspace.

Azure DevOps
Issue TrackerFile Azure DevOps work items directly from bug captures.
Configured Fields
- Organization URL:(Required)
- Personal Access Token (PAT):(Required)-Requires Work Items (Read & Write) scope.
- Project Name:(Required)
Permissions & Scope
Azure DevOps Personal Access Token with 'Work Items: Read & Write' scope.
Step-by-Step Setup Guide
- 1In Azure DevOps, click User Settings (top-right next to your avatar) > 'Personal access tokens'.
- 2Click '+ New Token', set Scopes to 'Custom defined', expand 'Work Items' and select 'Read & write'.
- 3Provide your Organization URL (e.g. https://dev.azure.com/your-org).
- 4Enter your Project Name exactly as named in Azure DevOps.
- 5Paste your PAT into BugSnap Settings > Azure DevOps, click 'Test Connection', and save.
Delivered Payload Preview
[
{
"op": "add",
"path": "/fields/System.Title",
"value": "[BugSnap] Checkout button unresponsive"
},
{
"op": "add",
"path": "/fields/System.Description",
"value": "<p>Bug captured via BugSnap</p><h3>Environment</h3><p>OS: Windows 11<br/>Browser: Chrome 132.0.0</p><p><a href=\"https://bugsnap.akusaraproject.my.id/v/cap_9a8f2\">View BugSnap Capture</a></p>"
}
]Common Issues & Resolutions
Ensure third-party application access via PAT is not disabled in your Azure DevOps Organization Policies.
Azure DevOps project names are case-sensitive and must match the URL slug.

Claude AI
AI & AutomationUse Anthropic Claude AI to generate root cause summaries and repro steps.
Configured Fields
- Anthropic API Key:(Required)-Generate from console.anthropic.com.
- Model Name:(Optional)
Permissions & Scope
Anthropic API Key with Claude 3.5 Sonnet access.
Step-by-Step Setup Guide
- 1Sign in to Anthropic Console at console.anthropic.com.
- 2Navigate to Settings > API Keys and click 'Create Key'.
- 3Copy your API key (starts with sk-ant-).
- 4In BugSnap Settings > Claude AI, enter your key. Optionally select your model (default: claude-3-5-sonnet-latest).
- 5Click 'Test Connection' -BugSnap runs a lightweight auth check without consuming chat tokens.
Delivered Payload Preview
### AI Root Cause & Repro Analysis (Claude 3.5 Sonnet) 1. Steps to Reproduce: - Navigate to /checkout with 1+ items in cart. - Click "Proceed to Payment". - Observed: Button spinner hangs; calculateTaxes fails. 2. Root Cause Analysis: - Uncaught TypeError at checkout.js:142 indicates state.cart.taxDetails is undefined before the async tax calculation promise resolves. 3. Recommended Fix: - Add optional chaining cart?.taxDetails?.rate or supply a fallback default tax object before mounting the checkout submit handler.
Common Issues & Resolutions
Check that the API key was copied completely without leading or trailing spaces.
Ensure your Anthropic account has available prepaid credits in Billing.

ChatGPT
AI & AutomationGenerate AI bug summaries, repro steps, and analysis via OpenAI.
Configured Fields
- OpenAI API Key:(Required)-Generate from platform.openai.com/api-keys.
- Model Name:(Optional)
Step-by-Step Setup Guide
- 1Open platform.openai.com and navigate to API Keys.
- 2Click '+ Create new secret key', name it 'BugSnap', and copy the key (starts with sk-).
- 3In BugSnap Settings > ChatGPT, paste your API key and optionally set the model (default: gpt-4o-mini).
- 4Click 'Test Connection' to verify API key validity without incurring prompt token charges.
Delivered Payload Preview
### AI Bug Diagnostic & Fix Guide (GPT-4o) 1. Steps to Reproduce: - Open https://app.example.com/checkout - Trigger payment submission with empty tax field - Network payload fails with HTTP 500 charge error 2. Root Cause: - Backend charge API rejects missing tax computation payload due to client-side unhandled exception. 3. Fix: - Validate tax calculation synchronously before dispatching the POST /v1/charge request.
Common Issues & Resolutions
Generate a new secret key at platform.openai.com/api-keys and paste it into BugSnap Settings.
Check your OpenAI account billing dashboard to add payment credits.
Google Gemini
AI & AutomationGenerate root cause analysis, repro steps, and fixes via Google Gemini.
Configured Fields
- Gemini API Key:(Required)-Generate from aistudio.google.com/app/apikey.
- Model Name:(Optional)
Permissions & Scope
Google AI Studio API Key with Gemini 1.5/2.0 model access.
Step-by-Step Setup Guide
- 1Sign in to Google AI Studio at aistudio.google.com.
- 2Navigate to 'Get API key' and click 'Create API key' in a new or existing Google Cloud project.
- 3Copy your generated API key (starts with AIzaSy...).
- 4In BugSnap Workspace Settings > Integrations > Google Gemini, paste your API key and optionally set the model (default: gemini-1.5-flash).
- 5Click 'Test Connection' or 'Pull Live Data' to verify connectivity and available models with zero chat spend.
Delivered Payload Preview
### AI Root Cause & Repro Analysis (Gemini 1.5 Flash) 1. Steps to Reproduce: - Load /checkout with multiple cart items. - Click "Submit Payment". - Unhandled rejection halts execution. 2. Root Cause Analysis: - TypeError: calculateTaxes is not a function at checkout.js:142. The tax calculator script failed to load before user interaction. 3. Recommended Fix: - Ensure the tax computation bundle is loaded statically or wrap the invocation in a safety check before triggering payment.
Common Issues & Resolutions
Ensure your API key from Google AI Studio is copied accurately without extra characters.
Check your Google Cloud / AI Studio project quota and ensure Generative Language API is enabled.