LaunchDarkly + Slack
Connect LaunchDarkly and Slack to Keep Your Team Informed on Feature Flags
Automate feature flag alerts, rollout notifications, and incident escalations directly in Slack so your engineering and product teams never miss a change that matters.
Why integrate LaunchDarkly and Slack?
LaunchDarkly and Slack are two tools that sit at the center of modern software delivery — one controls what features your users see, and the other is where your team communicates and makes decisions. When a feature flag is toggled, a rollout percentage changes, or an experiment completes, the people who need to know are almost certainly in Slack. Integrating LaunchDarkly with Slack closes the gap between flag activity and team awareness, turning silent configuration changes into visible, actionable events.
Automate & integrate LaunchDarkly & Slack
Use case
Real-Time Feature Flag Change Notifications
Whenever a feature flag is created, modified, or toggled in LaunchDarkly, a formatted Slack message is automatically posted to the relevant engineering or product channel. The notification includes the flag name, environment, who made the change, and a direct link to the flag in LaunchDarkly. Teams get instant visibility without polling the LaunchDarkly dashboard or relying on word of mouth.
Use case
Incident Response and Kill Switch Alerts
When a kill switch flag is triggered — typically during a production incident or unexpected degradation — an urgent Slack alert fires to the on-call channel, tagging the incident responders. When engineers are racing to fix an issue, the entire response team immediately knows a flag has been flipped to disable a feature. The alert can include environment details, flag targeting scope, and a timestamp.
Use case
Gradual Rollout Progress Updates
As a feature flag's rollout percentage climbs from 5% to 25% to 50% to 100%, automated Slack updates keep stakeholders informed of progress. Product managers, customer success, and support teams can follow along in a dedicated release channel without needing access to LaunchDarkly. Each update can include the current rollout percentage, environment, and a link to monitoring dashboards.
Use case
Flag Staleness and Cleanup Reminders
Flags that have been fully rolled out or are no longer serving a purpose accumulate as technical debt. This integration can detect flags that haven't been modified within a defined window and post a Slack reminder to the owning team, prompting cleanup. Engineers are notified in context, with a direct link to the flag, making it easy to act immediately.
Use case
Experiment and A/B Test Completion Alerts
When a LaunchDarkly experiment reaches statistical significance or a defined end date, a Slack notification goes out to the product and data teams summarizing the outcome. No more manual monitoring or waiting on someone to remember to check a dashboard before a product decision can move forward.
Use case
Approval Workflow Requests via Slack
When a team member submits a flag change request that requires approval in LaunchDarkly, a Slack message goes to the designated approver with full context on the requested change. The approver clicks through to LaunchDarkly to approve or reject without hunting for the pending request. Approval workflows keep moving without blocking engineering.
Use case
Environment-Specific Flag Monitoring for QA and Staging
QA and staging environments often have flags toggled independently of production, and testers need to know exactly which flags are active in the environment they're testing. This integration posts Slack notifications to a QA-specific channel whenever a flag changes in staging or QA, so testers always have an accurate picture of the current flag state without switching tools.
Get started with LaunchDarkly & Slack integration today
LaunchDarkly & Slack Challenges
What challenges are there when working with LaunchDarkly & Slack and how will using Tray.ai help?
Challenge
Routing Flag Notifications to the Right Slack Channels
LaunchDarkly projects can span dozens of teams, and a single notification channel for all flag changes quickly becomes noise. Engineering teams need flag change alerts to reach the specific Slack channel relevant to each product area, project, or environment — but mapping flags to channels dynamically requires custom logic that isn't trivial to build or maintain.
How Tray.ai Can Help:
tray.ai's conditional logic and data transformation capabilities let you inspect a flag's project key, tags, or environment within the workflow and route each notification to the appropriate Slack channel dynamically, without hardcoding routing rules or maintaining a separate lookup service.
Challenge
Handling High-Volume Flag Change Events Without Noise
Active engineering teams can trigger dozens of flag changes per day across multiple environments. Posting every change directly to Slack without filtering or batching creates notification fatigue, and teams start tuning out alerts — including the ones that actually need attention.
How Tray.ai Can Help:
tray.ai lets you build filtering logic that suppresses low-priority changes (such as flag edits in development environments) and batches non-urgent notifications into digest-style Slack messages, so only actionable changes generate real-time alerts.
Challenge
Resolving LaunchDarkly Users to Slack Identities
LaunchDarkly records the email address or member ID of the user who made a flag change, but Slack requires a user ID or handle to properly mention someone in a notification. Without a resolution step, notifications can't tag the responsible team member or route to their direct messages.
How Tray.ai Can Help:
tray.ai workflows can include a Slack API lookup step that resolves an email address to a Slack user ID mid-workflow, enabling proper user mentions in flag change notifications and approval alerts without a separate identity mapping system.
Challenge
Authenticating and Managing Webhooks Across Multiple LaunchDarkly Environments
LaunchDarkly environments — production, staging, QA, and others — each require their own webhook configuration to fire events independently. Managing webhook setup, secret validation, and payload differences across environments manually is error-prone and gets harder to maintain as projects scale.
How Tray.ai Can Help:
tray.ai provides a single webhook receiver that can accept and differentiate payloads from multiple LaunchDarkly environments using header validation and payload parsing, removing the need for separate workflow instances per environment and centralizing secret management.
Challenge
Keeping Approval Workflows Moving Across Time Zones
When LaunchDarkly flag approval requests go to approvers in different time zones or with variable Slack availability, requests can sit unreviewed for hours, blocking deployments and frustrating engineers who need to move quickly. There's no built-in escalation mechanism in the standard notification flow.
How Tray.ai Can Help:
tray.ai lets you build escalation logic directly into approval notification workflows: if an approver doesn't respond within a configurable window, the workflow automatically sends a follow-up Slack reminder, escalates to a secondary approver, or posts to a management channel — keeping the release process moving without manual follow-up.
Start using our pre-built LaunchDarkly & Slack templates today
Start from scratch or use one of our pre-built LaunchDarkly & Slack templates to quickly solve your most common use cases.
LaunchDarkly & Slack Templates
Find pre-built LaunchDarkly & Slack solutions for common use cases
Template
LaunchDarkly Flag Change → Slack Channel Notification
Automatically posts a Slack notification to a specified channel whenever any feature flag is created, updated, or deleted in LaunchDarkly. The message includes the flag key, project, environment, the type of change, the user who made the change, and a deep link back to the flag in LaunchDarkly.
Steps:
- Trigger: LaunchDarkly webhook fires on any flag change event (create, update, delete)
- Transform: Parse the webhook payload to extract flag name, environment, change type, and actor
- Action: Post a formatted Slack message to the designated engineering or release channel
Connectors Used: LaunchDarkly, Slack
Template
LaunchDarkly Kill Switch Toggle → Slack Incident Alert
Monitors LaunchDarkly for flags tagged as kill switches and sends an urgent Slack alert to the incident response channel whenever one is toggled. The alert tags the on-call team via a Slack user group and includes the flag name, affected environment, toggled-by user, and timestamp.
Steps:
- Trigger: LaunchDarkly webhook fires on a flag toggle event for flags tagged as kill switches
- Filter: Confirm the flag tag matches the kill switch designation before proceeding
- Action: Post an urgent Slack alert to the incident channel and mention the on-call user group
Connectors Used: LaunchDarkly, Slack
Template
LaunchDarkly Flag Approval Request → Slack Approver Notification
When a change request requiring approval is created in LaunchDarkly, this template sends a Slack direct message or channel post to the designated approver with full details of the requested change, a link to the approval page, and a follow-up reminder if the request sits unreviewed past a configurable time window.
Steps:
- Trigger: LaunchDarkly webhook fires when a new approval request is submitted for a flag change
- Lookup: Resolve the approver's Slack user ID based on their LaunchDarkly email address
- Action: Send a Slack DM or channel notification to the approver with request details and a direct link
Connectors Used: LaunchDarkly, Slack
Template
Scheduled LaunchDarkly Stale Flag Report → Slack Digest
Runs on a weekly schedule to query LaunchDarkly for flags that haven't been modified within a defined threshold (e.g., 30 days) and posts a digest to a Slack channel organized by project or team, prompting engineers to evaluate and clean up unused flags.
Steps:
- Trigger: Scheduled timer fires on a weekly cadence
- Action: Query LaunchDarkly API for flags not modified within the staleness threshold
- Action: Format and post a grouped Slack digest listing stale flags by project with direct links
Connectors Used: LaunchDarkly, Slack
Template
LaunchDarkly Rollout Percentage Change → Slack Stakeholder Update
Detects when a feature flag's rollout percentage changes in LaunchDarkly and posts an update to a product or release Slack channel summarizing the new rollout state. Useful for progressive delivery workflows where product managers and support teams need visibility but don't have direct LaunchDarkly access.
Steps:
- Trigger: LaunchDarkly webhook fires on a flag rule or percentage rollout change event
- Filter: Confirm the change involves a percentage rollout variation rather than a targeting rule
- Action: Post a Slack update to the release channel with the feature name, new rollout percentage, and environment
Connectors Used: LaunchDarkly, Slack
Template
LaunchDarkly Experiment Completion → Slack Results Summary
Polls LaunchDarkly on a scheduled basis to detect experiments that have reached completion or statistical significance, then posts a results summary to the product team's Slack channel. The summary includes the experiment name, winning variation, confidence level, and a link to the full results in LaunchDarkly.
Steps:
- Trigger: Scheduled timer polls LaunchDarkly API for experiments with a completed or significant status
- Filter: Check for experiments not yet reported on to avoid duplicate notifications
- Action: Post a Slack message to the product channel summarizing the experiment outcome and linking to LaunchDarkly
Connectors Used: LaunchDarkly, Slack