Skip to content

Commit 3270d0b

Browse files
authored
docs: add Slack integration page (cube-js#10676)
Cover notifications delivery and Slack Agent features, including setup, user matching, and current limitations. Made-with: Cursor
1 parent ad659b1 commit 3270d0b

2 files changed

Lines changed: 89 additions & 0 deletions

File tree

docs-mintlify/docs.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -141,6 +141,7 @@
141141
{
142142
"group": "Integrations",
143143
"pages": [
144+
"docs/integrations/slack",
144145
"docs/integrations/tableau",
145146
{
146147
"group": "Power BI",
Lines changed: 88 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,88 @@
1+
---
2+
title: Slack
3+
description: Connect Cube to Slack for notifications and AI-powered analytics chat.
4+
---
5+
6+
<Info>
7+
8+
Available on [Premium and above plans](https://cube.dev/pricing).
9+
10+
</Info>
11+
12+
Cube's Slack integration enables two capabilities:
13+
14+
- **[Notifications](#notifications)** — Deliver scheduled dashboard screenshots
15+
to Slack channels.
16+
- **[Slack Agent](#slack-agent)** — Let your team ask data questions directly in
17+
Slack and get AI-powered answers from the
18+
[Analytics Chat][ref-analytics-chat] agent.
19+
20+
## Setup
21+
22+
A workspace admin connects Slack from the **Settings → Integrations → Slack**
23+
page. The setup flow authorizes Cube to interact with your Slack workspace via
24+
OAuth.
25+
26+
Once connected, the admin selects:
27+
28+
- A **deployment** that the Slack integration will use.
29+
- An **agent** that will respond to questions in Slack.
30+
31+
<Frame>
32+
<img src="https://lgo0ecceic.ucarecd.net/adde089b-454b-4c7d-ad1b-0fbb930963ea/" />
33+
</Frame>
34+
35+
## Notifications
36+
37+
Slack notifications post a dashboard screenshot to a Slack channel after each
38+
[scheduled refresh][ref-scheduled-refreshes]. See [Notifications][ref-notifications]
39+
for details on creating and configuring notification schedules.
40+
41+
## Slack Agent
42+
43+
The Slack Agent brings [Analytics Chat][ref-analytics-chat] into Slack.
44+
Anyone in your Slack workspace can send a direct message to the Cube app and
45+
get AI-powered answers grounded in your semantic layer — without leaving Slack.
46+
47+
### How it works
48+
49+
1. A user sends a direct message to the Cube Slack app.
50+
2. Cube matches the user by **email address** — the email in Slack must match
51+
an existing Cube user.
52+
3. An [Analytics Chat][ref-analytics-chat] session is created, and the agent
53+
responds in a **Slack thread**.
54+
55+
<Frame>
56+
<img src="https://lgo0ecceic.ucarecd.net/bf19e3bf-98fd-4f6d-9db5-964696280cf3/" />
57+
</Frame>
58+
59+
Follow-up questions can be asked by replying in the same Slack thread, keeping
60+
the conversation contextual.
61+
62+
### User matching
63+
64+
Cube identifies Slack users by their email address. For the integration to work,
65+
a user with the **same email** must exist in both Cube and the connected Slack
66+
workspace. If no matching Cube user is found, the agent will not respond.
67+
68+
### Limitations
69+
70+
<Warning>
71+
72+
Slack Agent is in active development. The following limitations apply:
73+
74+
- **DMs only** — The Slack Agent currently works only in direct messages with
75+
the Cube app. Channel mentions are not supported.
76+
- **One agent** — Only one agent can be active at a time. Admins can change the
77+
selected agent in the Slack integration settings.
78+
- **One-way message sync** — Chats initiated from Slack are visible in the Cube
79+
UI, and you can post messages from the Cube UI, but those messages will not
80+
appear in the corresponding Slack thread.
81+
- **Email matching required** — Users must have the same email address in both
82+
Cube and Slack.
83+
84+
</Warning>
85+
86+
[ref-analytics-chat]: /docs/explore-analyze/analytics-chat
87+
[ref-notifications]: /docs/explore-analyze/notifications
88+
[ref-scheduled-refreshes]: /analytics/scheduled-refreshes

0 commit comments

Comments
 (0)