Resources · Zapier integration

LaunchDarkly Zapier integrationAutomate LaunchDarkly with Zapier.

The LaunchDarkly Zapier integration gives you 12 triggers and 4 actions, and no search step. All twelve triggers are instant, and the four actions all work on feature flags: evaluate one, toggle it, patch it, or change who it targets.

See the 16 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the LaunchDarkly Zapier integration is for

LaunchDarkly manages feature flags: switches you turn on or off, and that can target given users on a given variation. Connecting it to Zapier works both ways: activity in your LaunchDarkly account can start work in other apps, and other apps can act on your flags.

Three results come back most often. First, a trace of every change: Flag Event, Segment Event or Member Event start a Zap each time something moves, so the change is logged or announced wherever your team looks. Second, a flag flipped from outside: Toggle a Feature Flag turns a flag on or off when an event happens in another tool, with no one opening the LaunchDarkly dashboard. Third, an audience you manage from elsewhere: Add or Remove User Targets From a Feature Flag adds or removes user keys on one variation of a flag.

The point that changes everything here: the twelve triggers are all instant. LaunchDarkly warns Zapier itself, so the plan interval never delays a Zap, and a free account reacts as fast as an Enterprise one.

What Zapier does not do for LaunchDarkly matters just as much. There is no search step, so a Zap cannot look up a flag or a member before acting. No action creates or deletes a flag, a project or an environment: the four actions only read or change existing flags. And the editing action that goes furthest, Update a Feature Flag With JSON, expects instructions written in JSON, which is not a beginner's job. To weigh other tools on these points, see our n8n vs Zapier and Make vs Zapier comparisons.

Vocabulary

Zapier vocabulary in one minute

Seven words are enough to read the rest of the page. Explained once here, they come back without a reminder.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or changes something for you.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan allowance counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself as the event happens.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
Connection
Your LaunchDarkly account linked to Zapier once, then reused by every LaunchDarkly step of every Zap.
Cost

What a LaunchDarkly Zap really costs

LaunchDarkly is not a premium app: it runs on the free plan. Zapier bills in tasks, and only actions that succeed are counted.

  • Free plan100 tasks a month, unlimited Zaps
  • Zap length on Free2 steps: one trigger, one action
  • Trigger0 task
  • LaunchDarkly triggers12 instant, 0 polling

The trigger never costs a task, however many events LaunchDarkly sends, and an action that fails is not counted. Each successful action counts on its own: a Zap that evaluates a flag and then toggles another uses two tasks per run. The free plan stops at two steps, one trigger and one action; a second action or a filter makes it a multi-step Zap, which needs a paid plan. The interval grid below applies to polling triggers only. All twelve LaunchDarkly triggers are instant, so it never slows anything down here.

Connect

Connect your LaunchDarkly account in three steps

  1. 01

    Open the Apps page

    In Zapier, open Apps and click + Add connection. You need a LaunchDarkly account, plus access to the projects and flags you do not own but want the Zap to read or change.

  2. 02

    Pick LaunchDarkly

    Type LaunchDarkly in the search box of the dialog, select it and click Add connection. A new tab then opens on the LaunchDarkly side, where the sign-in happens.

  3. 03

    Sign in and grant access

    Log in to LaunchDarkly in that tab and allow Zapier to use your account. The connection is stored once, and every LaunchDarkly step of every Zap you build reuses it.

First Zap

Your first LaunchDarkly Zap

GoalWhen a flag changes in one environment, toggle a flag in another environment, but only when the change passes your condition.

  1. 01

    Create the Zap

    Start a new Zap, pick LaunchDarkly as the app that starts it and Flag Event as the event. Choose your LaunchDarkly connection.

  2. 02

    Point at one flag

    The trigger needs a project, an environment and a flag key, all three mandatory. Test it: Zapier brings back the three most recent events so you work on a real one.

  3. 03

    Add a filter

    Add a Filter step from the plus icon, choose the field to look at, the rule and the value. The rule type must match the data, text with text.

  4. 04

    Toggle the other flag

    Add Toggle a Feature Flag, pick the project, a different environment and the flag, then the instruction. Never the flag and environment the trigger watches.

  5. 05

    Test, then publish

    Run each step once and read what came back, then click Publish. With a filter this is a multi-step Zap, so it needs a paid plan.

Triggers

The 12 LaunchDarkly triggers

12 events start a Zap when something happens in LaunchDarkly, and 12 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Access Token Event

Instant trigger

In Zapier“Triggers when access token activity happens on your LaunchDarkly account.”

Starts the Zap whenever something happens to the access tokens of your LaunchDarkly account. One event on any token of the account is enough.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when your team wants a written trace, outside LaunchDarkly, of every token movement.
Watch out
it covers the whole account, with no field to narrow it down, so add a filter if only some events matter, and that makes the Zap multi-step.
2

