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

# Slack Integration

Connect your Slack workspace to Tellius so your team can ask data questions and get AI-powered answers (charts, summaries, document-based insights, and deep analytical workflows) directly inside Slack.

### What you can do with the Slack integration

Once the Tellius bot is set up in your Slack workspace, your team can:

* Ask Kaiya questions in a direct message with the bot, or by mentioning @Tellius in any channel where it has been added.
* Choose the data source for each question. Let Kaiya auto-select the most relevant Business View, manually pick one or more specific Business Views, or search across unstructured documents.
* Receive responses formatted natively in Slack, with chart images, text summaries, inline citations to source documents (for unstructured queries), and markdown formatting.
* Run **Deep Insight** workflows for complex analytical questions, with live step-by-step progress updates as Kaiya generates SQL, executes Python, and produces a structured analytical summary.
* Answer clarification questions when Kaiya needs more context, either by selecting from suggested options or by typing your own answer directly in the thread.
* Continue conversations naturally inside Slack threads. Kaiya remembers the data source you picked and the prior context across follow-up messages in the same thread.
* Submit 👍 or 👎 feedback on any response to help improve Kaiya's answers over time.
* Click **View in Tellius** on any answer to open the same conversation in the Tellius platform for deeper analysis, dashboard building, or sharing with your team.

{% hint style="warning" %}
To set up the Slack integration, you'll need Tellius admin access and Slack workspace admin permissions. Each Tellius instance connects to one Slack workspace. If you operate multiple Slack workspaces and want the Tellius bot in each, you'll need a separate Tellius instance per workspace.
{% endhint %}

### Admin setup in Tellius

The steps below mirror what you'll see in the product and add helpful context at each stage.

#### Step 1: Open the Integrations settings in Tellius

* Navigate to **Settings → System → Administration → Integrations**, then select the **Slack** tab at the top of the page.
* The **Slack** tab has two parts. **Set up a Slack app** explains the setup; select **Show setup instructions** to open the numbered steps this page follows. Below it, **Slack apps** lists the Slack apps (bots) connected to this deployment, one card per app.
* Select **Add Slack app**. A new card opens with:
  * **App name:** the name this app has in Tellius.
  * **Create Slack app from manifest:** opens Slack's app creator with a manifest pre-filled with your deployment's URLs (Step 2).
  * **Event Request URL:** the address in your deployment that Slack sends this app's events to.
  * **Bot User OAuth Token** and **Signing Secret:** the two values you copy from Slack in Steps 3 and 5.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/33jQ6iBfQ3pMg7oYMM2a/image.png" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://1702728550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC5PhRxmOjkQZJEO6F9Zw%2Fuploads%2FD6UOaQivqslE0nLEys9o%2Fslack-apps-64.png?alt=media&amp;token=75b18eb3-5948-4244-8e51-a8a86d484577" alt="The Slack tab of Settings, Integrations in Tellius 6.4: Set up a Slack app with Show setup instructions, then the Slack apps list with Add Slack app and one card per app showing Edit, Delete, the saved credentials and the Event Request URL" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
In releases before Tellius 6.4, the tab held one panel, **Set up the Tellius Slack bot**, with a single **Bot User OAuth Token** and **Signing Secret** at the bottom of the page. A bot set up that way appears in 6.4 as the **Tellius Slack bot** card.
{% endhint %}

#### Step 2: Pick your workspace and create the bot

* On the new app's card, click **Create Slack app from manifest**. This opens Slack in a new browser tab with the Tellius bot manifest **pre-filled with your deployment's URLs**.
* Select your workspace from the dropdown and click **Next**.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/xT71ft1Qg5e3C3KF487j/image.png" alt="" width="375"><figcaption></figcaption></figure>

* Review the app summary that Slack displays and click **Create**. Slack will create the Tellius bot inside your workspace and redirect you to the app's **Basic Information** page.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/XEzNF3a7IBp0sqDtjWHJ/image.png" alt="" width="375"><figcaption></figcaption></figure>

#### Step 3: Copy the Signing Secret

* You'll land on the **Basic Information** page in Slack. In the **App Credentials** section, find the **Signing Secret** field, and click **Show** to reveal the value. Copy and paste the Signing Secret into the **Signing Secret** field on the app's card in Tellius.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/2WEqhqr5tR0oLUuceDpZ/image.png" alt="" width="563"><figcaption></figcaption></figure>

* While you're on this page, you can optionally scroll down to the **Display Information** section to rename the app to something user-friendly, if required. This is the name your end users will see in Slack.
* Under **App icon**, you can upload your own icon, or click the **⬇ download and use the Kaiya bot icon** link inside the Tellius setup guide to get the official Kaiya bot icon, which you can then upload to Slack. This icon is what appears next to bot messages in Slack — choosing a recognizable icon helps your users identify Tellius responses at a glance.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/847R5Fyd7xHy2qdYCkUb/image.png" alt="" width="375"><figcaption></figcaption></figure>

#### Step 4: Install the bot to your workspace

* In Slack's left sidebar, click **OAuth & Permissions**. Under the **OAuth Tokens** section, click **Install to \[your workspace name]**.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/UyXWymAttt5j9PN5XJyR/image.png" alt="" width="563"><figcaption></figcaption></figure>

* Slack will redirect you to a **Review app permissions** page showing what the Tellius bot will be able to do in your workspace. Click **Allow** after reviewing.
* Slack will install the Tellius bot into your workspace and redirect you back to the **OAuth & Permissions** page.

#### Step 5: Copy the Bot User OAuth Token

* Back on the **OAuth & Permissions** page, you'll now see a **Bot User OAuth Token** under **OAuth Tokens**. It starts with `xoxb-`. Click **Copy** next to it. Paste it into the **Bot User OAuth Token** field on the app's card in Tellius.
* With both the **Signing Secret** and **Bot User OAuth Token** pasted into the card, click **Save** in the top right of the Integrations page. The card closes and shows **✓ Bot token and signing secret saved** with its **Event Request URL**. Your Tellius bot is now configured and ready to use in Slack.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/qszaGLMmxr5E3HCejhNR/image.png" alt="" width="563"><figcaption></figcaption></figure>

### Replacing or removing the Slack app

In Tellius 6.4, each Slack app has its own card:

* **Edit:** opens the card's form again so you can paste a new token or signing secret. Select **Save** at the top of the page to keep the change, or **Done** to close the form.
* **Delete:** removes the app from this deployment. Its stored credentials are deleted when you select **Save**. The Slack app itself isn't deleted; you can still manage or delete it at api.slack.com.

In releases before Tellius 6.4, the page worked as follows. If you click **Create Slack App** when a Tellius Slack app is already configured, Tellius will show a confirmation dialog to prevent you from accidentally creating a duplicate bot in your workspace.

* **Delete existing Slack app →** This link takes you to the existing Slack app in Slack's app management interface, where you can delete it before creating a new one. This is the recommended path if you want to replace the integration cleanly.
* **Create New Slack App** Proceeds anyway and creates a second app in your workspace. Use this only if you specifically need two Tellius bots in the same workspace.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/0RmUyVgQEGeKrNskKMBi/image.png" alt="" width="375"><figcaption></figcaption></figure>

In releases before Tellius 6.4, to disconnect the Tellius integration entirely, you cleared the credential fields and clicked **Save**, then deleted the Slack app from Slack itself.


---

# 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.tellius.com/tellius-6.4/settings/administration/slack-integration.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.