Feishu Bitable · Method B: Custom app (API)

Use the Feishu open-platform “custom app” API when you want BugCapturer to auto-create standard columns and keep a unified table structure. This method requires creating an app on the open platform and suits admins setting up team ledgers; for quick trials prefer Method A (Automation Webhook trigger).

Prerequisites

• A Feishu account (individual accounts can create custom apps)
• Access to the target Bitable
• About 10 minutes

Step 1: Create a Feishu custom app

1. Open the Feishu open platform, sign in and enter the “Developer Console”
2. Click “Create custom app”, fill in the name (e.g. BugCapturer) and description
3. Once created, copy the App ID (starts with cli_) and App Secret from “Credentials & basic info”

Step 2: Enable Bitable permissions and publish

1. In the app, open “Permissions”, search and enable bitable:app (view, comment, edit and manage Bitable)
2. Open “Version management & release”, create a version and publish
   • Individual accounts usually need no admin approval; enterprise tenants might

Step 3: Add the app as a table collaborator

1. Open the target Bitable, click ”…” in the top-right → “More” → “Add document app”
2. Search for your app, add it with “Can edit” permission

Collaborator access is required

If the app has no collaboration permission on the table, saving the integration fails with a permission error. If your app does not show up in the “Add document app” search, first add the “Bot” capability to the app on the open platform and publish a new version — without the Bot capability the app cannot be found in the search.

Step 4: 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” → choose “Custom app (API)”
3. Fill in App ID, App Secret, and paste the Bitable URL from the browser address bar (must contain the table parameter, e.g. https://xxx.feishu.cn/base/bascnXXXX?table=tblYYYY&view=vewZZZ; wiki /wiki/ links are supported too)
4. Click “Verify & save”

On save the server runs a four-step check: verify credentials → parse the table → auto-create missing standard columns → write one test record. Any failure is reported with its step on the page.

Standard columns created automatically

If any of the following columns are missing, BugCapturer creates them (existing same-name columns are kept untouched):

Column	Type	Meaning
描述 (Description)	Text	Problem description
类型 (Type)	Text	bug / suggestion
页面 URL (Page URL)	Text	Page where it happened
页面标题 (Page title)	Text	Title of that page
浏览器 (Browser)	Text	Browser info
操作系统 (OS)	Text	Operating system
分辨率 (Resolution)	Text	Screen resolution
控制台错误数 (Console errors)	Number	Console error count
网络错误数 (Network errors)	Number	Network error count
截图 (Screenshot)	Link	Screenshot URL
分享链接 (Share link)	Link	Full link to the shared report
提交时间 (Submitted at)	Date	Report submission time
到期时间 (Expires at)	Date	Share expiry time
同步时间 (Synced at)	Date	When this row was written

Method A vs Method B

	Method A: Webhook trigger	Method B: Custom app (API)
App required	No	Yes
Standard columns	Mapped manually	Auto-created
Attachment columns	Links only	Screenshot written as a link
Admin approval	Not needed	May be needed on enterprise plans
Best for	Individuals / small teams	Team ledgers with unified structure

Both methods can coexist: the same account can configure Method A and Method B integrations for different tables (3 in total).

FAQ

“Invalid credentials” error? Check that the App ID / App Secret were copied fully; credentials may reset after publishing a new version — always use the latest values from “Credentials & basic info”.

Do I need to re-enter the App Secret when editing? No. Leaving the Secret empty on edit keeps the old value; changing credentials or the table link triggers a re-verification.

Troubleshooting

When saving fails, the page shows the exact error message and error code. Find yours below (all are real-world pitfalls observed during testing):

Error / code	Cause & fix
“Missing required scopes” (code 99991672)	Scopes are incomplete or not yet effective: enable them via the link in the error (bitable:app for regular tables; wiki tables also need wiki:wiki:readonly), then create and publish a new app version — enabling scopes without publishing does not take effect
“Table not found” / “document not found” (code 131005)	Feishu returns “not found” for wiki nodes the app has no access to, so treat it as a permission issue first: 1) the app has the “Bot” capability added and a version published; 2) the app was added via ”…” → “More” → “Add document app” on the target table page; 3) the URL was copied in full from the browser address bar. Personal-edition wikis may lack the “Add document app” entry — move the table to “My Space” and use its /base/ link instead
“No collaboration permission” (code 91403)	The app was not added as a collaborator on that table: open the table → ”…” → “More” → “Add document app” → search the app name → add with “Can edit”
“Failed to create standard columns”	The collaborator permission was set to “Can read”: re-add the app with “Can edit” and retry. Existing same-name columns are skipped automatically — no need to delete any headers

Three permission layers — all required

Feishu permissions have three layers, and all must be in place: 1) API scopes enabled on the open platform and a version published; 2) the app added as a table collaborator at the document level; 3) wiki tables additionally require the app to have the “Bot” capability. A missing layer fails the save, and the error message usually points at only one of them — always check all three when troubleshooting.