.svg)
How to Send Amplitude Reports to Slack Automatically: A Step-by-Step Workflow
Most product and growth teams miss important data shifts simply because insights stay inside Amplitude and never reach the people who need to act on them. Connecting Amplitude to Slack lets you automatically deliver weekly reports, metric alerts, and dashboard summaries directly into your team's workflow without anyone having to log in, pull data, or write a summary. This guide covers the exact steps to set up the workflow, what to automate, and how to make the output actually useful.
The problem with most analytics setups is not the data. It is the distance between the data and the decision.
Your Amplitude dashboards might be perfectly structured. Your metrics might be clean and well-defined. But if your product manager has to remember to log in every Monday, pull the charts, interpret the numbers, and write a summary, that process will break down. People get busy. Dashboards get ignored. Insights that should have driven a decision last Tuesday are discovered three weeks later.
Bringing Amplitude into Slack removes that friction entirely. Instead of insights waiting to be found, they arrive where your team already works.
Here is exactly how to set it up.
What the Amplitude and Slack Integration Actually Does
Before getting into setup, it helps to understand what the integration is and is not.
The Amplitude and Slack integration lets you share charts, dashboards, and alerts directly into Slack channels. You can schedule automated reports to deliver on a set cadence, daily, weekly, or monthly. You can set up metric alerts that fire when a value crosses a threshold. And you can use Amplitude's AI features to generate written summaries that accompany the charts, so your team receives an interpreted insight rather than a raw chart they have to decode themselves.
What it does not do is replace the need for a clean Amplitude setup. The quality of what arrives in Slack is entirely dependent on the quality of what is in Amplitude. If your dashboards are unfocused or your AI context is empty, the automated output will reflect that. The workflow amplifies whatever foundation you have.
Step 1: Connect Amplitude to Your Slack Workspace
Start in Amplitude. Navigate to Settings, then Integrations, and find the Slack integration. Click Connect and follow the OAuth flow to authorize Amplitude to post to your Slack workspace.
You will be asked to select which Slack channels Amplitude is allowed to post to. Be intentional here. Create dedicated channels for analytics reports rather than posting into general or product channels where the reports will get buried in conversation. A channel called #analytics-weekly or #growth-metrics keeps reports visible and searchable without creating noise in your main channels.
Once connected, the integration is available across all dashboards and charts in your Amplitude workspace.
Step 2: Set Up a Scheduled Dashboard Report
Navigate to the dashboard you want to automate. This should be a dashboard structured around a specific business question: weekly conversion performance, feature adoption, retention by cohort. Focused dashboards produce focused reports.
Click the Subscribe option on the dashboard. You will see options to set a delivery schedule, choose the Slack channel, and configure what gets sent. Select your cadence, weekly is the right default for most teams, and choose the day and time that makes sense for your review process. Monday morning before standup is a common choice.
Enable the AI summary option if it is available on your plan. This adds a written interpretation of the dashboard data above the charts, turning a collection of numbers into a narrative that tells your team what changed, what stayed the same, and what is worth paying attention to. This is the step that transforms an automated report from something people scroll past into something people actually read.
The quality of that AI summary depends on how well your AI context is configured in Amplitude. If your summaries are coming out generic, filling in your AI context properly is the fix as it is what tells Amplitude who your users are and what your metrics actually mean.
Step 3: Set Up Metric Alerts for Significant Changes
Scheduled reports tell you what happened on a cadence. Metric alerts tell you the moment something important changes.
In Amplitude, navigate to any chart and click Monitor. You can configure an alert to fire when a metric crosses a threshold you define, conversion rate drops below 3%, daily active users fall more than 10% week over week, a specific event count spikes unexpectedly.
When the condition is met, Amplitude sends a notification directly to the Slack channel you specify. Your team does not have to be watching the dashboard. The dashboard watches itself and tells them when something needs attention.
This is particularly valuable for guardrail metrics, the metrics you need to stay healthy even when you are not actively optimizing them. Set alerts on your most important guardrail metrics and stop relying on someone remembering to check them.
Step 4: Structure Your Slack Channels for Maximum Usefulness
How you organize the incoming reports matters as much as the reports themselves. A few principles that work well in practice.
One channel per audience. A channel for your growth team, a channel for your product team, a separate channel for executive summaries. Each audience needs different metrics at different levels of detail. Mixing them in one channel means everyone gets more noise and less signal.
Pin the weekly report when it arrives. Slack's pin feature keeps the most recent report visible at the top of the channel so it does not get buried as the week goes on.
Use the report as a conversation starter, not a final document. The best use of an automated Amplitude report in Slack is as a prompt for discussion -- someone sees the conversion rate dropped and tags the right person to investigate. The report surfaces the signal. The team provides the judgment.
Combine with Amplitude Chat for follow-up questions. Once the weekly report arrives in Slack, team members can jump into Amplitude's Chat feature to ask follow-up questions directly: "why did conversion drop on mobile last week?"
Step 5: Add the AI Summary Layer
The difference between a useful automated report and one that gets ignored is almost always the narrative layer.
Raw charts require interpretation. A chart showing that conversion dropped from 4.2% to 3.8% tells you something changed. It does not tell you whether that is within normal variance, whether it affected a specific segment, or whether it warrants action this week. An AI-generated summary that says "conversion rate dropped 9.5% week over week, driven primarily by mobile users in the checkout step, consistent with the pattern seen during the last product release" is something a team can act on immediately.
Setting this up properly requires two things. First, your dashboards need to be structured around specific business questions with well-labeled charts. Second, your Amplitude AI context needs to be filled in accurately at both the organization and project level. Dashboard Agents are what generate this narrative output, they read every chart on the dashboard and produce the written summary that accompanies the report in Slack.
Without the AI context, the summaries are generic. With it, they are specific to your business, your users, and the decisions your team is actually trying to make.
What a Good Weekly Slack Report Workflow Looks Like
With everything in place, a realistic weekly analytics workflow looks like this.
On Monday morning, the scheduled Amplitude report arrives in your dedicated Slack channel. It includes the key charts from your dashboard alongside an AI-generated summary of what changed in the past week. A team member reviews the summary, adds a quick interpretation or flags anything that needs follow-up, and the report becomes a pinned artifact for the week.
Anyone on the team can react, comment, or tag someone based on what the report shows. Follow-up questions go into Amplitude Chat. Actions get created in your project management tool. The whole process takes fifteen minutes instead of two hours.
Is your Amplitude setup ready to automate?
Automated reports are only as good as the foundation underneath them. If you want to make sure your events, dashboards, and AI context are set up correctly before you automate anything, the AI Readiness package covers exactly that.
Explore the AI Readiness package
Want to talk through your analytics workflow?
Book a 30-minute call with Gregor
FAQ
Can Amplitude send reports to Slack automatically?
Yes. Amplitude's Slack integration lets you schedule dashboard reports to deliver on a daily, weekly, or monthly cadence. You can also configure metric alerts that fire automatically when a value crosses a threshold, sending a notification to any Slack channel you specify.
What does the Amplitude and Slack integration include?
The integration lets you share individual charts and full dashboards to Slack channels, schedule automated recurring reports, set up threshold-based metric alerts, and include AI-generated summaries alongside the charts when sending dashboard reports.
Do I need a paid Amplitude plan for Slack integration?
The Slack integration is available on Amplitude's paid plans. Specific features -- including AI summaries and advanced alert configuration -- may vary by contract tier. Check your current Amplitude plan or contact Amplitude directly to confirm what is included.
Why is my Amplitude AI summary in Slack too generic?
Generic summaries almost always come from missing or incomplete AI context in Amplitude. Navigate to your organization and project settings in Amplitude, find the AI Context fields, and fill them in with specific information about your business model, users, and key metrics. This is what makes the automated summaries specific and actionable rather than generic descriptions of chart shapes.
How do I set up metric alerts in Amplitude to send to Slack?
Navigate to any chart in Amplitude and click the Monitor option. Configure the alert condition -- a threshold value, a percentage change, or an anomaly detection trigger -- and select the Slack channel where the notification should be delivered. The alert fires automatically when the condition is met, without any manual monitoring required.
What is the best Slack channel structure for Amplitude reports?
Create dedicated channels per audience rather than posting all reports into a single channel. A growth team channel, a product team channel, and an executive summary channel each receive reports tailored to what that audience needs. Pin the weekly report when it arrives to keep it visible throughout the week.
.png)
