bugscreen
docsslack

Slack integration

Connect a Slack workspace to an app so every bug report posts a message to a channel — with the screenshot threaded underneath.

Overview

Slack is a notification integration, not an issue tracker. Connecting it links one of your apps to a single channel in one Slack workspace. From then on, every report submitted from that app posts a formatted message to that channel, with the screenshot shared as a native Slack file in a thread under the message.

If the same app also has GitHub, Jira, or ClickUp connected, the Slack message includes one-click links to the ticket(s) created for the same report — so triage can start in Slack.

One workspace and one channel per integration. To post to several channels, connect Slack more than once — each connection targets its own channel.

Before you start

  • You've created an app in the BugScreen console.
  • You can sign in to a Slack workspace where you're allowed to install apps (or an admin can approve the install).

Connect Slack

  1. Open your app in the console and go to the Integrations section.
  2. Click Connect Slack. You'll be redirected to Slack to authorize BugScreen.
  3. Approve the install. BugScreen requests permission to post messages, list channels, upload files, and read your workspace name.
  4. Back in the console, pick the channel reports should post to, then confirm.
Public vs private channels. Public channels work without any extra step to post messages. For the screenshot to attach, though, the BugScreen app has to be a member of the channel — so for the best result, invite it (/invite @BugScreen) even to a public channel. If it isn't a member, reports still post, but in place of the screenshot the message shows a short note asking you to invite the app. To use a private channel, invite the BugScreen app to it in Slack first, then reload the channel picker — the app can only see and post to private channels it has been invited to.

What gets posted

Each report posts a single message containing:

  • A header with the report title and a severity emoji.
  • The reporter's severity and type as fields.
  • The description.
  • Links to any GitHub / Jira / ClickUp tickets created for the same report, when those integrations are also connected.
  • The screenshot, shared as a native Slack file in a thread under the message.
Severity is shown as an emoji and a field — Slack has no priority concept.

Test the connection

After connecting, use Test on the integration to confirm everything works end to end. The test posts a real sample message to the channel and shows you whether it succeeded.

Note: Testing posts a real sample message to the channel. You can delete it afterwards.

Disconnect

Disconnect the integration from the app's Integrations section to stop posting reports. BugScreen automatically revokes its bot token when you disconnect.

Revoking the token stops BugScreen from posting, but it does not remove the app from your workspace's installed-apps list. To fully uninstall, a workspace admin removes BugScreen via Slack's Apps → Manage page.

Troubleshooting

If a test or real report fails to post, check the following:

  • The bot isn't in the channel. For private channels, invite the BugScreen app to the channel, then reconnect.
  • The message posts but the screenshot is missing. The BugScreen app isn't a member of that channel — Slack lets it post to a public channel without joining, but a file upload needs membership. The message will say so; run /invite @BugScreen in the channel and screenshots will attach on the next report.
  • The channel was archived or deleted. Reconnect Slack and pick a live channel.
  • The install was revoked. The integration shows a Reconnect needed status — reconnect Slack from the console.
  • Connect is blocked with a plan-limit message. Your plan's integration limit has been reached — remove an unused integration or upgrade your plan.

Start shipping bug reports

Create an account to start shipping bug reports from your app.

Get started