Pendo + Slack
Connect Pendo and Slack to Turn Product Insights into Instant Team Action
Bring real-time user behavior, NPS scores, and feature adoption data from Pendo directly into the Slack channels where your team makes decisions.
Why integrate Pendo and Slack?
Pendo captures product analytics, in-app guides, and user feedback that product, success, and engineering teams rely on to improve digital experiences. Slack is where those same teams collaborate, escalate issues, and coordinate responses. Connecting Pendo to Slack closes the gap between insight and action by getting the right data to the right people the moment it matters.
Automate & integrate Pendo & Slack
Use case
NPS Response Alerts in Slack
When a user submits an NPS survey response inside your product via Pendo, tray.ai instantly posts the score and verbatim comment to a dedicated Slack channel. Low scores get routed to a customer success channel for immediate follow-up, while promoter scores go to marketing to capture advocacy opportunities.
Use case
Feature Adoption Drop Notifications
Configure Pendo to track feature usage thresholds and trigger a tray.ai workflow when adoption falls below a defined benchmark. The workflow posts a structured Slack alert to the product channel, including the feature name, current adoption rate, and a direct link to the Pendo analytics report for immediate investigation.
Use case
New Account Onboarding Milestone Updates
When a new account completes onboarding steps tracked by Pendo guides — finishing setup flows or activating core features — tray.ai posts a milestone update to a shared Slack channel monitored by sales, success, and product teams. Everyone stays aligned on customer health from day one.
Use case
In-App Feedback Digest Delivered to Slack
Aggregate qualitative feedback collected through Pendo feedback modules on a schedule and deliver a summarized digest to a product Slack channel daily or weekly. tray.ai compiles top feedback themes, request volumes, and sentiment trends so product managers start every day with a clear picture of what users are asking for.
Use case
Churn Risk Account Escalations
When Pendo health scores or engagement metrics for a tracked account fall into a predefined risk range, tray.ai triggers a Slack message to the account owner and their manager. The alert includes usage trends, last active date, and guide completion rates so the team can act with full context rather than scrambling for data.
Use case
Guide Performance Reporting to Product Channels
Track the performance of Pendo in-app guides — view rates, completion rates, and dismissal rates — and push automated performance summaries to a Slack channel after a guide has been live for a configurable period. Product and UX teams get fast feedback on guide effectiveness without pulling manual reports.
Use case
Cross-Team Usage Anomaly Alerts
When Pendo detects an unusual spike or drop in session volume, page views, or critical workflow completions, tray.ai notifies engineering, product, and operations teams via Slack. Early warning helps teams figure out whether the cause is a deployment issue, a UX problem, or something external before users churn.
Get started with Pendo & Slack integration today
Pendo & Slack Challenges
What challenges are there when working with Pendo & Slack and how will using Tray.ai help?
Challenge
Translating Pendo Webhook Payloads into Readable Slack Messages
Pendo webhook payloads contain nested JSON with internal IDs, numeric scores, and metadata that aren't human-readable in their raw form. Posting raw payloads to Slack creates noise rather than clarity, and non-technical team members won't know what to do with them.
How Tray.ai Can Help:
tray.ai's data transformation tools let teams map Pendo payload fields to clean, readable values — replacing account IDs with account names, formatting scores, and building structured Slack Block Kit messages that include only the context each team actually needs.
Challenge
Routing Alerts to the Right Slack Channel and Person
Different Pendo events matter to different teams. An NPS response from an enterprise account should reach the enterprise CSM; a feature adoption drop should go to the product owner for that area. Without smart routing logic, alerts flood a single channel and lose their urgency fast.
How Tray.ai Can Help:
tray.ai supports conditional branching so each workflow evaluates account tier, event type, feature area, or team ownership before deciding which Slack channel to post to — and whether to send a direct message to a specific person — keeping signal-to-noise ratios high across all channels.
Challenge
Avoiding Alert Fatigue from High-Volume Pendo Events
Pendo can generate a lot of events — especially for guide views, page visits, and feedback submissions — and routing every one to Slack would quickly overwhelm your channels. When that happens, teams mute channels and start missing the alerts that actually need attention.
How Tray.ai Can Help:
tray.ai supports rate limiting, deduplication logic, and scheduled digest patterns so teams can choose real-time alerts for high-priority events and batched summaries for high-volume, lower-priority signals, keeping Slack channels focused and actionable.
Challenge
Keeping Pendo Segment and Account Data in Sync with Slack Context
Pendo events reference internal segment names and account identifiers that may not match the naming conventions used by customer success or sales teams in Slack. When the names don't match, teams lose time trying to connect an alert to a real customer relationship.
How Tray.ai Can Help:
tray.ai can enrich Pendo event data mid-workflow by looking up additional context from a CRM or customer database, translating internal Pendo identifiers into the account names and owner information that Slack recipients recognize and can act on immediately.
Challenge
Managing Workflow Maintenance as Pendo Guides and Metrics Evolve
Product teams regularly launch new Pendo guides, retire old ones, and adjust tracked metrics as the product changes. Hardcoded integrations break silently when guide IDs or metric names shift, creating gaps in Slack notifications that teams may not notice for days or weeks.
How Tray.ai Can Help:
tray.ai's visual workflow builder makes it straightforward for non-engineers to update trigger conditions, add new guide IDs, or modify Slack message templates without touching code. Teams can maintain their Pendo-to-Slack automations as their product analytics strategy evolves, no developer required.
Start using our pre-built Pendo & Slack templates today
Start from scratch or use one of our pre-built Pendo & Slack templates to quickly solve your most common use cases.
Pendo & Slack Templates
Find pre-built Pendo & Slack solutions for common use cases
Template
Pendo NPS Detractor to Slack CSM Alert
Automatically monitors Pendo for new NPS survey submissions, filters for detractor scores (0–6), and posts a formatted alert — including the score, user segment, account name, and verbatim response — to a customer success Slack channel so the responsible CSM can follow up within the hour.
Steps:
- Trigger: New NPS response event received from Pendo via webhook or polling
- Filter: Check if score is in the detractor range (0–6)
- Action: Format and post a rich Slack message to the #customer-success channel with score, account, and feedback text
Connectors Used: Pendo, Slack
Template
Weekly Pendo Feature Adoption Digest to Slack
Runs on a weekly schedule to query Pendo for feature adoption metrics across defined segments, formats a ranked digest of top and bottom performing features, and posts the report to a product team Slack channel every Monday morning to inform sprint planning and prioritization discussions.
Steps:
- Trigger: Scheduled workflow fires every Monday at 8 AM in the product team's timezone
- Action: Query Pendo API for feature adoption rates across key user segments for the previous week
- Action: Format ranked adoption digest and post to #product-team Slack channel with feature names, rates, and week-over-week change
Connectors Used: Pendo, Slack
Template
Pendo Churn Risk Score Alert to Slack Account Owner
Monitors Pendo account health data and triggers when an account's engagement score drops below a configurable threshold, sending a direct Slack message to the assigned account owner and posting a summary in the #at-risk-accounts channel with current usage metrics and recommended next steps.
Steps:
- Trigger: Pendo account health score or engagement metric crosses a defined risk threshold
- Lookup: Identify the assigned CSM or account owner from account metadata
- Action: Send a direct Slack DM to the account owner and a parallel post to #at-risk-accounts with usage context
Connectors Used: Pendo, Slack
Template
Pendo Onboarding Milestone Completion to Slack Team Update
Listens for Pendo guide completion events tied to onboarding flows and posts a milestone update to a shared Slack channel when a new account completes each defined stage, keeping sales, success, and product teams in sync on customer activation progress.
Steps:
- Trigger: Pendo guide completion event fires for a tracked onboarding guide
- Enrich: Map guide name to a human-readable milestone label and retrieve account details
- Action: Post a milestone update message to #customer-onboarding Slack channel with account name, milestone reached, and completion timestamp
Connectors Used: Pendo, Slack
Template
Pendo In-App Feedback to Slack Product Backlog Channel
Captures new feedback submissions from the Pendo feedback module in real time and posts each item to a dedicated Slack channel where product managers can react, comment, and tag backlog items directly. It's a continuous feedback inbox inside Slack, no manual Pendo logins required.
Steps:
- Trigger: New feedback item submitted through Pendo feedback module
- Transform: Extract title, description, submitting user, and account from Pendo payload
- Action: Post formatted feedback card to #product-feedback Slack channel with user context and a link back to the Pendo feedback record
Connectors Used: Pendo, Slack
Template
Pendo Usage Anomaly to Slack Engineering and Product Alert
Detects significant deviations in product usage metrics tracked in Pendo — such as a 20% or greater drop in core workflow completions — and sends alert messages to both an engineering Slack channel and a product Slack channel, so both teams can investigate in parallel.
Steps:
- Trigger: Pendo metric crosses a configured anomaly threshold via webhook or scheduled metric check
- Evaluate: Determine anomaly type and severity to select the correct routing logic
- Action: Post parallel Slack alerts to #engineering-alerts and #product-alerts channels with metric name, current value, expected range, and a Pendo report deep link
Connectors Used: Pendo, Slack