> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/scout/connections/slack.md). # Slack Scout works in Slack as its own app. You and Scout talk in its direct message, and drafts arrive as cards you can send with one tap. Scout works in Slack as its own app. Once it's in your workspace, you and Scout talk in its direct message, and that's where your briefs, heads-ups and drafts arrive. ## Connect * **From your signup email**: click **Add Scout to Slack**. It adds the app to your workspace and links you to your Scout. * **From your Scout page**: open [**Scout**](https://app.spara.co/scout) in Spara and, under **Accounts**, connect Slack. Scout links you by your email address. If your Slack email is different, use **Sign in with Slack**. Connect your inbox first. Scout needs to be in your Slack workspace with its own permissions. If your company's workspace already has Scout, you're linked straight away. ## How it works * **One direct message.** Message Scout there. Each thread is a conversation, and replies in the thread continue it. * **Cards you can act on.** Connections arrive as cards with a Connect button. Drafts arrive as cards with **Edit**, **Discard**, **Open in Gmail** and **Send**. When Scout asks a question with a known set of answers, it gives you buttons, and typing always works too. * **Jobs post new messages.** When a job has something for you, it's a new message in the same direct message. Reply to it to pick the item up; that starts a fresh conversation. * **Long work shows its progress.** When Scout is working through a lot, it posts one progress message and updates it in place. ## Slack and text together If you've also linked a phone, Scout answers wherever you wrote. Ask for something on the other surface when you want it there: "text me that", "send it to my Slack". See [Text](/scout/connections/text.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.spara.com/scout/connections/slack.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.