> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Doppler

The Doppler connector lets your AI agent act in each user's Doppler account. Each user connects their own Doppler access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 26 tools.

**Authentication:** Bearer Token
**Categories:** Developer Tools
**Tools:** 26: 16 read, 9 write, 1 destructive
**Users sign in with:** Access token
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=DOPPLER)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Doppler connection

   In **AgentKit > Connections**, create a Doppler connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'doppler'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Doppler:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'doppler_activity_log_list',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "doppler"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Doppler:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="doppler_activity_log_list",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Doppler credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'doppler_activity_log_get',
  toolInput: {
    log: '<log>',
  },
  connector: 'doppler',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="doppler_activity_log_get",
    tool_input={
        "log": "<log>",
    },
    connection_name="doppler",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `doppler_activity_log_get`

Get Activity Log · Read-only

Get one entry from the Doppler workplace activity log by ID.
Returns the log's id, text, html, created_at, project, environment, config and user.
Use doppler_activity_log_get for a known log entry. Use doppler_activity_log_list to find the log id.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `log` (`string`, required): ID of the activity log entry, from the `id` field returned by doppler_activity_log_list. Example: emwk7ra70oem3xa

Example input: `{"log":"<log>"}`

### `doppler_activity_log_list`

List Activity Logs · Read-only

List the activity log for the whole Doppler workplace, newest first, one page at a time.
Returns each log's id, text, html, created_at, project, environment, config and the user who acted.
Use doppler_activity_log_list to audit workplace-wide activity. Use doppler_config_log_list for the history of one config.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number to return, starting at 1. Example: 2. Default: `1`.
- `per_page` (`integer`, optional): Number of items per page. Defaults to 20. Example: 50. Default: `20`.

Example input: `{}`

### `doppler_config_get`

Get Config · Read-only

Get one config in a Doppler project by name.
Returns the config's name, environment, project, root, locked, initial_fetch_at, last_fetch_at and created_at.
Use doppler_config_get for a known config. Use doppler_config_list to browse configs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `config` (`string`, required): Config name inside the project, from the `name` field returned by doppler_config_list. Root configs are named after their environment slug (dev, stg, prd); branch configs look like dev_personal or prd_aws. Example: prd
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend

Example input: `{"config":"<config>","project":"<project>"}`

### `doppler_config_list`

List Configs · Read-only

List the configs in a Doppler project, optionally only those in one environment.
Returns each config's name, environment, project, root, locked, initial_fetch_at, last_fetch_at and created_at, plus the page number.
Use doppler_config_list to find a config name for the secret tools. Use doppler_config_get for one known config.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
- `environment` (`string`, optional): Environment slug inside the project, from the `id` field returned by doppler_environment_list. Example: dev
- `page` (`integer`, optional): Page number to return, starting at 1. Example: 2. Default: `1`.
- `per_page` (`integer`, optional): Number of items per page. Defaults to 20. Example: 50. Default: `20`.

Example input: `{"project":"<project>"}`

### `doppler_config_log_get`

Get Config Log · Read-only

Get one change in a Doppler config's history, including the secret diff.
Returns the log's id, text, rollback flag, created_at, user and a diff array of the secrets added, changed or removed. The diff can contain secret values in plaintext.
Use doppler_config_log_get to see exactly what one change did. Use doppler_config_log_list to find the log id.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `config` (`string`, required): Config name inside the project, from the `name` field returned by doppler_config_list. Root configs are named after their environment slug (dev, stg, prd); branch configs look like dev_personal or prd_aws. Example: prd
- `log` (`string`, required): ID of the config log, from the `id` field returned by doppler_config_log_list. Example: WaRMMyxHUg4lOKR
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend

Example input: `{"config":"<config>","log":"<log>","project":"<project>"}`

### `doppler_config_log_list`

List Config Logs · Read-only

List the change history of a Doppler config, newest first, one page at a time.
Returns each log's id, text, html, rollback flag, created_at, config, environment, project and the user who made the change. Secret values are not included.
Use doppler_config_log_list to see who changed a config and when. Use doppler_config_log_get for the secret diff of one change.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `config` (`string`, required): Config name inside the project, from the `name` field returned by doppler_config_list. Root configs are named after their environment slug (dev, stg, prd); branch configs look like dev_personal or prd_aws. Example: prd
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
- `page` (`integer`, optional): Page number to return, starting at 1. Example: 2. Default: `1`.
- `per_page` (`integer`, optional): Number of items per page. Defaults to 20. Example: 50. Default: `20`.