Code Reference Repository Event

Instant trigger

In Zapier“Triggers when code reference repository activity happens on your LaunchDarkly account.”

Reacts to activity on the code reference repositories linked to your account, as declared in LaunchDarkly.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a change on one of these repositories should reach the people who maintain it without them checking LaunchDarkly.
Watch out
no field narrows the scope, so every repository of the account can start the Zap.
3

Flag Event

Instant trigger

In Zapier“Triggers when flag activity happens on your LaunchDarkly account.”

Follows one feature flag and fires on any activity around it. It is the most targeted trigger of the list, and the natural start for Zaps that act on flags.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a flag going on or off somewhere has to be announced, logged, or mirrored on another flag.
Watch out
project, environment and flag key are mandatory: one Zap watches one flag in one environment.
4

Integration Event

Instant trigger

In Zapier“Triggers when integration activity happens on your LaunchDarkly account.”

Goes off when the integrations set up in your LaunchDarkly account see activity. It watches how LaunchDarkly is plugged into your other tools.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a change to a connection between LaunchDarkly and another tool should not go unnoticed.
Watch out
account wide, with no field to target one integration; a filter sorts the events, at the price of a multi-step Zap.
5

Member Event

Instant trigger

In Zapier“Triggers when member activity happens on your LaunchDarkly account.”

Keeps watch on one member of your LaunchDarkly account and fires on any activity concerning that person.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a change on a specific member account should leave a trace outside LaunchDarkly.
Watch out
the member key is mandatory, so the trigger follows one member, not the whole team. For a group, look at Team Event instead.
6

Relay Proxy Configuration Event

Instant trigger

In Zapier“Triggers when relay proxy configuration activity happens on your LaunchDarkly account.”

Springs into action on activity around the Relay Proxy configurations of your account, whichever one of them changes.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a configuration change has to reach the right people the moment it happens.
Watch out
nothing narrows it to one configuration; every one in the account can start the Zap.
7

Role Event

Instant trigger

In Zapier“Triggers when role activity happens on your LaunchDarkly account.”

Tracks one role of your account, and fires on any activity on it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a change in permissions should be reviewed by someone else than the person who made it.
Watch out
the role key is mandatory, so one Zap follows one role. Several sensitive roles mean several Zaps.
8

Segment Event

Instant trigger

In Zapier“Triggers when segment activity happens on your LaunchDarkly account.”

Watches one segment, in a given project and environment, and reacts to any activity on it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when changing who sits in a segment changes who sees a feature, and that must be known outside LaunchDarkly.
Watch out
project, environment and segment key are all mandatory; the same segment in another environment needs its own Zap.
9

Service Token Event

Instant trigger

In Zapier“Triggers when service token activity happens on your LaunchDarkly account.”

Signals activity on the service tokens of your account, a separate family from the access tokens.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when service token activity should be followed as closely as access tokens, with Access Token Event alongside.
Watch out
it watches all service tokens at once; no field restricts it to one.
10

Team Event

Instant trigger

In Zapier“Triggers when team activity happens on your LaunchDarkly account.”

Wakes up on activity concerning one team of your LaunchDarkly account, chosen when you set the trigger up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when the managers of a team want to be told as soon as its setup changes in LaunchDarkly.
Watch out
the team key is mandatory, so each Zap sticks to one team; it does not cover the others.
11

User Event

Instant trigger

In Zapier“Triggers when user activity happens on your LaunchDarkly account.”

Follows one user, in a given project and environment, and fires on any activity around that user in LaunchDarkly.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when one user's activity in a project matters enough to be followed outside LaunchDarkly.
Watch out
project, environment and user key are mandatory: the trigger watches one user, never all of them.
12

Webhook Event

Instant trigger

In Zapier“Triggers when webhook activity happens on your LaunchDarkly account.”

Keeps an eye on one of the webhooks set up in LaunchDarkly, and fires on any activity concerning it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a webhook others depend on must not change without the right people knowing.
Watch out
the webhook key is mandatory, so the Zap follows one webhook only.
Actions

The 4 LaunchDarkly actions

LaunchDarkly gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Evaluate a Feature Flag

Action

In Zapier“Evaluates a LaunchDarkly feature flag.”

Asks LaunchDarkly which value a flag returns for a given context, and passes the answer to the next steps.

When to use it
when a Zap has to behave differently depending on what a flag says for a given person.
Watch out
the context key is mandatory; a user's email is a common choice, so it must match what LaunchDarkly knows.
2

Toggle a Feature Flag

Action

In Zapier“Toggles a Feature Flag on or off”

Switches a flag on or off in a chosen project and environment, from any event Zapier can see.

