Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.bugzy.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

Slack is Bugzy’s primary communication channel. Once connected, Bugzy posts test results, responds to questions, accepts disputed findings, and executes tasks — all through normal Slack conversations. Think of it as adding a QA teammate to your channel. No @mention needed — Bugzy listens to all messages in channels it’s been added to and responds when the message is relevant to QA, testing, or the project. Casual conversation is ignored automatically.

​
What you can do in Slack

ActionHowWhat happens
Ask Bugzy to run tests”Run smoke tests on checkout”Bugzy confirms and executes
Verify a PR”Verify PR #42”Bugzy runs relevant tests, posts results
Report a bug”The checkout button is broken on mobile”Bugzy logs the finding
Dispute a findingReply to a finding notificationBugzy re-evaluates, updates knowledge base
Ask about test results”What failed in the last run?”Bugzy responds with context
Get status”What’s the test status?”Bugzy summarizes recent results

​
The conversation model

Bugzy interacts via the inbox agent conversation model:
  1. An event triggers Bugzy (message, webhook, schedule)
  2. Bugzy proposes an action in the channel: “I’d like to run smoke tests on the checkout flow. Should I proceed?”
  3. A team member responds (thumbs up, “yes”, or custom instructions)
  4. Bugzy executes and posts results in the same thread
For automated triggers (cron, deployment hooks), Bugzy executes without confirmation and posts results directly.

​
Disputed findings

When Bugzy reports a finding that’s incorrect:
  1. Reply to the finding message with your reasoning
  2. Bugzy’s handle-message task processes the reply
  3. If the dispute is valid, the finding is updated
  4. Knowledge base adjusted to avoid similar false positives
  5. Bugzy confirms the resolution in the thread

​
Setup

1

Navigate to connections

Go to Dashboard > Projects > [Your Project] > Connections.
2

Connect Slack

Click Connect Slack. This opens the Slack OAuth flow managed by Nango.
3

Select workspace and authorize

Choose your Slack workspace and authorize the requested bot permissions.
4

Invite bot to channels

In Slack, open each channel where you want Bugzy to listen and respond. Click the channel name, go to Integrations > Add apps, and add the Bugzy app. Bugzy will automatically respond to relevant messages in these channels — no @mention required.
The bot can only read and post in channels it has been explicitly invited to. Public channels can receive messages via chat:write.public without an invite, but adding the bot is recommended for full functionality.

​
Bot permissions

The OAuth flow requests these scopes automatically:
ScopePurpose
channels:readList public channels in the workspace
chat:writePost messages to channels the bot is in
chat:write.publicPost messages to any public channel
reactions:writeAdd emoji reactions to messages
channels:historyRead message history for context

​
Troubleshooting

Bot not posting to a channel — Ensure the bot has been invited to the channel. Go to channel settings and add the Bugzy app under Integrations. “missing_scope” errors — The OAuth connection may need to be refreshed. Disconnect and reconnect Slack from Dashboard > Connections. Messages not reaching Bugzy — Verify the Slack connection is active in the project connections page. Nango handles token refresh automatically, but if issues persist, reconnect.