Blog › Tutorials

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

🔧 Tutorials · 5 min read · September 9, 2026 ·Updated: September 11, 2026
Overview Preparation: Create a Webhook flow in Lark Configure in BugCapturer Complete the Field Mapping What Gets Written to the Table Daily Usage FAQ

Overview

After configuring the Lark Bitable integration, every share report you generate in the BugCapturer extension is automatically written to the Bitable you specify as a new complete row: description, 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:
  • Effortless setup: the recommended Webhook trigger method needs no Lark app and no admin approval — configured in minutes
  • 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: when you save, the server sends a test request to the Webhook URL — connectivity is confirmed on the spot
  • 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, Lark Bitable supports two connection methods:
  • Method A: Automation Webhook trigger (recommended) — no Lark app needed. Create a Webhook-triggered flow under "Automation" in your Bitable and paste the URL — configured in minutes
  • Method B: Custom app (API) — 13 standard columns are created automatically on save, with no field mapping required; ideal for teams that need a unified column structure
For a detailed comparison and step-by-step guides for both methods, see the official docs · integrations overview.

Preparation: Create a Webhook flow in Lark

Open your Bitable and click Automation → New flow in the top right:
  • For the trigger, select "When a Webhook request is received" (displayed as "Webhook trigger" in some versions)
  • The system automatically generates a unique Webhook URL — copy it and keep it handy
  • We recommend enabling "Validate token" to prevent forged requests, and noting down the generated Bearer Token
    • No Lark app to create, no admin approval needed — that's all there is to the preparation.

    Configure in BugCapturer

  • Open app.bugcapturer.com/settings/integrations and sign in
  • In the platform list on the left, select "Lark Bitable" → click "Add Integration" → choose "Automation Webhook trigger" (recommended)
  • Fill in:
    • Name: e.g. "Bug Tracking Table"
    • Webhook URL: paste the URL copied in the previous step
    • Bearer Token (optional): only needed if you enabled token validation on the Lark side
  • Click "Verify & Save" — when saving, BugCapturer sends a test request to that URL

    • Complete the Field Mapping

    Back in the Lark flow editor:
  • In "Output settings", select "Set via request"
  • Lark automatically detects the test request it just received and lists all fields
  • Map the fields you need to the table columns one by one, then save and enable the flow
    • Once done, click "Test" on the card in the BugCapturer integrations page — a new record appears in your table right away, and your setup is complete.

    What Gets Written to the Table

    Column Content
    Description The reported issue description
    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 (message bodies not included — open the share link for the full content)
    Screenshot Screenshot link (click to open it directly)
    Share Link BugCapturer share page (full annotations, screen recording, diagnostic details)
    Submitted At / Expires At / Synced At Timestamps
    If you'd rather skip manual mapping and have the server create these standard columns automatically, switch to Method B · Custom app (API) instead. The overall process is more involved, though, so try it if it suits your needs. 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 Lark 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. the Webhook URL is no longer valid or the flow was disabled), the integration pauses automatically and you get an email; once fixed, click "Test" to verify and it resumes

    FAQ

    Save fails with a "Webhook URL validation" error? Make sure the URL was copied in full (including https://) with no stray spaces or line breaks. BugCapturer only supports public https URLs. Saved successfully but no data in the table? Make sure the Lark flow has been saved and enabled; if no field mapping is configured in "Output settings", incoming requests won't write anything to the table. Click "Test" on the integration card to trigger a new test record. Is the screenshot file itself written to the table? Currently a screenshot link is written — click it to view the full-resolution image. Is my data safe? Integration writes only trigger when you actively share; this data flow is disclosed in the privacy policy. More documentation: step-by-step guides in the official docs — Method A · Automation Webhook trigger / Method B · Custom app (API).

    #v1.3.2 #Lark Bitable #webhook integration #bug tracking #BugCapturer
    Share

    Related Articles