# LaunchDarkly + Slack integration

> Automate feature flag alerts, rollout notifications, and incident escalations directly in Slack so your engineering and product teams never miss a change that matters.

**Canonical page:** https://tray.ai/connectors/launchdarkly-slack-integrations/
**LaunchDarkly connector:** https://tray.ai/connectors/launchdarkly-integrations/
**LaunchDarkly documentation:** https://tray.ai/documentation/connectors/service/launchdarkly
**Slack connector:** https://tray.ai/connectors/slack-integrations/
**Slack documentation:** https://tray.ai/documentation/connectors/service/slack

## Overview

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.

Feature flags let teams move fast — dark launches, gradual rollouts, kill switches, A/B experiments, all without redeploying code. But that speed creates a communication problem. Flag changes can happen at any time by any authorized team member, and without visibility, engineers, product managers, QA, and on-call responders get caught off guard. Connecting LaunchDarkly to Slack means every meaningful flag event — a toggle, a targeting rule update, a percentage rollout shift — shows up in the right Slack channel, tagged to the right people. It cuts mean time to resolution during incidents and gives distributed teams a shared, real-time view of what's live in production.

## Use cases

### 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.

- Eliminate blind spots around who changed what flag and when
- Reduce miscommunication between product, engineering, and QA during releases
- Create a persistent, searchable record of flag changes in Slack

### 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.

- Cut seconds off incident response time by removing manual Slack notifications
- Keep on-call engineers looped in during emergency flag changes
- Reduce confusion between teams about whether a feature has been disabled

### 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.

- Keep non-technical stakeholders informed without granting LaunchDarkly access
- Build confidence in gradual rollouts with visible milestone tracking
- Let support teams prepare proactively for user-facing changes

### 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.

- Reduce feature flag technical debt before it becomes unmanageable
- Assign cleanup accountability to specific Slack channels or team members
- Keep the LaunchDarkly environment clean and easy to navigate

### 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.

- Surface experiment results the moment they're ready, not hours later
- Notify the right product and analytics stakeholders automatically
- Reduce the time experiments stay live past their useful window

### 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.

- Reduce approval bottlenecks by surfacing requests directly in Slack
- Give approvers full context without requiring them to check LaunchDarkly proactively
- Maintain a clear record of approval requests and responses in Slack threads

### 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.

- Give QA teams real-time awareness of flag states in non-production environments
- Reduce test failures caused by unexpected flag configurations
- Speed up QA cycles by eliminating manual flag state verification

## Templates

### 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.

Connectors used: LaunchDarkly, Slack

Steps:
1. Trigger: LaunchDarkly webhook fires on any flag change event (create, update, delete)
2. Transform: Parse the webhook payload to extract flag name, environment, change type, and actor
3. Action: Post a formatted Slack message to the designated engineering or release channel

### 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.

Connectors used: LaunchDarkly, Slack

Steps:
1. Trigger: LaunchDarkly webhook fires on a flag toggle event for flags tagged as kill switches
2. Filter: Confirm the flag tag matches the kill switch designation before proceeding
3. Action: Post an urgent Slack alert to the incident channel and mention the on-call user group

### 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.

Connectors used: LaunchDarkly, Slack

Steps:
1. Trigger: LaunchDarkly webhook fires when a new approval request is submitted for a flag change
2. Lookup: Resolve the approver's Slack user ID based on their LaunchDarkly email address
3. Action: Send a Slack DM or channel notification to the approver with request details and a direct link

### 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.

Connectors used: LaunchDarkly, Slack

Steps:
1. Trigger: Scheduled timer fires on a weekly cadence
2. Action: Query LaunchDarkly API for flags not modified within the staleness threshold
3. Action: Format and post a grouped Slack digest listing stale flags by project with direct links

### 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.

Connectors used: LaunchDarkly, Slack

Steps:
1. Trigger: LaunchDarkly webhook fires on a flag rule or percentage rollout change event
2. Filter: Confirm the change involves a percentage rollout variation rather than a targeting rule
3. Action: Post a Slack update to the release channel with the feature name, new rollout percentage, and environment

### 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.

Connectors used: LaunchDarkly, Slack

Steps:
1. Trigger: Scheduled timer polls LaunchDarkly API for experiments with a completed or significant status
2. Filter: Check for experiments not yet reported on to avoid duplicate notifications
3. Action: Post a Slack message to the product channel summarizing the experiment outcome and linking to LaunchDarkly

## Challenges Tray.ai solves

### 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 helps:** 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.

### 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 helps:** 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.

### 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 helps:** 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.

### 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 helps:** 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.

### 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 helps:** 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.

## 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/