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

Each connection targets one Slack channel. Connect Slack again to notify another channel. Messages include links to issues created by your connected trackers.

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 find Connected destinations.
  2. Open the Add integration menu and choose 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.

Give BugScreen channel access

  • Public channel: messages can post without an invite, but screenshots require channel membership.
  • Private channel: invite BugScreen first, then reload the channel picker in the console.
  • Run the command below in the destination channel. Without membership, public-channel messages show an invite reminder instead of the screenshot.
text
/invite @BugScreen

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 integrations to confirm everything works end to end. It fires a sample report at every integration connected to this app, not just this one. 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 Connected destinations to stop posting reports, and BugScreen asks Slack to revoke its bot token.

The disconnect always takes effect on our side — BugScreen stops posting either way — but the revoke is best-effort, so the bot token is not guaranteed to be withdrawn in Slack. It also does not remove the app from your workspace's installed-apps list. To fully withdraw access, a workspace admin removes BugScreen via Slack's Apps → Manage page, which is the control that always works.

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.
    Slack Integration - Post Reports to a Channel | BugScreen