> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/statsig.md).

# Statsig

Connect to Statsig to manage feature gates, experiments, dynamic configs, and segments, and to review who changed what.

## Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication  |
| --------- | --------------- |
| Statsig   | Console API Key |

### Statsig

Connect to Statsig with a Console API key to manage feature gates, experiments, dynamic configs, and segments.

#### Set up in Statsig

1. In the Statsig Console, open Project Settings → Environments & Keys.
2. Create a Console API key for project-management actions. Use a key with the required project permissions; client SDK keys are not equivalent to Console API keys.

#### Set up in StackAI

1. Open **Settings → Connections**, add a connection, and select **Statsig**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field   | Required | What to enter                                                                                                                                                                                                                                                                                                                       |
| --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Console API Key | Yes      | Create a Console API key in Statsig under Project Settings > Keys & Environments. Choose read-write if you want to use the write actions (create gates, change rollouts, add overrides); read-only is enough for the read actions. Server SDK keys do not work here. [Provider instructions](https://console.statsig.com/api_keys). |

**Provider documentation:** [Setup reference](https://docs.statsig.com/access-management/api-keys).

### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

## Use an action

1. Add the required **Statsig** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

## Actions

### List Feature Gates

List the feature gates in your Statsig project with their status and rollout.

#### Inputs

| Field                 | Type            | Required | Description                                                                            |
| --------------------- | --------------- | -------- | -------------------------------------------------------------------------------------- |
| Show Advanced Options | boolean         | No       | Reveal filters by gate type, tags, archived state, and page. Default: false.           |
| Gate Type             | select (string) | No       | Only show gates of this lifecycle type. Available values: Temporary, Permanent, Stale. |
| Tags                  | string          | No       | Only show gates with these tags, separated by commas.                                  |
| Include Archived      | boolean         | No       | Also show gates that have been archived. Default: false.                               |
| Max Results           | integer         | No       | The most gates to return. Minimum: 1. Maximum: 500. Default: 50.                       |
| Page                  | integer         | No       | Which page of results to start from. Minimum: 1.                                       |

#### Outputs

| Field     | Type          | Description                       |
| --------- | ------------- | --------------------------------- |
| Gates     | object\_array | The matching feature gates.       |
| Next Page | integer       | Page to request for more results. |

### Get Feature Gate

Look up one feature gate, including its rules and rollout percentages.

#### Inputs

| Field        | Type            | Required | Description                                                             |
| ------------ | --------------- | -------- | ----------------------------------------------------------------------- |
| Feature Gate | select (string) | Yes      | The feature gate to look up. Options load from the selected connection. |

#### Outputs

| Field | Type   | Description               |
| ----- | ------ | ------------------------- |
| Gate  | object | The feature gate details. |

### Create Feature Gate

Create a new feature gate, optionally rolled out to a percentage of everyone.

#### Inputs

| Field              | Type            | Required | Description                                                                                                                            |
| ------------------ | --------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Gate Name          | string          | Yes      | A short name for the gate. It becomes the gate's id in your code.                                                                      |
| Description        | textarea        | No       | What the gate controls.                                                                                                                |
| Rollout Percentage | number          | No       | Percentage of everyone who should pass the gate (0-100). Leave empty to start with no rules. Minimum: 0. Maximum: 100.                 |
| Advanced Options   | boolean         | No       | Show unit type, gate type, and tags. Default: false.                                                                                   |
| Unit Type          | string          | No       | Which identifier the gate evaluates, such as userID or stableID. Default: userID.                                                      |
| Gate Type          | select (string) | No       | Temporary gates are meant to be removed after launch; permanent ones stay. Available values: Temporary, Permanent. Default: TEMPORARY. |
| Tags               | string          | No       | Tags to add, separated by commas.                                                                                                      |

#### Outputs

| Field | Type   | Description           |
| ----- | ------ | --------------------- |
| Gate  | object | The new feature gate. |

### Set Feature Gate Status

Turn a feature gate on or off.

#### Inputs

| Field        | Type            | Required | Description                                                                    |
| ------------ | --------------- | -------- | ------------------------------------------------------------------------------ |
| Feature Gate | select (string) | Yes      | The feature gate to turn on or off. Options load from the selected connection. |
| Status       | select (string) | Yes      | Whether the gate should be on or off. Available values: On, Off.               |

#### Outputs

| Field | Type   | Description               |
| ----- | ------ | ------------------------- |
| Gate  | object | The updated feature gate. |

### Update Feature Gate Rollout

Change the percentage of people who pass one rule of a feature gate.

#### Inputs

| Field              | Type            | Required | Description                                                                               |
| ------------------ | --------------- | -------- | ----------------------------------------------------------------------------------------- |
| Feature Gate       | select (string) | Yes      | The feature gate to change. Options load from the selected connection.                    |
| Rule               | select (string) | Yes      | The rule whose rollout to change. Options load from the selected connection.              |
| Rollout Percentage | number          | Yes      | Percentage of people matching the rule who should pass (0-100). Minimum: 0. Maximum: 100. |

#### Outputs

| Field | Type   | Description               |
| ----- | ------ | ------------------------- |
| Gate  | object | The updated feature gate. |

### Add Feature Gate Overrides

Force specific users to always pass or always fail a feature gate.

#### Inputs

| Field        | Type            | Required | Description                                                                      |
| ------------ | --------------- | -------- | -------------------------------------------------------------------------------- |
| Feature Gate | select (string) | Yes      | The feature gate to add overrides to. Options load from the selected connection. |
| Always Pass  | string          | No       | User IDs that should always pass, separated by commas.                           |
| Always Fail  | string          | No       | User IDs that should always fail, separated by commas.                           |

#### Outputs

| Field            | Type          | Description                      |
| ---------------- | ------------- | -------------------------------- |
| Passing User IDs | string\_array | All user IDs now forced to pass. |
| Failing User IDs | string\_array | All user IDs now forced to fail. |

### List Experiments

List the experiments (A/B tests) in your Statsig project.

#### Inputs

| Field                 | Type            | Required | Description                                                                                                                                |
| --------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| Status                | select (string) | No       | Only show experiments in this state. Available values: Running, In setup, Decision made, Abandoned, Archived, Stopped, Assignment stopped. |
| Show Advanced Options | boolean         | No       | Reveal filters by tags and page. Default: false.                                                                                           |
| Tags                  | string          | No       | Only show experiments with these tags, separated by commas.                                                                                |
| Max Results           | integer         | No       | The most experiments to return. Minimum: 1. Maximum: 500. Default: 50.                                                                     |
| Page                  | integer         | No       | Which page of results to start from. Minimum: 1.                                                                                           |

#### Outputs

| Field       | Type          | Description                       |
| ----------- | ------------- | --------------------------------- |
| Experiments | object\_array | The matching experiments.         |
| Next Page   | integer       | Page to request for more results. |

### Get Experiment

Look up one experiment's setup and status.

#### Inputs

| Field      | Type            | Required | Description                                                           |
| ---------- | --------------- | -------- | --------------------------------------------------------------------- |
| Experiment | select (string) | Yes      | The experiment to look up. Options load from the selected connection. |

#### Outputs

| Field      | Type   | Description             |
| ---------- | ------ | ----------------------- |
| Experiment | object | The experiment details. |

### List Dynamic Configs

List the dynamic configs (remote settings) in your Statsig project.

#### Inputs

| Field                 | Type    | Required | Description                                                        |
| --------------------- | ------- | -------- | ------------------------------------------------------------------ |
| Show Advanced Options | boolean | No       | Reveal filters by tags and page. Default: false.                   |
| Tags                  | string  | No       | Only show configs with these tags, separated by commas.            |
| Max Results           | integer | No       | The most configs to return. Minimum: 1. Maximum: 500. Default: 50. |
| Page                  | integer | No       | Which page of results to start from. Minimum: 1.                   |

#### Outputs

| Field           | Type          | Description                       |
| --------------- | ------------- | --------------------------------- |
| Dynamic Configs | object\_array | The matching dynamic configs.     |
| Next Page       | integer       | Page to request for more results. |

### Get Dynamic Config

Read a dynamic config's default value and targeting rules.

#### Inputs

| Field          | Type            | Required | Description                                                            |
| -------------- | --------------- | -------- | ---------------------------------------------------------------------- |
| Dynamic Config | select (string) | Yes      | The dynamic config to read. Options load from the selected connection. |

#### Outputs

| Field          | Type   | Description                 |
| -------------- | ------ | --------------------------- |
| Dynamic Config | object | The dynamic config details. |

### Add IDs to Segment

Add user or unit IDs to an ID list segment.

#### Inputs

| Field   | Type            | Required | Description                                                               |
| ------- | --------------- | -------- | ------------------------------------------------------------------------- |
| Segment | select (string) | Yes      | The ID list segment to add to. Options load from the selected connection. |
| IDs     | textarea        | Yes      | IDs to add, separated by commas or new lines.                             |

#### Outputs

| Field      | Type    | Description                   |
| ---------- | ------- | ----------------------------- |
| Segment ID | string  | The segment that was updated. |
| IDs Added  | integer | How many IDs were sent.       |

### List Change History

See who changed what in your Statsig project, and when.

#### Inputs

| Field       | Type    | Required | Description                                                        |
| ----------- | ------- | -------- | ------------------------------------------------------------------ |
| From        | string  | No       | Earliest date to include. Defaults to 90 days before the end date. |
| To          | string  | No       | Latest date to include. Defaults to today.                         |
| Max Results | integer | No       | The most entries to return. Minimum: 1. Maximum: 500. Default: 50. |
| Page        | integer | No       | Which page of results to start from. Minimum: 1.                   |

#### Outputs

| Field     | Type          | Description                       |
| --------- | ------------- | --------------------------------- |
| Entries   | object\_array | The change history entries.       |
| Next Page | integer       | Page to request for more results. |

## Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/statsig.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
