docs: add Slack integration page

[keydunov]

Cover notifications delivery and Slack Agent features, including setup, user matching, and current limitations.

Made-with: Cursor

Check List

• Tests have been run in packages where changes have been made if available
• Linter has been run for changed code
• Tests for the changes have been added if not covered yet
• Docs have been added / updated if required

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
cubed3	🔴 Failed	–	Apr 12, 2026, 11:52 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[claude]

Claude finished @keydunov's task in 1m 52s —— View job

---

Review: docs: add Slack integration page

• Gather context and read changed files
• Review documentation content and structure
• Review navigation configuration changes
• Check for Mintlify preview failure cause
• Post review feedback

---

Overall: This is a clean, well-structured documentation page. The content covers the two Slack capabilities (Notifications and Slack Agent) clearly, with good use of Mintlify components (<Info>, <Warning>, <Frame>) and reference-style links. The structure (Setup → Notifications → Slack Agent → How it works → User matching → Limitations) follows a logical flow.

Observations

Navigation placement (docs-mintlify/docs.json): Slack is placed as the first item under Integrations, which makes sense given it's a high-visibility feature.

Reference links are consistent: The ref-scheduled-refreshes link uses /analytics/scheduled-refreshes, which matches the same pattern used in the notifications page. The ref-analytics-chat and ref-notifications links use /docs/explore-analyze/... paths, consistent with other integration pages.

Image hosting: Uses Uploadcare CDN (ucarecd.net), which is the standard pattern across the docs site.

Suggestions (non-blocking)

1. Image alt text (slack.mdx:32, 56): The two <img> tags lack alt attributes. While this is consistent with other integration pages, adding descriptive alt text (e.g., alt="Slack integration settings page") would improve accessibility. This is a pre-existing pattern across the docs, so not specific to this PR.

2. Mintlify preview failure: The Mintlify preview deployment failed. Since the PR only adds one navigation entry and one new page, the failure may be unrelated to this PR's changes (e.g., a transient Mintlify issue or a pre-existing config problem). Worth verifying the preview works post-merge.

Summary

Clean docs PR. The content is accurate, well-organized, and follows the existing patterns in the docs site. The Limitations section with the <Warning> component is a nice touch for managing user expectations around a feature in active development. No blocking issues found.