# Amplitude Dashboard + Slack integration > Automatically push product metrics, behavioral trends, and user insights to the Slack channels where your team already works. **Canonical page:** https://tray.ai/connectors/amplitude-dashboard-slack-integrations/ **Amplitude Dashboard connector:** https://tray.ai/connectors/amplitude-dashboard-integrations/ **Amplitude Dashboard documentation:** https://tray.ai/documentation/connectors/service/amplitude-dashboard **Slack connector:** https://tray.ai/connectors/slack-integrations/ **Slack documentation:** https://tray.ai/documentation/connectors/service/slack ## Overview Amplitude Dashboard and Slack are two of the most-used tools in a modern product team's stack — one tracks how users interact with your product, the other is where your team communicates and makes decisions. Integrating the two closes the gap between insight and action: metric changes, funnel drops, and behavior anomalies become immediately visible to the people who can do something about them. No more waiting for weekly reports or manually checking dashboards. Product teams live in Slack, but their most important data lives in Amplitude. Without an integration, engineers, product managers, and growth teams have to context-switch constantly — pulling up dashboards, exporting charts, pasting screenshots into channels just to share a single data point. That manual process introduces delays, inconsistency, and the real risk that something important goes unnoticed. Connecting Amplitude to Slack via tray.ai means your team can define threshold-based alerts, schedule daily metric digests, and automatically notify stakeholders when KPIs move. Whether you're tracking retention curves, activation funnels, or feature adoption, your whole organization stays aligned on product performance without leaving Slack. ## Use cases ### Threshold-Based Metric Alerts Automatically post a Slack message to a designated channel whenever an Amplitude metric crosses a defined threshold — DAU dropping below a target, say, or conversion rate falling more than 10% week-over-week. Teams can configure alerts per chart or dashboard segment so the right people are notified without the noise. That means a faster response before a dip becomes a crisis. - Catch metric regressions within minutes, not days - Route alerts to the correct team channel based on metric type - Reduce reliance on manual dashboard monitoring ### Scheduled Daily or Weekly Analytics Digests Send a formatted Slack digest every morning or at the start of each week summarizing Amplitude metrics like active users, session counts, feature engagement, and retention rates. Leadership, product, and engineering teams stay aligned on performance without anyone having to log into Amplitude. Digests can be customized per team with the metrics most relevant to their work. - Every stakeholder starts the day with current product health data - Reduce time spent creating and distributing manual reports - Give non-technical teams a reliable window into product data ### Feature Release Performance Monitoring When a new feature ships, automatically start posting Amplitude engagement and adoption metrics for that feature into a dedicated Slack channel for the launch team. Engineers, product managers, and designers can watch real-time adoption and catch issues early. Everyone shares the same source of truth during the post-release window. - Tighten post-launch feedback loops for product teams - Spot adoption problems before they compound - Keep cross-functional launch teams informed without extra meetings ### Funnel Drop-Off Notifications Monitor conversion funnels in Amplitude and trigger a Slack alert whenever drop-off at a specific step exceeds a set tolerance. The notification includes the step name, current drop-off percentage, and a direct link to the Amplitude chart so investigation can start immediately. Growth and product teams can respond to UX friction as it happens. - Catch funnel degradations before they cost revenue - Link directly to Amplitude charts so engineers can diagnose fast - Assign ownership of funnel issues directly within the Slack alert thread ### Cohort and Retention Milestone Notifications Automatically notify the product team in Slack when a user cohort hits a retention milestone — like a new cohort achieving 30-day retention above the historical average. Positive signals matter as much as negative ones; they tell you what's actually working. Cohort alerts can also fire when retention drops below acceptable thresholds. - Celebrate wins and reinforce data-driven product decisions - Get early warning on retention drops before they affect revenue - Tie retention trends to recent product changes for faster attribution ### A/B Test Results Delivery When an experiment tracked in Amplitude reaches statistical significance or a scheduled review point, automatically push the results summary to a Slack channel with variant metrics, confidence levels, and a link to the full Amplitude report. Analysts don't have to manually compile and share results, so decisions on feature rollouts move faster. - Speed up experiment decision cycles across product and engineering - Get results to all relevant stakeholders at the same time - Reduce analyst time spent packaging and distributing test results ### User Segment Behavior Alerts for Customer Success Detect when a specific high-value user segment in Amplitude shows a behavioral change — a drop in engagement from enterprise accounts, for instance — and automatically notify the Customer Success team in Slack. CSMs can intervene before churn risk escalates. Alerts can include segment size, the affected behavioral metric, and a suggested action. - Give Customer Success proactive data rather than reactive reports - Reduce churn by identifying at-risk enterprise segments early - Connect product analytics directly to customer-facing teams ## Templates ### Daily Amplitude Metrics Digest to Slack This template runs on a scheduled trigger each morning, pulls a defined set of metrics from Amplitude Dashboard, formats them into a clean Slack Block Kit message, and posts the digest to a specified channel. Teams can configure which metrics to include and set different channels for different teams. Connectors used: Amplitude Dashboard, Slack ### Amplitude Metric Threshold Alert to Slack Monitors an Amplitude metric on a recurring schedule and compares the current value against a configured threshold. When the value breaches the threshold, a formatted Slack alert goes to the relevant channel with the metric name, current value, threshold, and a link to the Amplitude chart. Connectors used: Amplitude Dashboard, Slack ### Feature Adoption Tracker Post-Deployment Triggered when a deployment event or feature flag activation is detected, this template starts polling Amplitude for engagement data on the newly released feature and posts a running summary to a dedicated Slack launch channel at configurable intervals. Connectors used: Amplitude Dashboard, Slack ### Funnel Drop-Off Alert to Slack Regularly checks a defined conversion funnel in Amplitude and sends an immediate Slack notification to the growth or product team channel if any funnel step's drop-off rate exceeds the configured tolerance, with the specific step, current rate, and historical baseline for context. Connectors used: Amplitude Dashboard, Slack ### Weekly A/B Test Results Summary to Slack On a weekly cadence, this template retrieves experiment data from Amplitude, identifies any tests that have reached significance or their review date, and posts a structured results summary to the product team's Slack channel so decisions can be made without manual analyst involvement. Connectors used: Amplitude Dashboard, Slack ### High-Value Segment Engagement Drop Alert to Customer Success Slack Monitors engagement metrics for a defined high-value user segment in Amplitude and sends a proactive Slack alert to the Customer Success team channel when engagement falls below a threshold, giving CSMs the data they need to step in before accounts churn. Connectors used: Amplitude Dashboard, Slack ## Challenges Tray.ai solves ### Translating Raw Amplitude Data Into Readable Slack Messages Amplitude API responses return complex, nested JSON with chart data, event properties, and segmentation breakdowns that aren't readable in a Slack message. Forwarding raw API output creates noisy, unreadable notifications that teams learn to ignore fast. **How Tray.ai helps:** tray.ai's built-in data transformation tools let you map, reshape, and format Amplitude API responses into clean Slack Block Kit messages. Pull exactly the fields you need, calculate deltas or percentages inline, and build rich notification cards with contextual links. No custom parsing code required. ### Managing Alert Fatigue From High-Frequency Metric Polling Poll Amplitude too often or set overly sensitive thresholds and you'll flood Slack channels with alerts until teams stop reading them entirely. Getting the balance right between timely signals and notification noise is something product and data teams wrestle with constantly. **How Tray.ai helps:** tray.ai workflows support conditional logic, cooldown periods, and stateful tracking so you can suppress duplicate alerts within a defined window, require a threshold to be breached across multiple consecutive checks before alerting, and route different severity levels to different Slack channels. You get precise control over frequency and relevance. ### Keeping Amplitude Chart Links and Dashboard References Current Amplitude dashboards and charts get reorganized, renamed, and archived as product priorities shift. Hard-coded chart URLs in Slack notifications go stale quickly, leaving team members with broken links when they're trying to investigate an alert. **How Tray.ai helps:** tray.ai lets you store Amplitude chart and dashboard IDs as configurable workflow variables instead of hard-coded strings. Update a single variable in tray.ai and the change carries through every workflow that references that chart, so Slack notifications always point to the right place. ### Handling Amplitude API Rate Limits at Scale When multiple workflows are polling Amplitude simultaneously across different teams, metrics, and schedules, it's easy to hit Amplitude's API rate limits. Workflows fail silently and Slack notifications stop arriving with no obvious sign of what went wrong. **How Tray.ai helps:** tray.ai has built-in rate limit handling and retry logic for the Amplitude connector, automatically queuing and spacing API requests to stay within Amplitude's limits. Error handling steps can also post a Slack notification to an ops channel when a rate limit error is hit, so the team knows about any data gaps. ### Routing Alerts to the Right Slack Channels and Teams As integration usage grows, product, engineering, growth, customer success, and leadership all want Amplitude data delivered to their own Slack channels with metrics relevant to their work. Managing that routing logic manually across separate tools gets messy and error-prone fast. **How Tray.ai helps:** tray.ai's workflow branching and lookup table capabilities let you build a single Amplitude monitoring workflow that dynamically routes alerts to different Slack channels based on metric type, team ownership, or severity. Adding a new routing rule doesn't mean rebuilding the whole workflow from scratch. ## Learn more - Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/ - Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/ - Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/ - Book a demo: https://tray.ai/contact/