> ## Documentation Index > Fetch the complete documentation index at: https://docs.qawolf.com/llms.txt > Use this file to discover all available pages before exploring further. # Integrate with Slack > Connect Slack to add the QA Wolf agent to your Slack workspace, then add it to each channel where your team should be able to use it. Connecting Slack installs the QA Wolf app in your Slack workspace. That app is the [QA Wolf agent](https://docs.qawolf.com/agent-in-your-tools.md), and there's nothing else to turn on. It answers direct messages right away. In a channel, it answers once you've added it to that channel and mentioned it. ## Requirements * Access to a QA Wolf workspace * Permission to add apps to your Slack workspace ## Add the agent to Slack **Step 1** Open **Workspace settings → Integrations**. Under **Notifications**, select **Connect** on the **Slack** card. **Step 2** Follow the prompts to sign in to Slack and allow the QA Wolf app in your Slack workspace. **Step 3** Back in QA Wolf, confirm the Slack card reads **Connected**. A Slack workspace connects to one QA Wolf workspace at a time, so connecting fails if yours is already connected to another. ## Add the agent to each channel Connecting Slack doesn't add the agent to any channel. Add it to each channel separately by sending this in the channel: ```text theme={null} /invite @QA Wolf ``` This works in public and private channels. Direct messages need no invite: search Slack for **QA Wolf**, open the app, and message it. In a channel, mention `@QA Wolf` to ask it something. Once it's answering in a thread, replies in that thread don't need the mention. ## What you can ask the agent The agent works from your QA Wolf workspace: its flows, runs, environments, and bug reports. * **Why a run failed** — "Why did the checkout flows fail on staging this morning?" * **Where things stand** — "What's the status of our latest runs?" Ask for a summary you can paste into a standup or a status update. * **Report a bug** — describe what you saw. Unless you've already said what caused it, the agent confirms the details before it files a bug report. * **Fix a flow** — "The login flow broke after today's deploy. Fix it." * **Run flows** — name the flows and the environment. If you don't name any flows, the agent asks which. * **Add coverage** — "We don't have a flow for applying a coupon. Add one." Attach screenshots to show what you mean. The agent reads up to five images per message and ignores other files. It reads the thread it's in. It doesn't read your other channels or direct messages, except shared channels with QA Wolf that your QA Wolf representative sets up for it. It never runs your application's source code. Anyone in your Slack workspace can ask for any of these, in a direct message or by mentioning `@QA Wolf` in a channel the agent is in. They don't need a QA Wolf account. ## Agent notices If the agent posts one of these notices, here's what to do: | Notice | What to do | | - | - | | "…its QA Wolf team doesn't have a default environment." | Set a default environment for your QA Wolf workspace, then ask again. | | "…I can't determine which QA Wolf user should own this conversation." | Create a [trigger](https://docs.qawolf.com/triggers/overview.md) on your default environment, then ask again. | | "…QA Wolf doesn't have permission to upload files in this Slack workspace yet." | Under **Workspace settings → Integrations**, disconnect Slack and connect it again, and allow the new permission when Slack asks. | ## Agent doesn't respond If the agent doesn't reply at all, check these: | Cause | What to do | | - | - | | The message doesn't mention the agent. | In a channel, mention `@QA Wolf` in your message. Replies in a thread it's already answering don't need the mention. | | The agent isn't in the channel. | Send `/invite @QA Wolf` in the channel, then ask again. | | Slack isn't connected. | Check that the Slack card under **Workspace settings → Integrations** reads **Connected**. | | A bot or a Slack workflow posted the message. | Post the request yourself. The agent answers people only. | | The message was edited. | Post the request again as a new message. The agent doesn't read edits. | | The agent took the message as meant for someone else, for example a reply that tags another person. | Mention `@QA Wolf` in your message. | | Someone in the thread told the agent to stop replying. | Mention `@QA Wolf` in the thread with your new request. | ## Disconnect Slack Under **Workspace settings → Integrations**, open the Slack card's menu and select **Disconnect**. The agent stops answering in your Slack workspace, except in shared channels with QA Wolf where your QA Wolf representative turned it on. ## Run alerts and bug reports QA Wolf can post run alerts, new bugs, new blockers, and questions to the Slack channels you choose. These come from QA Wolf, not from the agent, and connecting Slack doesn't turn them on. An organization admin sets them up under **Workspace settings → Notifications**, in the **Slack** section: turn on each type you want and choose its channel. A run alert also links that run's new bugs, blockers, and questions in its thread. To post in one of your own channels, first add the agent to it with `/invite @QA Wolf`. If you haven't connected Slack, you can choose your shared channels with QA Wolf instead. ## Shared channels with the QA Wolf team A shared channel is a Slack Connect channel between your Slack workspace and QA Wolf's, where your team works with QA Wolf's people. You don't need to connect Slack to have one. If you've connected Slack, the agent answers in a shared channel the same way as in your other channels: mention `@QA Wolf`. If you haven't, it answers there once your QA Wolf representative turns it on for that channel. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.