> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/integrations/other/slackbot-for-odin.md).

# Slackbot for Odin

## **How to Integrate Slack with HockeyStack Odin**

1. Go to Atlas > Export >  Slack - Odin

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2FeFwaP3AhzZJV5hfXJo6n%2FScreenshot%202026-04-23%20at%209.56.49%E2%80%AFAM.png?alt=media&amp;token=21f6856f-c612-4dd0-b52c-50d5b8788ebe" alt=""><figcaption></figcaption></figure>

2. Click the **"Add to Slack"** on the modal
3. The Slack OAuth screen will appear. Select the workspace you want to integrate with
4. After selecting the workspace, you will be redirected to a dedicated website
5. On the redirect page, choose the HockeyStack domain you want to connect to
6. Once the domain is selected, the Slack bot will appear in your workspace, connected to the chosen domain

This connection will let you and your coworkers chat with Odin using Slack! Please remember that it's only available for HockeyStack users.


---

# 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.hockeystack.com/integrations/other/slackbot-for-odin.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.