> 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/doppler.md).

# Doppler

Manage Doppler projects, configs, and application secrets.

### Connectors

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

| Connector | Authentication |
| --------- | -------------- |
| Doppler   | API Token      |

#### Doppler

Connect to Doppler to discover projects and manage secrets in selected configs.

**Set up in Doppler**

1. Prepare the Doppler account or service that the workflow will access. Grant access to the required resources and operations.
2. Create or obtain the API credential identified in the fields below. Use the provider instructions linked with those fields to find its key-management page.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Doppler**.
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                                                                                                                                                                                                                                           |
| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| API Token     | Yes      | Paste a Doppler API token. For automation, prefer a Service Account token with only the required project and environment access. Any capable Doppler Bearer token is accepted. [Provider instructions](https://docs.doppler.com/docs/service-accounts). |

#### 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 **Doppler** 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 Projects

List Doppler projects available to the connected token.

**Inputs**

| Field            | Type    | Required | Description                                                                   |
| ---------------- | ------- | -------- | ----------------------------------------------------------------------------- |
| Maximum Projects | integer | No       | Maximum number of projects to return. Minimum: 1. Maximum: 400. Default: 100. |
| Start Page       | integer | No       | Provider page number to start from. Minimum: 1. Default: 1.                   |

**Outputs**

| Field     | Type          | Description                                                           |
| --------- | ------------- | --------------------------------------------------------------------- |
| Projects  | object\_array | Typed project records returned by Doppler.                            |
| Next Page | integer       | Page number to use for the next request, when more results may exist. |

#### List Configs

List configs in a Doppler project so one can be selected for secret operations.

**Inputs**

| Field           | Type            | Required | Description                                                                                |
| --------------- | --------------- | -------- | ------------------------------------------------------------------------------------------ |
| Project         | select (string) | Yes      | Doppler project whose configs should be listed. Options load from the selected connection. |
| Environment     | string          | No       | Optional environment slug used to narrow the configs.                                      |
| Maximum Configs | integer         | No       | Maximum number of configs to return. Minimum: 1. Maximum: 400. Default: 100.               |
| Start Page      | integer         | No       | Provider page number to start from. Minimum: 1. Default: 1.                                |

**Outputs**

| Field     | Type          | Description                                                           |
| --------- | ------------- | --------------------------------------------------------------------- |
| Configs   | object\_array | Typed config records returned by Doppler.                             |
| Next Page | integer       | Page number to use for the next request, when more results may exist. |

#### List Secrets

List secret names in one Doppler config.

**Inputs**

| Field        | Type            | Required | Description                                                                       |
| ------------ | --------------- | -------- | --------------------------------------------------------------------------------- |
| Project      | select (string) | Yes      | Project containing the config. Options load from the selected connection.         |
| Config       | select (string) | Yes      | Config whose secrets should be listed. Options load from the selected connection. |
| Secret Names | string          | No       | Optional comma-separated secret names to include.                                 |

**Outputs**

| Field        | Type          | Description                          |
| ------------ | ------------- | ------------------------------------ |
| Secret Names | string\_array | Secret names in the selected config. |
| Count        | integer       | Number of secret names returned.     |

#### Create a Secret

Create one new secret in a Doppler config without overwriting an existing name.

**Inputs**

| Field        | Type            | Required | Description                                                                                    |
| ------------ | --------------- | -------- | ---------------------------------------------------------------------------------------------- |
| Project      | select (string) | Yes      | Project containing the target config. Options load from the selected connection.               |
| Config       | select (string) | Yes      | Config where the secret should be created. Options load from the selected connection.          |
| Secret Name  | string          | Yes      | Name of the new secret.                                                                        |
| Secret Value | secret          | Yes      | Sensitive value to store in Doppler.                                                           |
| Visibility   | select (string) | No       | Optional visibility policy for the new secret. Available values: Masked, Unmasked, Restricted. |

**Outputs**

| Field       | Type    | Description                              |
| ----------- | ------- | ---------------------------------------- |
| Project     | string  | Project containing the created secret.   |
| Config      | string  | Config containing the created secret.    |
| Secret Name | string  | Name of the created secret.              |
| Created     | boolean | Whether Doppler accepted the new secret. |

#### Update a Secret

Set one existing Doppler secret to an exact new value.

**Inputs**

| Field                             | Type            | Required | Description                                                                                                          |
| --------------------------------- | --------------- | -------- | -------------------------------------------------------------------------------------------------------------------- |
| Project                           | select (string) | Yes      | Project containing the secret. Options load from the selected connection.                                            |
| Config                            | select (string) | Yes      | Config containing the secret. Options load from the selected connection.                                             |
| Secret Name                       | string          | Yes      | Existing secret name to update.                                                                                      |
| New Value                         | secret          | Yes      | Exact replacement value, including an empty value when needed.                                                       |
| Expected Current Value (Advanced) | secret          | No       | Optional current value that must still match before updating.                                                        |
| Visibility (Advanced)             | select (string) | No       | Optional visibility to set; leave blank to keep the current setting. Available values: Masked, Unmasked, Restricted. |

**Outputs**

| Field       | Type    | Description                            |
| ----------- | ------- | -------------------------------------- |
| Project     | string  | Project containing the updated secret. |
| Config      | string  | Config containing the updated secret.  |
| Secret Name | string  | Name of the updated secret.            |
| Updated     | boolean | Whether Doppler accepted the update.   |

#### Delete a Secret

Permanently delete one Doppler secret after confirmation.

**Inputs**

| Field                      | Type            | Required | Description                                                                         |
| -------------------------- | --------------- | -------- | ----------------------------------------------------------------------------------- |
| Project                    | select (string) | Yes      | Project containing the secret to delete. Options load from the selected connection. |
| Config                     | select (string) | Yes      | Config containing the secret to delete. Options load from the selected connection.  |
| Secret Name                | string          | Yes      | Exact secret name to permanently delete.                                            |
| Confirm Permanent Deletion | boolean         | Yes      | Confirm that this secret should be permanently deleted. Default: false.             |

**Outputs**

| Field       | Type    | Description                                       |
| ----------- | ------- | ------------------------------------------------- |
| Project     | string  | Project that contained the deleted secret.        |
| Config      | string  | Config that contained the deleted secret.         |
| Secret Name | string  | Name of the deleted secret.                       |
| Deleted     | boolean | Whether Doppler confirmed the secret was deleted. |

### 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/doppler.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.