Example input: `{"config":"<config>","project":"<project>"}`

### `doppler_environment_get`

Get Environment · Read-only

Get one environment in a Doppler project by its slug.
Returns the environment's id (slug), name, project, initial_fetch_at and created_at.
Use doppler_environment_get for a known environment. Use doppler_environment_list to browse.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `environment` (`string`, required): Environment slug inside the project, from the `id` field returned by doppler_environment_list. Example: dev
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend

Example input: `{"environment":"<environment>","project":"<project>"}`

### `doppler_environment_list`

List Environments · Read-only

List the environments in a Doppler project.
Returns each environment's id (slug), name, project, initial_fetch_at and created_at.
Use doppler_environment_list to find environment slugs. Use doppler_config_list to see the configs inside an environment.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend

Example input: `{"project":"<project>"}`

### `doppler_me_get`

Get Token Info · Read-only

Get details about the Doppler token used for this connection.
Returns the token's slug, name, type (personal, service, service_account, cli), token preview, last seen time and workplace.
Use doppler_me_get to check which kind of token is connected before calling project-wide tools; a service token can only reach its own config.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `doppler_project_get`

Get Project · Read-only

Get one Doppler project by its slug.
Returns the project's id, name, description and created_at.
Use doppler_project_get to check a known project. Use doppler_project_list to browse projects.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend

Example input: `{"project":"<project>"}`

### `doppler_project_list`

List Projects · Read-only

List the projects in the Doppler workplace, one page at a time, optionally filtered by tags.
Returns each project's id, slug, name, description and created_at, plus the page number.
Use doppler_project_list to find a project slug. Use doppler_project_get when you already know the slug.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number to return, starting at 1. Example: 2. Default: `1`.
- `per_page` (`integer`, optional): Number of items per page. Defaults to 20. Example: 50. Default: `20`.
- `tags` (`string`, optional): Comma-separated tag slugs. Only projects that have every listed tag are returned. Example: backend,pci

Example input: `{}`

### `doppler_secret_get`

Get Secret Value · Read-only

Get one secret from a Doppler config, including its plaintext value.
Returns the secret name and a value object with the raw value, the computed value (references resolved) and the note. The response contains the secret value in plaintext.
Use doppler_secret_get to read one value. Use doppler_secret_names_list to check whether a secret exists without exposing its value.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `config` (`string`, required): Config name inside the project, from the `name` field returned by doppler_config_list. Root configs are named after their environment slug (dev, stg, prd); branch configs look like dev_personal or prd_aws. Example: prd
- `name` (`string`, required): Name of the secret, from doppler_secret_names_list. Secret names are uppercase by convention. Example: STRIPE_KEY
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend

Example input: `{"config":"<config>","name":"<name>","project":"<project>"}`

### `doppler_secret_list`

List Secrets With Values · Read-only

List the secrets in a Doppler config with their plaintext values, optionally limited to named secrets.
Returns an object keyed by secret name; each entry has the raw value, the computed value (references resolved), the note and the visibility. The response contains secret values in plaintext.
Use doppler_secret_list only when the values are needed. Use doppler_secret_names_list to see names without values, and doppler_secret_get for one secret.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `config` (`string`, required): Config name inside the project, from the `name` field returned by doppler_config_list. Root configs are named after their environment slug (dev, stg, prd); branch configs look like dev_personal or prd_aws. Example: prd
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
- `include_managed_secrets` (`boolean`, optional): Whether to include Doppler's auto-generated secrets (DOPPLER_PROJECT, DOPPLER_ENVIRONMENT, DOPPLER_CONFIG). Defaults to true. Example: false. Default: `true`.
- `secrets` (`string`, optional): Comma-separated secret names to return instead of every secret in the config. Example: STRIPE_KEY,DATABASE_URL

Example input: `{"config":"<config>","project":"<project>"}`

### `doppler_secret_names_list`

List Secret Names · Read-only

