Feishu Bitable Integration: Auto-Sync Bug Reports to Your Table

Overview

After configuring the Feishu Bitable integration, every share report you generate in the BugCapturer extension is automatically written to the Bitable you specify as a new complete ledger row: description, type, page, environment, diagnostic summary, screenshot link, share link — without disturbing anyone in your group chat, and your team can filter and review entries anytime. Key features:

Zero manual table setup: 14 standard columns are created automatically when you save the integration (existing columns with the same name are reused)

Multiple tables: add up to 3 integrations, each pointing to a different table — perfect for keeping a "Bug tracking table" and a "Product request table" separate

Verified on save: before saving, the server runs the full four-step check "verify credentials → confirm table is writable → create columns → write a test record"

Failures are visible: failed writes are retried automatically and logged in the delivery log; after 20 consecutive failures the integration is paused automatically and you get an email

Since v1.3.2, Feishu Bitable supports two connection methods:

Method A: Automation Webhook trigger (recommended) — no Feishu app needed. Create a Webhook-triggered automation in your Bitable and paste the URL; configured in minutes

Method B: Custom app (API) — the method described in this article; 14 standard columns are created automatically, ideal for teams that need a unified structure

For a detailed comparison and step-by-step guides, see the official docs · integrations overview.

Preparation: Create a Feishu App

Feishu Bitable connects through a custom enterprise app (App ID + App Secret), in four steps:

1. Create a custom enterprise app

Open the Feishu Open Platform → Developer Console → Create Custom App, and fill in the app name and description (e.g. "BugCapturer Ledger Sync").

2. Enable Bitable permissions

Go to your app → Permissions & Scopes → search for and enable:

bitable:app (view, comment, edit and manage Bitable)

If your table lives in a wiki, also wiki:wiki:readonly (view wiki)

3. Publish the app

Go to Version Management & Publishing → Create Version → Submit for release. Custom apps are usually approved directly by the workspace admin.

4. Add the app as a table collaborator

Open your Bitable → "..." in the top right → More → Add Document App → search for your app and add it as an editable collaborator. > Without this step the app cannot write to the table due to missing collaborator permission — the most common setup mistake.

Configure in BugCapturer

Open app.bugcapturer.com/settings/integrations and sign in

Click "Add Integration" and read through the four-step guide to reach the form

Fill in:

Name: e.g. "Bug Tracking Table"

App ID: starts with cli_

App Secret: copy it from the app's Credentials & Basic Info page

Bitable URL: paste the full link from your browser's address bar (including the table= parameter; wiki links are supported too and resolved automatically)

Click "Verify & Save" — the server runs the four-step check automatically. Once everything passes, the integration goes live and a test record appears in your table immediately

What Gets Written to the Table

The following standard columns are created automatically on first save (existing columns with the same name are reused; your column types are never modified):

Column	Content
Description	The reported issue description
Type	Bug / Feature / Suggestion / Praise
Page URL	URL of the page where the issue occurred (sensitive parameters redacted)
Page Title	Page title
Browser / OS / Resolution	Environment info
Console Errors / Network Errors	Diagnostic summary counts (full details are in the share link)
Screenshot	Screenshot link (click to open full resolution)
Share Link	BugCapturer share page (full annotations, screen recording, diagnostic details)
Submitted At / Expires At / Synced At	Timestamps

You can freely add or remove your own columns in the table (e.g. "Owner", "Priority", "Status") — the integration is not affected.

Daily Usage

Once configured, no extra action is needed: click "Share" in the extension → a new row appears in the table automatically. The share success panel shows "Synced to N tables automatically".

Test write: each integration card in the settings page has a "Test" button to verify the write anytime

Delivery log: check the status, failure reason and Feishu record ID of the last 20 writes

Pause / Resume: pause when you temporarily don't want to sync, resume anytime

Consecutive-failure protection: after 20 consecutive failed writes (e.g. rotated secret, app removed from collaborators), the integration pauses automatically and you get an email; after fixing, click "Test" to verify and it resumes

FAQ

Save fails with "invalid credentials"? The App ID or App Secret was copied incorrectly, or the app hasn't been published yet. Re-copy from the credentials page and make sure the app is published. Save fails with "missing table collaborator permission"? The app wasn't added as a table collaborator. Go back to the "Add the app as a table collaborator" step. Does it upload the screenshot file itself? Currently a screenshot link (never expires) is written — click it to view the full-resolution image. Direct attachment upload is on the roadmap. Is my data safe? Integration credentials and server-side writes only trigger when you actively share; this data flow is disclosed in the privacy policy. More documentation: step-by-step guides (including Method A field mapping) in the official docs — Method A · Automation Webhook trigger / Method B · Custom app (API).