LaunchDarkly

Feature flag management API. Control feature rollouts, manage flags, and track usage.

Detail	Value
Category	Dev Tools
Base URL	https://app.launchdarkly.com/api/v2
Authentication	API Key
Endpoints	6
Connector key	launchdarkly

Using LaunchDarkly in a workflow

1. Go to Connections and click New Connection.
2. Pick LaunchDarkly from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /flags/{projectKey}	List feature flags
POST /flags/{projectKey}	Create a feature flag
GET /flags/{projectKey}/{featureFlagKey}	Get a feature flag
DELETE /flags/{projectKey}/{featureFlagKey}	Delete a feature flag
GET /projects	List projects
GET /projects/{projectKey}/environments	List environments

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /flags/{projectKey}

List feature flags

Detail	Value
Operation ID	devtools.listFlags
Method	GET
Path	/flags/{projectKey}

Parameters

Name	Location	Type	Required
projectKey	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your LaunchDarkly connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.listFlags.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream LaunchDarkly API reference.

POST /flags/{projectKey}

Create a feature flag

Detail	Value
Operation ID	devtools.createFlag
Method	POST
Path	/flags/{projectKey}

Parameters

Name	Location	Type	Required
projectKey	path	string	Yes

Request Body

Field	Type
name	string
key	string
variations	array

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your LaunchDarkly connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.createFlag.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream LaunchDarkly API reference.

GET /flags/{projectKey}/{featureFlagKey}

Get a feature flag

Detail	Value
Operation ID	devtools.getFlag
Method	GET
Path	/flags/{projectKey}/{featureFlagKey}

Parameters

Name	Location	Type	Required
projectKey	path	string	Yes
featureFlagKey	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your LaunchDarkly connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.getFlag.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream LaunchDarkly API reference.

DELETE /flags/{projectKey}/{featureFlagKey}

Delete a feature flag

Detail	Value
Operation ID	devtools.deleteFlag
Method	DELETE
Path	/flags/{projectKey}/{featureFlagKey}

Parameters

Name	Location	Type	Required
projectKey	path	string	Yes
featureFlagKey	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your LaunchDarkly connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.deleteFlag.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream LaunchDarkly API reference.

GET /projects

List projects

Detail	Value
Operation ID	devtools.listProjects
Method	GET
Path	/projects

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your LaunchDarkly connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.listProjects.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream LaunchDarkly API reference.

GET /projects/{projectKey}/environments

List environments

Detail	Value
Operation ID	devtools.listEnvironments
Method	GET
Path	/projects/{projectKey}/environments

Parameters

Name	Location	Type	Required
projectKey	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your LaunchDarkly connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.listEnvironments.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream LaunchDarkly API reference.