Skip to main content
Plan requirement: This feature requires an On-call Standard or higher subscription. Learn more
Use a LaunchDarkly organization webhook to sync feature flag and segment changes to Flashduty On-call. Each flag or segment entry in LaunchDarkly’s change history becomes one Flashduty change, for example turning a flag on or off, editing targeting rules, or changing the default rule. LaunchDarkly sends changes that have already taken effect, so each change is recorded as Done directly.

​
In Flashduty On-call

  1. In the Flashduty console, go to Integration Center → Change Events
  2. Select LaunchDarkly and enter an integration name
  3. To assign changes to specific channels, add rules under the integration’s Routes that match labels such as project, environment, or flag
  4. Click Save and copy the generated Push URL

​
Configure LaunchDarkly

1

Open the Webhooks integration

  1. Click the gear icon in the left sidebar to open Organization settings
  2. Click Integrations, find Webhooks, and click Add new
You need a member role that can manage integrations, such as Admin.
2

Enter the push URL

  1. Name: enter a recognizable name, such as Flashduty
  2. URL: paste the full push URL of the Flashduty integration
  3. Sign this webhook: leave it unchecked. Flashduty authenticates the delivery by the integration_key in the push URL
3

Choose what to send

Without a policy, LaunchDarkly sends only flag changes in the production environment. To send other environments or segment changes, add this policy:
Replace env/* with a specific environment (such as env/production) to send only that environment. Accept the terms and click Save settings.
LaunchDarkly has no test delivery button. After saving, make one change to any flag and the record appears in the Flashduty change list.

​
What one change is

​
Status mapping

These deliveries are accepted without creating a change:
  • Entries for other resource kinds, such as projects, environments, members, roles, webhooks, metrics, and experiments
  • Entries that contain only the following actions, which do not change how a flag evaluates:
    • Creating, updating, reviewing, or deleting an approval request (once an approval request is applied, LaunchDarkly sends the entry for that step)
    • Creating, updating, or deleting scheduled changes (the entry for the scheduled change is sent when it runs)
    • Name, description, tags, maintainer, temporary flag, deprecation, custom properties, rule descriptions, code references, flag links, followers, and segment exports

​
Change content

Labels can be used in routes and to filter the change list:

​
FAQ

Without a policy, LaunchDarkly sends only flag changes in the production environment. Add a policy as described in Choose what to send.
No. When a delivery fails, LaunchDarkly retries it once with the same content, and Flashduty records it once.
LaunchDarkly does not guarantee chronological delivery. Flashduty uses the entry’s own time (date) as the change time.
  • _id is missing: the payload is incomplete. Make sure the delivery comes from a native LaunchDarkly webhook
  • invalid date: the time field in the payload is malformed