Turn every report from your site
into a fully loaded Lark record

Screenshots, page URLs, Console errors and failed requests come attached β€” your team opens Lark and starts fixing, with nothing to follow up on.

Choose your connection method

⚑Bitable automation webhookRecommended

Let Lark's own automation receive the report and write it into the table. No app review needed.

  • Fastest to set up β€” paste one webhook URL
  • No app credentials to manage or rotate
  • Best for individuals and small teams
Setup guide β†’
πŸ”‘Your own Lark app

Create a Lark custom app and give BugCapturer its credentials. The most direct and most controllable route.

  • Full control over the target table and permissions
  • No automation platform required
  • Best when IT already manages Lark apps
Setup guide β†’
πŸ€–Lark group bot

Push new reports straight into your project chat, so nobody has to watch a table.

Setup guide β†’

Three steps to a live integration

1

Open the table

Prepare the Bitable and decide which columns should receive which values.

β†’
2

Connect

Either paste your app credentials, or paste the automation webhook URL from Lark.

β†’
3

Send a test report

Use the test button to confirm a row appears, then bind the integration to the project.

What lands in each column

You choose which table and which fields β€” the payload is stable and predictable.

FieldContent
DescriptionThe text the reporter typed
TypeBug, suggestion, question, and so on
Page URL and titleWhere the report was submitted, with sensitive parameters masked
EnvironmentBrowser, operating system, viewport and pixel ratio
Error counts and messagesTwo count columns plus two message columns β€” one line per error, up to 10 each
Screenshot and share linkA link back to the full report in the browser
ReporterThe nickname of whoever submitted, falling back to the email prefix