Alex Morgan · Principal Engineer
Alex Morgan is a principal engineer at SyncRivo, focused on platform architecture, reliability engineering, and the infrastructure powering real-time messaging interoperability. LinkedIn
April 10, 2026 · 8 min read
Route LaunchDarkly feature flag toggles, kill switch activations, targeting rule changes, and experiment events to Slack, Teams, Webex, Google Chat, and Zoom simultaneously.
LaunchDarkly has a native Slack integration — but no native Microsoft Teams integration. Flag changes surface only in Slack. When your kill switch fires in production, Teams users don't see it until someone tells them manually.
Every LaunchDarkly event type — flag toggles, kill switches, targeting changes, and experiments — delivered simultaneously to Slack, Teams, Webex, Google Chat, and Zoom.
Feature flag activation events — especially in production — routed to the release Slack channel and the product leadership Teams channel simultaneously for deployment visibility across both platforms.
Kill switch activations and flag-off events routed to the on-call Slack channel and engineering leadership Teams channel immediately — signaling a live feature was disabled in response to an incident or degradation.
Targeting rule updates — new user segments, percentage rollout changes, individual user targeting — routed to the feature team Slack channel and the product manager Teams channel for rollout change awareness.
A/B test and multivariate experiment launch events routed to the product Slack channel and the product leadership Teams channel simultaneously — keeping both engineering and product stakeholders informed across platforms.
Flag variation value changes — especially for configuration flags controlling behavior in production — routed to the engineering Slack channel and flagged to the on-call Teams channel for awareness.
Flag archival events — removing old flags no longer serving traffic — routed to the feature team Slack channel and logged to the engineering leads Teams channel for technical debt tracking visibility.
LaunchDarkly audit log webhooks (Account Settings → Integrations → Webhooks) fire for every flag and environment change in the project: flag toggles, targeting rule edits, segment updates, variation changes, and project configuration. Point the audit log webhook at your SyncRivo inbound endpoint. Use SyncRivo routing rules to filter and route by event type — kill switch events to one channel set, targeting changes to another.
LaunchDarkly flag triggers (Flag Settings → Triggers → Webhook) allow individual flags to fire webhook requests on toggle. Use flag triggers for high-visibility flags where Teams visibility is specifically needed: kill switches, billing flags, paywall features, experiment variants in a major A/B test. Point the flag trigger at SyncRivo for multi-platform delivery from that specific flag.
Set per-event routing: flag-off and kill switch events → Slack #on-call + Teams Engineering Leads simultaneously; experiment start events → Slack #product + Teams Product Leadership; production targeting changes → Slack #releases (engineering awareness). Routing rules live in SyncRivo — changing channels requires no LaunchDarkly reconfiguration.
LaunchDarkly's native Slack app supports interactive actions — toggling flags directly from Slack, subscribing to specific flag change notifications from Slack. These Slack-native features require the native app. The SyncRivo webhook path runs in parallel: use native Slack app for Slack-specific interactions; use SyncRivo for Teams delivery and multi-platform routing from the same flag events.
Route flag changes to the right audience — engineering on-call in Slack, product and leadership in Teams — based on event type and environment.
| LaunchDarkly Event | Slack Destination | Teams Destination | Rationale |
|---|---|---|---|
| Kill switch activated (production) | #on-call (immediate response) | Engineering Leads channel | On-call investigates; leadership has real-time awareness |
| Flag toggled on (production) | #releases (deploy confirmation) | Product Leadership channel | Engineering tracks release; product confirms feature is live |
| Targeting rule changed (production) | #releases (rollout change) | Product Leadership (if % rollout) | Engineering sees change; product tracks rollout progression |
| Experiment started | #product-team (experiment active) | Product Leadership channel | Feature team tracks metrics; leadership monitors experiment scope |
| New flag created | #feature-flags (dev awareness) | — (Slack only) | Developer workflow; leadership notified only for major feature flags |
| Flag archived | #feature-flags (cleanup log) | Engineering Leads (tech debt tracking) | Developers see cleanup; leads track flag lifecycle |
| Capability | LaunchDarkly Native | SyncRivo |
|---|---|---|
| Notify Slack | ✓ Native Slack app + flag triggers | ✓ Via SyncRivo webhook relay |
| Notify Microsoft Teams | ✗ No native Teams integration | ✓ Full Teams channel delivery via SyncRivo routing |
| Notify Webex / Google Chat / Zoom | ✗ Not available natively | ✓ All 5 platforms |
| Single flag event → Slack AND Teams simultaneously | ✗ Slack app is Slack-only | ✓ One webhook URL, fan-out to all platforms |
| Kill switch → on-call Slack + leadership Teams simultaneously | ✗ Slack notification only | ✓ Per-event routing rules handle simultaneous delivery |
| Flag-specific triggers on selected high-visibility flags | ✓ LaunchDarkly flag triggers (Enterprise) | ✓ Point flag trigger to SyncRivo for multi-platform routing |
| M&A: notify both organizations on their native platforms | ✗ Slack-only | ✓ Add destination in SyncRivo in minutes |
| Audit trail for flag change notification delivery | ✗ Not provided | ✓ Full event log per delivery |
LaunchDarkly does not have a native Microsoft Teams integration for flag change notifications. LaunchDarkly has a native Slack integration — the LaunchDarkly Slack app routes flag toggle events, targeting rule changes, and audit log entries to Slack channels, and supports Slack triggers for flag actions directly from Slack. There is no equivalent Teams app or webhook integration for routing these events to Microsoft Teams. For engineering organizations where developers use Slack but product managers, release managers, or engineering leadership use Teams, configure LaunchDarkly audit log webhooks pointing to SyncRivo. SyncRivo routes flag change events to Slack, Teams, Webex, Google Chat, and Zoom simultaneously.
LaunchDarkly supports outbound webhooks (Account Settings → Integrations → Webhooks) that fire HTTP POST requests when flag changes occur — toggles, targeting rule edits, new flag creation, flag archival. Point a LaunchDarkly webhook at your SyncRivo inbound endpoint. SyncRivo routes the payload to your configured Teams channel in real time. For flag-specific notifications (rather than all audit log events), use LaunchDarkly flag triggers with a webhook trigger type pointing to SyncRivo, configured on individual flags.
SyncRivo routes any LaunchDarkly webhook payload: feature flag toggled on or off (by environment), targeting rule created or updated, flag killed (kill switch activated), experiment started or stopped, new flag created, flag archived, flag variation updated, and segment changes. Configure routing rules in SyncRivo to route kill switch activations to both Slack and Teams simultaneously; route experiment start events to the product Slack channel and the product leadership Teams channel; route targeting rule changes affecting production to the on-call Slack channel.
LaunchDarkly flag triggers (available on Enterprise plans) allow individual flags to fire webhook requests when flag state changes. Configure a webhook trigger on a feature flag pointing to your SyncRivo inbound endpoint. When the flag is toggled on or off in any environment, LaunchDarkly fires the trigger. SyncRivo routes the event to Slack, Teams, Webex, Google Chat, and Zoom based on your routing configuration. Use flag triggers for high-visibility flags — kill switches, billing features, experiment variants — where cross-platform notification is critical.
Yes. Kill switch activation is one of the most time-sensitive flag events — it indicates a feature was disabled in production in response to an incident or degradation. Configure a LaunchDarkly webhook (or flag trigger on kill switch flags) pointing to SyncRivo. Route kill switch activations to the on-call Slack channel and the engineering leadership Teams channel simultaneously — so the response team on Slack and leadership on Teams are notified in real time without waiting for manual escalation.
Yes. LaunchDarkly supports audit log webhooks (Account Settings → Integrations → Webhooks) that send HTTP POST requests for all flag and environment changes — including flag toggles, targeting rule updates, segment edits, and project configuration changes. This webhook fires for all flag activity across all flags in the project, not just specific flags. For flag-specific notifications on selected flags only, use LaunchDarkly flag triggers instead. Both webhook types can point to SyncRivo for multi-platform delivery.
LaunchDarkly routes flag changes to Slack. SyncRivo routes them to Teams, Webex, Google Chat, and Zoom too — simultaneously, from one webhook, with per-event routing rules.
Ready to connect? Slack ↔ Teams connection setup →