If your team lives in Slack but your data lives in dashboards, you’re probably tired of copy-pasting screenshots or links. Good news: you can plug Metabase right into Slack and get instant updates, charts, and alerts sent to your channels. This guide is for anyone—techie or not—who wants real data sharing, not just more notifications.
Below, I’ll walk you through getting Metabase talking to Slack, what you should actually use this for, what’s a waste of time, and some things to watch out for. Let’s make your data as easy to share as a meme.
Why Connect Metabase and Slack?
Before we dive in, here’s what you’ll really get from connecting Metabase to Slack:
- Push charts and dashboards right into channels—no more “can you send me that report?”
- Schedule regular updates so teams get fresh data when they need it.
- Set up alerts for when something weird happens (like sales dropping or an error spike).
- Share without giving everyone access to Metabase (useful if you don’t want to manage a million logins).
What you won’t get: full dashboard interactivity inside Slack, or perfect formatting every time. Sometimes, a link is still the best option.
Step 1: What You Need Before You Start
Don’t waste time halfway in. Here’s what you’ll need on hand:
- Admin access to both Metabase and your Slack workspace.
- A cloud-hosted or self-hosted Metabase instance (v0.35 or higher; ideally the latest).
- A browser and ~15 minutes.
Pro tip: If you’re not an admin in Slack, find someone who is. You’ll need their help for the Slack app setup.
Step 2: Setting Up the Slack Integration in Metabase
Metabase’s Slack integration is built-in—you just have to turn it on and connect your Slack workspace.
1. Go to Metabase Settings
- Log into Metabase.
- Click on your avatar (top right) → Admin → Settings.
2. Find the Slack Integration
- In the left sidebar, select Slack (sometimes under “Integrations”).
- Click Connect to Slack.
3. Authorize Metabase in Slack
- You’ll be redirected to Slack’s authorization page.
- Pick your Slack workspace.
- Decide who can use the integration (defaults to everyone—tighten this up if you want).
- Click Allow.
You’re done when you see a confirmation in Metabase. If you get an error, double-check your Slack permissions.
Heads up: If your company restricts Slack apps, you may need to request approval. This can take hours, days, or forever, depending on your IT folks.
Step 3: Configure Slack Channels for Sharing
Now that Metabase and Slack are connected, you need to set up where things get sent.
1. Pick Your Channels
- Decide which Slack channels (or DMs) should receive reports or alerts.
- Metabase can only send messages to channels where it’s a member.
2. Add Metabase to Channels
- In Slack, type
/invite @Metabasein each channel you want to use. - If you don’t do this, Metabase can’t post there.
Pro tip: Start with a private test channel so you don’t spam everyone while you’re experimenting.
Step 4: Share Dashboards and Reports to Slack
This is where the magic happens. You can send charts, dashboards, or even query results to Slack, either immediately or on a schedule.
Option 1: Share Instantly
- Open any dashboard or saved question in Metabase.
- Click the Sharing or Send to Slack button (paper airplane or Slack logo).
- Choose the Slack channel or person.
- Add an optional message.
- Click Send.
Option 2: Schedule Regular Updates
- On the dashboard or question, click the clock icon or “Schedule delivery.”
- Pick Slack as the destination.
- Set your schedule (daily, weekly, etc.).
- Choose your channel.
- Save.
Now your team gets updates automatically—nobody has to remember to send them.
Option 3: Set Up Alerts
- On a question, click the bell icon (Alert).
- Pick your condition (e.g., “greater than 100 sales”).
- Choose Slack as the delivery method and pick the channel.
- Save.
Metabase will ping Slack only when your condition is met.
Step 5: Test and Troubleshoot
Don’t assume it’s working—test it!
- Send a quick report to your test channel.
- Make sure formatting looks right (sometimes charts get squished).
- Try scheduling a test update and see if it arrives.
Common issues: - No message arrives: Metabase isn’t in the channel, or Slack permissions are too tight. - Ugly formatting: Some complex charts or tables don’t look great in Slack. If it’s unreadable, just share the link instead. - Delivery delays: Slack API can lag, or Metabase may queue messages if you schedule a lot at once.
Honest Takes: What Works, What Doesn’t
What Works Well
- Quick context: Getting a chart or number in Slack keeps teams focused.
- Scheduled updates: Good for KPIs, sales numbers, or support queues—stuff people need to see daily.
- Simple alerts: Great for “heads up” moments (like when something breaks or hits a goal).
What Doesn’t
- Deep analysis: If you want drill-downs, filters, or live dashboards, Slack’s not the place. Just send the link.
- Heavy reports: Big tables and complex visuals get mangled. Use dashboards, not giant data dumps.
- Too many alerts: Slack fatigue is real. Alert only when it matters.
What to Ignore
- Making Slack a data warehouse: Don’t try to do all your analytics in Slack. It’s for highlights, not homework.
- Over-automation: If nobody reads your automated reports, turn them off or adjust the schedule.
Security and Privacy: Don’t Get Burned
- Sensitive data: Remember, anything sent to Slack is as secure as your Slack workspace. Don’t send PII or confidential stuff unless it’s locked down.
- Channel access: Only add Metabase to channels that actually need reports.
- Audit: Check who’s getting what. It’s easy to overshare in the name of “transparency.”
Updating or Removing the Integration
Things change. Here’s how to tweak or turn off the setup:
- Change channels: Just invite or remove Metabase from Slack channels as needed.
- Disconnect Slack: In Metabase settings, you can remove the Slack integration entirely. This stops all messages instantly.
- Re-authenticate: If you change your Slack permissions, you might need to reconnect Metabase.
Wrapping Up: Keep It Simple
Integrating Metabase with Slack is straightforward, and it’s great for sharing key numbers without extra fuss. But don’t overdo it—start with one or two channels, send only what people actually need, and adjust as you go. The best setups are the ones people use, not the ones with the most bells and whistles. Keep it lean, review what’s helpful, and iterate. If you’re ever in doubt, just ask the team what’s working and what’s noise.
That’s it. Now your data can meet your team where they already are—without one more login or another endless thread of “Hey, can you send me that report?”