Slack delivery
Each project can post its reports to its own Slack channel — one channel per client, if that's how you work.
Setup
You need a Slack Incoming Webhook — a URL that lets BugClip post into one channel, and nothing else. Creating one takes about two minutes:
- Go to api.slack.com/apps → Create New App → From scratch. Name it anything (“BugClip” works) and pick your workspace.
- In the app's sidebar under Features, open Incoming Webhooks, switch it on, then click Add New Webhook to Workspace and choose the channel reports should land in.
- Copy the URL Slack shows you — it starts
https://hooks.slack.com/services/… - In BugClip, open the project's Widget settings, paste the URL into Slack notifications, and save.
- Click Send test message and check the channel. If the test arrives, real reports will too.
Already made the app once? Your webhook URLs stay listed on that same Incoming Webhooks page, each with a copy button — you never need to create a second app for more channels, just add another webhook to it.
What gets posted
Every uploaded report posts a card with the reporter's note, the project name, report type, the page it came from, a summary of captured errors (e.g. 1 uncaught error · 2 failed requests), and a View report button into the dashboard.
Good to know
- The webhook is stored server-side only — it is never exposed to the widget or anyone visiting the site.
- Delivery is best-effort: if Slack is down, the report still uploads and appears in the dashboard.
- Clearing the field and saving disconnects the channel.
Slack delivery is a Pro feature. If your plan lapses, the saved webhook is kept but delivery pauses — upgrading resumes it. See Plans & billing.