> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/connectors/source-catalog/community/slack.md).

# Slack

## **Why syncing my Slack data to** [**Whaly**](https://whaly.io)**?**

Syncing your Slack can be useful for various use cases:

* Monitor the number of Active Users on your Slack workspace and their number of exchanged messages
* Understand who are your most engaged Users and on which Channels they are exchanging information
* Track your historical number of Users for "public" Slack communities
* ...

## Which Slack data is synced by [Whaly](https://whaly.io)?

[Whaly](https://whaly.io) 🐳 is currently syncing the following data:

* **User**: A member in your workspace.
* **Conversation**: A conversation object contains information about a channel-like thing in Slack. It might be a public channel, a private channel, a direct message, or a multi-person direct message.
* **Conversation Member**: Link Users and Conversations in which they belong.
* **Message**: Messages are text communication exchanged on Conversations by Users.

{% embed url="<https://docs.google.com/presentation/d/1FlTN9qShuyexnm_4F-SUZMMRxu4r_uhnlGtpGJW20RE/edit?usp=sharing>" %}

[You can find the relationship between all those objects here.](https://docs.google.com/presentation/d/1FlTN9qShuyexnm_4F-SUZMMRxu4r_uhnlGtpGJW20RE/edit?usp=sharing)


---

# 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.whaly.io/connectors/source-catalog/community/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.