Skip to main content
Flag triggers are available to customers on select plansFlag triggers are only available to customers on select plans. To learn more, read about our pricing. To upgrade your plan, contact Sales.
Consider adaptive flag triggers insteadAdaptive flag triggers let you automatically serve a different flag variation and send an alert when a LaunchDarkly metric or observability metric indicates a problem. To learn how to use them, read Adaptive triggers.
This topic explains how to use the LaunchDarkly flag triggers feature, which lets you make changes to flag targeting remotely from a third-party application, like an APM tool. You can use triggers to turn flag targeting on or off.
You can also use the REST API: Flag triggers

​
About flag triggers

A trigger lets you initiate flag changes remotely using a unique webhook URL. Triggers integrate with your existing tools to let you enable or disable flags when you hit specific operational health thresholds or receive certain alerts. A flag can have multiple triggers attached to multiple tools or alerts. Triggers work by creating unique URLs to connect feature flags to third-party tools. When the third-party tool generates a specific alert, the trigger sets the flag’s targeting to On or Off. Each URL controls one action, and the URLs are distinct from each other. Subsequent requests to the flag’s On URL will not change the flag’s state after the initial contact turns the flag On.
Triggers are environment-specificTriggers are unique to each flag within a given environment. This means that you can add multiple tools and multiple triggers to every flag, but if you wish to use the same trigger in multiple environments, you must create a new trigger for each flag in each environment as flags do not share URLs across environments.
Flag triggers are rate limited to prevent a flag turning on and off indefinitely if the triggering metric changes frequently. To learn how to create and manage flag triggers, read Creating flag triggers and Managing flag triggers.

​
Flag trigger security

Although flag triggers use public URLs, they’re still a very secure way to initiate changes to your feature flags. Here’s why:
  • Triggers use unguessable URLs, and
  • Only some people in your LaunchDarkly project can create or modify triggers.
An unguessable URL is functionally similar to an access token in that it does not require an active connection between LaunchDarkly and other services to work. To learn more about unguessable URLs, read Google’s Unguessable URLs. When you create a new trigger, its URL only displays once and prompts you to copy it locally. After the initial display, URLs are obscured so future viewers of the flag cannot view them. If you lose a trigger’s URL, you can reset it from the trigger’s overflow menu. To learn more, read Managing flag triggers. Additionally, not all LaunchDarkly account members can interact with triggers. To modify existing triggers or create new ones, account members must have the LaunchDarkly Project Admin or Maintainer project role, or the Writer, Admin, or Owner base role, or another role with the createTriggers and updateTriggers permission. If you use custom roles to manage your team, every account member who needs to manage triggers must be able to use the createTriggers, updateTriggers and deleteTriggers actions. To learn more, read Roles.

​
Integrations that use flag triggers

Triggers are available on the following tools. Read each tool’s documentation to learn how to set up triggers for them. The tools are: LaunchDarkly also supports generic triggers that you can use with other tools. To learn more, read Creating flag triggers. Generic triggers can connect to anything that fires a webhook. If a tool or service accepts an inbound connection from a webhook, you can use that service to turn flag targeting on or off. For example, if your company has an in-house monitoring application, you can use a generic trigger to turn flags on or off directly from your application. Generic triggers work without any request body, but if you want to enhance the flag’s change history with more information, you can add different attributes. Any combination of properties will return information, and every attribute is optional. To do this, send a JSON payload with the following shape:
The payload supports two optional attributes:
  • eventName: A name or description associated with the event
  • url: A link to direct a member to more information