List the names of the secrets in a Doppler config, without their values.
Returns an array of secret names only.
Use doppler_secret_names_list to see which secrets exist without exposing values. Use doppler_secret_get or doppler_secret_list only when the values are needed.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `config` (`string`, required): Config name inside the project, from the `name` field returned by doppler_config_list. Root configs are named after their environment slug (dev, stg, prd); branch configs look like dev_personal or prd_aws. Example: prd
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
- `include_managed_secrets` (`boolean`, optional): Whether to include Doppler's auto-generated secrets (DOPPLER_PROJECT, DOPPLER_ENVIRONMENT, DOPPLER_CONFIG). Defaults to true. Example: false. Default: `true`.

Example input: `{"config":"<config>","project":"<project>"}`

### `doppler_service_token_list`

List Service Tokens · Read-only

List the service tokens that have access to a Doppler config. Token values are never returned.
Returns each token's name, slug, config, environment, project, created_at and expires_at.
Use doppler_service_token_list to audit which service tokens can read a config.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `config` (`string`, required): Config name inside the project, from the `name` field returned by doppler_config_list. Root configs are named after their environment slug (dev, stg, prd); branch configs look like dev_personal or prd_aws. Example: prd
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend

Example input: `{"config":"<config>","project":"<project>"}`

### `doppler_workplace_get`

Get Workplace · Read-only

Get the Doppler workplace the connected token belongs to.
Returns the workplace id, name, billing email and security email.
Use doppler_workplace_get for workplace settings. Use doppler_me_get for details about the token itself.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `doppler_config_clone`

Clone Config · Write

Create a new branch config by copying an existing branch config and all of its secrets.
Returns the new config's name, environment, project, root, locked and created_at.
Use doppler_config_clone to duplicate a branch with its secrets. Use doppler_config_create for an empty branch.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `config` (`string`, required): Name of the branch config to copy, from doppler_config_list. Example: prd_aws
- `name` (`string`, required): Name of the new branch config. It must start with the same environment slug and an underscore. Example: prd_aws_copy
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend

Example input: `{"config":"<config>","name":"<name>","project":"<project>"}`

### `doppler_config_create`

Create Branch Config · Write

Create a new empty branch config in a Doppler environment. The branch inherits secrets from the environment's root config.
Returns the new config's name, environment, project, root, locked and created_at.
Use doppler_config_create for an empty branch. Use doppler_config_clone to copy an existing config's secrets into a new branch.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `environment` (`string`, required): Environment slug inside the project, from the `id` field returned by doppler_environment_list. Example: dev
- `name` (`string`, required): Name of the new branch config. It must start with the environment slug and an underscore. Example: prd_aws
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend

Example input: `{"environment":"<environment>","name":"<name>","project":"<project>"}`

### `doppler_config_rename`

Rename Config · Write

Rename an existing Doppler config. A locked config cannot be renamed.
Returns the updated config's name, environment, project, root, locked and created_at.
Use doppler_config_rename to change a config name. Use doppler_config_create or doppler_config_clone for a new config.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `config` (`string`, required): Config name inside the project, from the `name` field returned by doppler_config_list. Root configs are named after their environment slug (dev, stg, prd); branch configs look like dev_personal or prd_aws. Example: prd
- `name` (`string`, required): New name for the config. Branch config names keep the environment slug prefix. Example: prd_gcp
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend

Example input: `{"config":"<config>","name":"<name>","project":"<project>"}`

### `doppler_environment_create`

Create Environment · Write

Create a new environment in a Doppler project. Doppler also creates the environment's root config.
Returns the new environment's id (slug), name, project and created_at.
Use doppler_environment_create for a new environment. Use doppler_environment_rename to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Display name of the new environment. Example: QA
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
- `slug` (`string`, required): Short slug for the new environment, used as its id and as the root config name. Example: qa
- `personal_configs` (`boolean`, optional): Whether to enable personal configs for this environment. Defaults to false. Example: true

Example input: `{"name":"<name>","project":"<project>","slug":"<slug>"}`

### `doppler_environment_rename`

Rename Environment · Write

Change an environment's name, slug or personal-configs setting in a Doppler project.
Returns the updated environment's id (slug), name, project and created_at.
Use doppler_environment_rename to edit an existing environment. Use doppler_environment_create to add one.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `environment` (`string`, required): Environment slug inside the project, from the `id` field returned by doppler_environment_list. Example: dev
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
- `name` (`string`, optional): New display name for the environment. Example: Quality Assurance
- `personal_configs` (`boolean`, optional): Whether to enable personal configs for this environment. Example: true
- `slug` (`string`, optional): New slug for the environment. Example: qa2

