Integrations overview

BugCapturer integrations connect “capturing a bug report” with “recording it in your team’s workspace”: after you annotate, screenshot and submit a share in the browser, the report is written automatically into the target table or channel you configured.

How it works

1. A team member submits a bug report through the BugCapturer extension and creates a share
2. Right after the share is created, the BugCapturer backend writes the report into your configured integration target
3. Every write (success/failure, retries) is recorded in the delivery log, visible on the integrations page

Writes are asynchronous

A write usually completes within seconds after the share is created. If the target service is temporarily unavailable we retry twice (5s / 15s backoff). An integration that fails 20 times in a row is automatically disabled and you get an email notification.

Supported platforms

Platform	Status	Notes
Slack	✅ Available	Block Kit card into a channel, see Slack
Microsoft Teams	✅ Available	Adaptive Card into a channel via a Workflows webhook, see Microsoft Teams
Lark group bot	✅ Available	Card into a group chat via a custom bot, see Lark group bot
Lark Bitable	✅ Available	Two connection methods, see Lark Bitable
Custom Webhook	✅ Available	Signed JSON to any endpoint: n8n, Zapier, Make, your own system
DingTalk	🚧 In development	Group robots & DingTalk tables planned
WeCom	🚧 In development	Group robot push planned
Notion	🚧 In development	Database writes planned
GitHub	🚧 In development	Issue creation planned
GitLab	🚧 In development	Issue creation planned
Jira	🚧 In development	Issue creation planned

Chat cards vs. record-type integrations

Slack, Microsoft Teams and the Lark group bot are notification targets: the report is posted as a card into a channel or group and is not stored there. For a trackable table/board (filter, assign, follow up), use a record-type target such as Lark Bitable — or push into a chat and a table at the same time.

Where to configure: sign in and open the integrations page. The left column lists all platforms; click one to open its configuration panel.

Common limitations

• One-way write: data can only be written, never read back, modified or deleted
• Attachments as links: screenshots and log files are not uploaded as native attachments; a URL is written into the cell instead
• 1 integrations per user: push different needs to different tables
• Delivery log keeps the latest 20 entries: view them via each integration’s “Delivery log”