Screenshots, page URLs, Console errors and failed requests come attached β your team opens Feishu and starts fixing, with nothing to follow up on.
Let Feishu's own automation receive the report and write it into the table. No app review needed.
Create a Feishu custom app and give BugCapturer its credentials. The most direct and most controllable route.
Push new reports straight into your project chat, so nobody has to watch a table.
Prepare the Bitable and decide which columns should receive which values.
Either paste your app credentials, or paste the automation webhook URL from Feishu.
Use the test button to confirm a row appears, then bind the integration to the project.
You choose which table and which fields β the payload is stable and predictable.
| Field | Content |
|---|---|
| Description | The text the reporter typed |
| Type | Bug, suggestion, question, and so on |
| Page URL and title | Where the report was submitted, with sensitive parameters masked |
| Environment | Browser, operating system, viewport and pixel ratio |
| Error counts and messages | Two count columns plus two message columns β one line per error, up to 10 each |
| Screenshot and share link | A link back to the full report in the browser |
| Reporter | The nickname of whoever submitted, falling back to the email prefix |