Slack delivery

Nobody checks a dashboard on the off-chance. Connect a channel and the bug comes to you instead.

Setting it up

You need something Slack calls an Incoming Webhook — a private URL that lets BugClip post into one channel and do nothing else. It takes about two minutes to make one.

• Go to api.slack.com/apps and click Create New App → From scratch. Call it anything (“BugClip” works) and pick your workspace.
• In the sidebar under Features, open Incoming Webhooks and switch it on.
• Click Add New Webhook to Workspace and choose the channel you want reports in.
• Copy the URL Slack gives you. It starts with https://hooks.slack.com/services/…
• Back in BugClip, open Widget settings from the project's ⋯ menu, paste the URL into Slack notifications, and save.
• Click Send test message. If it turns up in the channel, you're done — real reports will follow the same path.

Adding a second project later? You don't need a second Slack app. Open that same Incoming Webhooks page, add another webhook for the other channel, and paste that one into the other project.

What a message looks like

Every report posts a card with:

• The reporter's note — usually enough to triage on its own.
• Which project it came from, and whether it's a screenshot or a video.
• The page it happened on.
• A one-line error summary, like 1 uncaught error · 2 failed requests.
• A View report button that opens the full thing.

Worth knowing

• Your webhook URL is stored on our server and never handed to the widget, so it can't be scraped off your site.
• If Slack is down, the report still uploads and appears in your dashboard. You just don't get the ping.
• To disconnect a channel, clear the field and save.
• The View report link needs a BugClip login. To send a report to someone outside your workspace, use a share link instead.