LaunchDarkly

Connect LaunchDarklyCopy Anchor Link

A workspace administrator connects LaunchDarkly as an organization connector in Customize → Connectors. The trigger uses that shared OAuth connection to register its webhook, so it must have permission to manage webhooks in LaunchDarkly.

Add the triggerCopy Anchor Link

Select LaunchDarkly flag change under Add trigger, then choose a project under Project key. Choose an environment under Environment key to limit the trigger to changes in that environment, or leave it blank for any environment.

Add conditions to narrow which changes start a run. Every condition must match:

• Flag key is, is not, contains, or starts with a value. With is or is not, choose a flag from the project; use contains or starts with to match several flags.
• Action matches a LaunchDarkly action name such as updateOn.
• Member email matches the person who made the change.
• Comment matches the comment saved with the change.

A change without a member email or comment never matches a condition on that field, including is not. With no conditions, every flag change in the project and environment starts a run.

Save the automation. Inspect creates a signed webhook named Inspect … in LaunchDarkly that covers the projects of its enabled triggers, and removes the webhook when no enabled triggers use it. If setup fails, the trigger shows the error; fix the connection, then save the automation again to retry.

What starts a runCopy Anchor Link

Each LaunchDarkly audit log entry that matches starts one run per automation, even when several of its triggers match. The agent receives the change's title, description, member, comment, actions, and the flag's previous and current versions.

Repeated deliveries of the same audit log entry do not create another run. Creating a trigger does not replay earlier changes; it responds to subsequent ones.

ExampleCopy Anchor Link

To review risky releases, add a trigger for the production environment with Action is updateOn. Prompt the automation to compare the flag's previous and current targeting, check recent errors for the affected service, and post a summary to the owning team's channel.