Example input: `{"environment":"<environment>","project":"<project>"}`

### `doppler_project_create`

Create Project · Write

Create a new Doppler project. Doppler adds the default environments (dev, stg, prd) and their root configs.
Returns the new project's id, slug, name, description and created_at.
Use doppler_project_create for a new project. Use doppler_project_update to rename or describe an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Name of the new project. Example: payments-api
- `description` (`string`, optional): Optional description of the project. Example: Secrets for the payments service

Example input: `{"name":"<name>"}`

### `doppler_project_update`

Update Project · Write

Rename a Doppler project or change its description.
Returns the updated project's id, name, description and created_at.
Use doppler_project_update to edit an existing project. Use doppler_project_create to add a new one.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `name` (`string`, required): New name for the project. Send the current name to keep it. Example: payments-api-v2
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
- `description` (`string`, optional): New description for the project. Example: Secrets for the payments service

Example input: `{"name":"<name>","project":"<project>"}`

### `doppler_secret_note_update`

Set Secret Note · Write

Set the note on a secret in a Doppler project. The note applies to that secret name in every environment of the project.
Returns the secret name and the saved note.
Use doppler_secret_note_update to document what a secret is for. Use doppler_secret_update to change its value.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `note` (`string`, required): Note text to set on the secret. Example: Rotated quarterly by the payments team
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
- `secret` (`string`, required): Name of the secret to annotate. Example: STRIPE_KEY

Example input: `{"note":"<note>","project":"<project>","secret":"<secret>"}`

### `doppler_secret_update`

Set Secrets · Write

Create or update one or more secrets in a Doppler config. Pass either `secrets` (name to value) or `change_requests` (per-secret changes such as rename, visibility, delete), not both.
Returns every secret in the config after the change, keyed by name, with raw and computed values. The response contains secret values in plaintext.
Use doppler_secret_update to set or change secret values. Use doppler_secret_delete to remove a single secret and doppler_secret_note_update to change a note.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `config` (`string`, required): Config name inside the project, from the `name` field returned by doppler_config_list. Root configs are named after their environment slug (dev, stg, prd); branch configs look like dev_personal or prd_aws. Example: prd
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
- `change_requests` (`array`, optional): Per-secret changes, used instead of `secrets` when you need more than a plain value change. Each item names the secret and sets the new value (null keeps the current value), and can also set its visibility (masked, unmasked or restricted), rename it by giving the old name as originalName, or delete it with shouldDelete true. Optional originalValue or originalVisibility make the change apply only if the secret still has that value or visibility. Example: [{"name": "API_URL", "originalName": "API_HOST", "value": "https://api.example.com", "visibility": "unmasked"}]
- `secrets` (`object`, optional): Secrets to save, as an object mapping each secret name to its new string value. New names are created; existing names are overwritten. Omit it when you use change_requests. Example: {"STRIPE_KEY": "sk_test_123", "LOG_LEVEL": "debug"}

Example input: `{"config":"<config>","project":"<project>"}`

### `doppler_secret_delete`

Delete Secret · Destructive

Permanently delete one secret from a Doppler config.
Returns an empty response on success (HTTP 204).
Use doppler_secret_delete to remove one secret. Use doppler_secret_update with change_requests to delete or change several secrets in one call.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `config` (`string`, required): Config name inside the project, from the `name` field returned by doppler_config_list. Root configs are named after their environment slug (dev, stg, prd); branch configs look like dev_personal or prd_aws. Example: prd
- `name` (`string`, required): Name of the secret to delete, from doppler_secret_names_list. Example: OLD_API_KEY
- `project` (`string`, required): Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend

Example input: `{"config":"<config>","name":"<name>","project":"<project>"}`

## Related

Other Developer Tools connectors ([all 200](/agentkit/connectors/?category=developer-tools)):

- [GitHub](/agentkit/connectors/github/): Scalekit connector, OAuth, 217 tools
- [Datadog](/agentkit/connectors/datadog/): Scalekit connector, API key, 105 tools
- [Linear](/agentkit/connectors/linear/): Scalekit connector, OAuth, 64 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
