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
Feishu Bitable	✅ Available	Two connection methods, compared below
DingTalk	🚧 In development	Group robots & DingTalk tables planned
Slack	🚧 In development	Incoming Webhook & Block Kit messages planned
Microsoft Teams	🚧 In development	Channel Webhooks 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

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

Two ways to connect Feishu Bitable

	Method A: Automation Webhook trigger	Method B: Custom app (API)
App required	❌ No	✅ Custom app on the Feishu open platform
Setup time	~3 minutes	~10 minutes
Standard columns	Manual (or mapped from the test request)	✅ 14 standard columns auto-created
Permission	Table member is enough	App must be added as table collaborator
Data capability	One-way write	One-way write, server-controlled
Best for	Individuals, small teams, quick trials	Teams that need unified structure and long-lived ledgers

Recommended: start with Method A (Automation Webhook trigger) — no approval needed. Only move to Method B when you need auto-created standard columns.

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
• Up to 3 integrations per user: push different needs to different tables
• Delivery log keeps the latest 20 entries: view them via each integration’s “Delivery log”