Lark group bot

A Lark group bot (a custom bot) posts every new report as a card message into one group chat. No Lark app and no admin approval are needed: you create the bot inside the group, copy its webhook URL, and paste it into BugCapturer.

Note

This is a notification target: reports are not stored in Lark. If you also want a trackable ledger, connect Lark Bitable at the same time — the two work side by side.

Step 1: Create the custom bot

1. Open Lark and go to the target group
2. Group settings → Bots → Add bot → Custom bot
3. Set an avatar and a name, then click Add
4. Copy the generated webhook URL — it looks like https://open.larksuite.com/open-apis/bot/v2/hook/…

Step 2: Add the integration in BugCapturer

1. Sign in at app.bugcapturer.com and open the “Integrations” page
2. Pick Lark group bot in the platform list → click “Add integration”
3. Paste the webhook URL
4. Signature secret (optional): only if you enabled signature verification in the bot settings
5. Pick the card language, then click “Verify & save”

On save we post a test card into the group. Once you see it there, you are all set.

Step 3: Pick one security setting

Lark offers three settings and they can be combined, but one is enough:

Setting	What it does	Recommendation
Signature verification	Every request carries a timestamp + sign; Lark rejects anything it cannot verify	Recommended — we store the secret and sign every delivery for you
IP allowlist	Only requests from the listed IPs are accepted	Fine if your policy requires it — remember to add our egress IP
Custom keywords	The message must contain at least one keyword	Not recommended — the card copy would have to keep matching your keywords

Caution

If you use the IP allowlist, add 47.236.11.198 (our egress IP). Without it Lark rejects every request with 19022 Ip Not Allowed and nothing ever reaches the group.

What the card contains

Part	Content
Title	🐞 [bug] <first line of the report>
Body	Page, environment (browser · OS · screen) and diagnostic counts (Console 3 · Network 2)
Button	View full report — opens the BugCapturer share page

Note

The card carries no screenshot. Lark card images must first be uploaded to Lark (image_key), which a custom bot cannot do. Open the report to see the annotated screenshot, console errors and failed requests.

Group chat is a public surface, so the card only carries diagnostic counts — never the error text itself.

How to tell if it really arrived

A successful delivery means Lark accepted the request (code == 0) — not that someone read it. To confirm:

1. Open the integration → Delivery log
2. Green rows show code 0 plus the raw response from Lark
3. Rejected deliveries are red and carry Lark’s own error code (19021 signature, 19022 IP allowlist, 19024 keywords)

Failed deliveries are retried twice (after 5s and 15s); after 20 consecutive failures the integration is disabled and we email you. See Delivery logs and Auto-disable.

Troubleshooting

Symptom	Cause	Fix
19021 sign match fail	The secret does not match, or the server clock drifted by more than an hour	Re-copy the secret from the bot settings, or leave the secret empty
19022 Ip Not Allowed	The bot’s IP allowlist does not contain our egress IP	Add 47.236.11.198
19024 Key Words Not Found	Custom keywords are enabled and the card did not match any of them	Switch to signature verification instead
No card, but the delivery log is green	Delivery succeeded on our side — check whether you are looking at the right group	Open the delivery log and read the raw response
No card and the log is red (invalid or deleted)	The bot was removed from the group, or the URL was regenerated	Copy a fresh URL from the group settings and save the integration again

Cards vs. records

	Lark group bot (this page)	Lark Bitable
Type	Notification (card into a chat)	Record (a row in a table)
Stored in Lark	No	Yes — filter, sort, assign, revisit
Best for	Teams that want to know immediately	Teams that need a ledger

One bot is bound to one group. To notify several groups, add one integration per group.