Bug reports, straight into your Slack channels

Every share becomes a Block Kit card carrying the page, the environment, diagnostics and a link to the annotated screenshot β€” plus a button that opens the full report. Setup is a single Incoming Webhook URL: no OAuth, no app review.

Live in three steps

Create the webhook in Slack, paste it into BugCapturer, confirm the test card.

1

Create an Incoming Webhook

In api.slack.com/apps create an app, enable Incoming Webhooks, then use "Add New Webhook to Workspace" to pick a channel and copy the generated URL.

β†’
2

Paste it into BugCapturer

Integrations β†’ Slack β†’ Add integration. Only hooks.slack.com URLs are accepted, because that URL can post into your workspace.

β†’
3

Confirm the test card

We post a test card when you save. Once it lands in the channel, every new share is posted there automatically.

Everything a developer needs at a glance

The card is built to be triaged from Slack, without clicking through to find out what broke.

πŸ–ΌοΈ

Screenshot link

A link to the annotated screenshot is always included; Slack renders the image inline when it can fetch it.

🧭

Page & environment

Page title, linked to the sanitized URL, plus browser, OS and screen resolution.

πŸ”’

Diagnostics counts

Console and network error counts only β€” error contents can contain tokens and a channel is a public surface.

πŸ”€

One URL, one channel

Slack webhooks are channel-scoped: add one integration per channel, or post into a single channel and route further inside Slack.

Built like every other BugCapturer integration

Retries, delivery logs and auto-disable are shared with all other targets.

πŸ”

Retries with backoff

Failed posts are retried twice (5s / 15s) before being recorded as a failure.

⏸️

Auto-disable

20 consecutive failures pause the integration and email you, so a revoked webhook cannot fail silently forever.

πŸ”’

Credential-safe

The webhook URL is treated as a secret: we only ever show its last 6 characters back.

🧾

Delivery log

Every attempt, status code and error summary is kept for the last 20 deliveries.