Feishu Bitable · Method A: Automation Webhook trigger

Feishu Bitable’s built-in Automation supports flows triggered by incoming Webhook requests. This is a completely separate path from the open-platform custom app: individuals and small teams can set it up in a few clicks, with no app application and no admin approval.

This is the recommended way to integrate BugCapturer.

Prerequisites

• A Feishu account with edit access to the target Bitable
• No Feishu app required

Step 1: Create an automation flow in Feishu

1. Open the target Bitable, click “Automation” in the top-right → “New flow”
2. Choose “When a Webhook request is received” as the trigger
3. Feishu generates a unique Webhook URL — copy it for the next step
   • If you enable “Verify token”, note the generated Bearer token (optional, recommended to prevent forged requests)
4. Keep the flow editor open and continue below

Step 2: Add the integration in BugCapturer

1. Sign in at app.bugcapturer.com and open the “Integrations” page
2. Select “Feishu Bitable” in the left platform list → click “Add integration”
3. Choose “Automation Webhook trigger” (recommended)
4. Fill in:
   • Name: anything recognizable, e.g. “Client bug ledger”
   • Webhook URL: paste the URL from step 1
   • Bearer token (optional): only if you enabled token verification in Feishu
5. Click “Verify & save”

Step 3: Generate the field mapping

On save, BugCapturer sends a test request to your Webhook URL. Back in the Feishu flow editor:

1. In the flow’s “Output settings”, choose “Set via sent request”
2. Feishu listens for requests arriving within 3 minutes, automatically lists every field of the test record it just received
3. Map the fields you need to table columns, then save and enable the flow

Afterwards click “Test” on the integration card and confirm a new row appears in the table.

Field reference

The JSON body BugCapturer sends contains the following fields (all text, mappable to plain-text columns):

Field	Meaning	Example
source	Source marker, always BugCapturer	BugCapturer
description	Problem description (truncated when too long)	Login button unresponsive
feedback_type	Report type	bug / suggestion
page_url	URL of the page where it happened	https://example.com/login
page_title	Title of that page	Sign in - Example
browser_info	Browser and OS	Chrome 128 / Windows 11
screen_resolution	Screen resolution	1920x1080
console_errors	Console errors summary (count + first 3)	2 items - TypeError: …
network_errors	Network errors summary (count + first 3)	1 item - GET /api → 500
screenshot_url	Screenshot link	https://…/api/shares/xxx/file
report_link	Full link to the shared report	https://app.bugcapturer.com/share/xxx
submitted_at	Submission time (Beijing time text)	2026-09-09 14:30:00
expires_at	Share expiry time (Beijing time text)	2026-12-08 14:30:00

Suggested mapping

Map description to “Description”, feedback_type to “Type”, screenshot_url / report_link to link columns and submitted_at to a date column — that covers most ledger scenarios.

FAQ

“Validating Webhook URL” fails on save? Make sure the URL was copied completely (including https://) with no stray spaces or line breaks. BugCapturer only accepts public https URLs.

Save succeeded but nothing appears in the table? Confirm the flow is saved and enabled; without output mappings an incoming request writes nothing. Click “Test” on the integration card to fire another test record.

Can screenshots go into native attachment columns? No. Automation Webhooks only write text fields; screenshots are provided as a screenshot_url link. For native attachments use Method B.

Can one table have multiple integrations? Each table’s flow generates its own Webhook URL. Each BugCapturer account can hold up to 3 integrations.