When to use it
when something happening in another tool should turn a feature on or off without anyone opening LaunchDarkly.
Watch out
toggling the very flag a Flag Event Zap watches restarts that Zap, again and again.
3

Update a Feature Flag With JSON

Action

In Zapier“Allows you to update a feature flag using JSON”

Changes a flag through instructions written in JSON, LaunchDarkly's semantic patch format, for edits the other actions do not offer.

When to use it
when a change goes beyond on, off or user targets, and someone on the team can write those instructions.
Watch out
a malformed instruction makes the action fail; failed actions are not billed, but the flag stays unchanged.
4

Add or Remove User Targets From a Feature Flag

Action

In Zapier“Updates a feature flag's user targets for the specified variation.”

Adds user keys to, or removes them from, one variation of a flag, so specific people see or stop seeing that version.

When to use it
when the list of people who should get a feature lives in another app.
Watch out
the variation, the instruction and the user keys are mandatory, on top of project, environment and flag.
When it breaks

When a LaunchDarkly Zap breaks

Zapier attaches no help article and no rate limit specific to LaunchDarkly. The failures are those of every Zap, plus one trap that flag actions make easy.

Go through these four cases before publishing. If a Zap is already misbehaving, see our Zapier troubleshooting page.

  • The flag that triggers itself

    A Zap started by Flag Event that toggles or patches the same flag in the same environment sets itself off again and again, and burns through your task count.

  • Nothing from before the Zap

    A Zap only reacts to what happens after it is switched on. Changes made to flags, roles or tokens earlier never come through.

  • Bulk changes held back

    A trigger that suddenly sends a huge batch, after a bulk import or a migration, can be held back by Zapier's flood protection.

  • Empty project or environment lists

    Flag actions need a project, an environment and a flag. If the connected account cannot see them, there is nothing to choose and the step cannot be set.
Need help

Need help automating LaunchDarkly with Zapier?

A person reads every message.

FAQ

LaunchDarkly Zapier integration: frequent questions

01Is the LaunchDarkly Zapier integration free?
Yes, for two-step Zaps. LaunchDarkly is not a premium app, so the free plan covers it, with 100 tasks a month and unlimited Zaps. What the free plan does not cover is length: one trigger and one action, nothing more. Add a filter, a second action or a search step and it becomes a multi-step Zap that needs a paid plan. No price appears on this page, because Zapier changes its grids often.
02How many tasks does a LaunchDarkly Zap use?
One task per action that succeeds, on each run. The trigger is free, even when LaunchDarkly sends many events, and a failed action is not billed. A Zap that toggles one flag uses one task per run. A Zap that evaluates a flag, then updates another, uses two. The real risk is a loop: a Zap that toggles the very flag its trigger watches restarts itself, and every round costs a task.
03Do LaunchDarkly triggers work in real time?
Yes. All twelve LaunchDarkly triggers are instant: LaunchDarkly warns Zapier as soon as the event happens, so the Zap starts at once. The plan interval, from 15 minutes on Free to 1 minute on Team and Enterprise, only concerns polling triggers, and this app has none. On LaunchDarkly, the free plan therefore reacts as fast as the paid ones. A Zap built on an instant trigger shows a lightning bolt in the editor.
04What does it take to connect LaunchDarkly to Zapier?
A LaunchDarkly account, plus access to the projects and flags you do not own but want the Zap to use. In Zapier, open Apps, click + Add connection, pick LaunchDarkly, sign in in the new tab and grant access. The connection is saved once for every Zap. Most steps then ask for a project and an environment, so the account must be able to see them, or the lists stay empty.
05Why does a LaunchDarkly Zap keep running on its own?
Usually because it changes what its own trigger watches. A Zap built on Flag Event that toggles or patches the same flag, in the same environment, reports its own change back to Zapier, which starts the Zap again. Each round costs a task. The fix is to act on another flag or another environment than the one the trigger follows, or to add a filter that stops the second pass.
06What if the LaunchDarkly operation you want is not on Zapier?
Then this integration does not offer it. Zapier lists 12 triggers and 4 actions for LaunchDarkly, with no search step and no action that creates or deletes a flag, a project or an environment. Some needs are still reachable: Update a Feature Flag With JSON covers flag edits the other actions skip, if someone can write the instructions. Beyond that, the operation is simply missing from Zapier for now, and no Zap setting can add it.
07Zapier, Make or n8n for LaunchDarkly?
It comes down to criteria rather than a winner. Zapier is ready now, with 12 instant triggers and 4 flag actions, and the free plan handles two-step Zaps. For Make or n8n, first check whether they offer a LaunchDarkly integration and which operations it has, then how each run is billed. On Zapier, remember that a filter or a second action already calls for a paid plan. Compare those points on your own case before you choose one.
Same platform

Other docs you might need on this stack.

Browse all integrations