> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/settings/integrations/messaging-apps/slack.md).

# Slack

Learn how to connect your Slack organization to Swarmia.

{% hint style="info" %}
In order to set up the Slack integration with Swarmia, you must be a Slack workspace administrator or have permission to add apps to that Slack workspace. For more information, see the [Slack Help Center](https://slack.com/help/articles/222386767-Manage-app-approval-for-your-workspace).
{% endhint %}

\
\\

## **Connecting Slack to Swarmia**

1. Sign in to the [Swarmia app](https://app.swarmia.com/) and go to [Slack settings](https://app.swarmia.com/settings/slack).
2. Find the Slack tab under Integrations on the setting page, click **Connect to Slack.**
3. If you're not already signed in to Slack, on the **Sign in to your workspace** page, enter your workspace name, and then choose **Continue**.
4. On the **Swarmia is requesting permission to access the your-workspace-name Slack workspace** page, choose **Allow**.

{% hint style="info" %}
Once the Slack integration is complete, you'll want to configure your

* [Team Notifications](/settings/team/team-notifications.md)
* [Personal Notifications](/settings/personal/notifications.md)
  {% endhint %}

\\


---

# 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://help.swarmia.com/settings/integrations/messaging-apps/slack.md?ask=<question>&goal=<user_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.