TVL Managed Superset
Get started

Integrate Apache Superset with Slack 2026

Integrate Apache Superset with Slack: alerts, scheduled reports, /superset commands, bot. Step-by-step.

· Tuvalu Tech OÜ

Integrating Apache Superset with Slack allows teams to receive alerts, reports, and summaries directly in their channels. This guide details integration options in 2026, from simple webhook to advanced bot.

1. Three Slack integration levels

LevelEffortCapabilities
Simple webhook15 minText notifications
Slack App + bot token1hAlerts + reports with attachments
Custom bot1-2 days/superset commands, interactive queries

If you want preconfigured Slack integration, TVL Managed Superset offers a Slack wizard on Pro+ instances.

2. Level 1 — Simple webhook

  1. Slack workspace → Apps → Incoming Webhooks;
  2. Create a webhook for the #alerts-data channel;
  3. Copy the URL;
  4. In Superset, create an alert with "URL" notification;
  5. Paste the Slack URL.

3. Level 2 — Slack App + bot token

For richer notifications (with attached PNG):

  1. api.slack.com/apps → Create App from scratch;
  2. OAuth & Permissions → bot scopes: chat:write, files:write, chat:write.public;
  3. Install to workspace;
  4. Copy the Bot User OAuth Token (starts with xoxb-);
  5. In Superset config:
SLACK_API_TOKEN = os.environ["SLACK_API_TOKEN"]

Now, when creating an alert or report, choose Slack as method and enter the channel #alerts-data.

4. Slack message format

Superset sends a Slack Block Kit payload with:

  • Alert or report title;
  • Description;
  • Link to the dashboard;
  • PNG image (if Chrome headless configured);
  • Timestamp.

5. Level 3 — Interactive custom bot

For /superset commands directly in Slack:

  1. Create a Slack App with Slash Commands;
  2. Custom endpoint (Lambda, Cloud Run) that calls the Superset API;
  3. Example: /superset top-customers returns an embedded chart.

This configuration is applied by default on TVL Managed Superset, which follows community best practices.

6. Typical use cases

  • Real-time alert: churn spike → ping CS team Slack;
  • Weekly report: Monday morning MRR in #leadership;
  • Incidents: HTTP error rate > 1% → #ops-alerts;
  • Sales wins: deal closed-won → #sales-wins;
  • Daily quiz: top 3 SKUs sold at 9am in #ecommerce.

7. Best practices

  • One channel per team, not a catch-all channel;
  • Criticality level: warning vs critical, route differently;
  • Throttling: no more than 5 alerts/hour, otherwise spam;
  • Direct link to Superset dashboard in each message;
  • Annual rotation of bot token.

8. Alternatives to Slack

Apache Superset also supports:

  • Microsoft Teams via webhook (cf. Teams integration);
  • Discord via webhook;
  • Classic email;
  • PagerDuty via webhook;
  • Custom webhook for proprietary integrations.

9. Common pitfalls

  • Bot not invited to channel: message refused, check chat:write.public;
  • Expired token: Slack invalidates bot tokens if app is uninstalled;
  • Missing image: Chrome headless not configured in worker;
  • Badly rendered Markdown: Slack uses mrkdwn, not standard Markdown;
  • Slack rate limit: 1 message/second per channel.

10. Conclusion

Slack integration transforms Apache Superset into a proactive notification system. A well-configured Slack alert channel can avoid major business incidents by alerting the right people with the right data. It's an investment of a few hours that pays off immediately.

Want the benefits of Apache Superset without the friction of installation and maintenance? Deploy your instance in 3 clicks with TVL Managed Superset, hosted in Europe (OVHcloud, Roubaix, France).

For more: Superset alerts, scheduled reports, Teams integration.