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.
- Tools
- 26
- What they doRead · write · destructive
- 16 · 9 · 116 read9 write1 destructive
- Users sign in with
- Access token
Setup
Install the SDK
Terminal window npm install @scalekit-sdk/node dotenvTerminal window pip install scalekit-sdk-python python-dotenvSet your credentials
Add your Scalekit credentials to your
.envfile. Find values in app.scalekit.com > Developers > API Credentials..env SCALEKIT_ENVIRONMENT_URL=<your-environment-url>SCALEKIT_CLIENT_ID=<your-client-id>SCALEKIT_CLIENT_SECRET=<your-client-secret>Create the Doppler connection
In AgentKit > Connections, create a Doppler connection. The name you give it is the
connection_nameyour code passes. See Configure connections.Authorize a user and make your first call
quickstart.mts 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.actionsconst connector = 'doppler'const identifier = 'user_123'// Generate an authorization link for the userconst { 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 callconst result = await actions.executeTool({connector,identifier,toolName: 'doppler_activity_log_list',toolInput: {},})console.log(result)Terminal window npx tsx quickstart.mtsquickstart.py import osfrom scalekit import ScalekitClientfrom dotenv import load_dotenvload_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.actionsconnection_name = "doppler"identifier = "user_123"# Generate an authorization link for the userlink_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 callresult = actions.execute_tool(tool_input={},tool_name="doppler_activity_log_list",connection_name=connection_name,identifier=identifier,)print(result)Terminal window python quickstart.pyEach user opens the link once and enters their Doppler credentials there. See Authorize a user for the full flow and statuses.
Tools
Pass the exact name toexecute_tooldoppler_activity_log_getGet one entry from the Doppler workplace activity log by ID.Read-onlyGet Activity Log
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.
Inputs
logstringrequired- ID of the activity log entry, from the `id` field returned by doppler_activity_log_list. Example: emwk7ra70oem3xa
doppler_activity_log_listList the activity log for the whole Doppler workplace, newest first, one page at a time.Read-onlyList Activity Logs
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.
Inputs
pageinteger- Page number to return, starting at 1. Example: 2default
1 per_pageinteger- Number of items per page. Defaults to 20. Example: 50default
20
doppler_config_getGet one config in a Doppler project by name.Read-onlyGet Config
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.
Inputs
configstringrequired- 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
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
doppler_config_listList the configs in a Doppler project, optionally only those in one environment.Read-onlyList Configs
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.
Inputs
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
environmentstring- Environment slug inside the project, from the `id` field returned by doppler_environment_list. Example: dev
pageinteger- Page number to return, starting at 1. Example: 2default
1 per_pageinteger- Number of items per page. Defaults to 20. Example: 50default
20
doppler_config_log_getGet one change in a Doppler config's history, including the secret diff.Read-onlyGet Config Log
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.
Inputs
configstringrequired- 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
logstringrequired- ID of the config log, from the `id` field returned by doppler_config_log_list. Example: WaRMMyxHUg4lOKR
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
doppler_config_log_listList the change history of a Doppler config, newest first, one page at a time.Read-onlyList Config Logs
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.
Inputs
configstringrequired- 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
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
pageinteger- Page number to return, starting at 1. Example: 2default
1 per_pageinteger- Number of items per page. Defaults to 20. Example: 50default
20
doppler_environment_getGet one environment in a Doppler project by its slug.Read-onlyGet Environment
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.
Inputs
environmentstringrequired- Environment slug inside the project, from the `id` field returned by doppler_environment_list. Example: dev
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
doppler_environment_listList the environments in a Doppler project.Read-onlyList Environments
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.
Inputs
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
doppler_me_getGet details about the Doppler token used for this connection.Read-onlyGet Token Info
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.
Inputs
This tool takes no inputs.
doppler_project_getGet one Doppler project by its slug.Read-onlyGet Project
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.
Inputs
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
doppler_project_listList the projects in the Doppler workplace, one page at a time, optionally filtered by tags.Read-onlyList Projects
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.
Inputs
pageinteger- Page number to return, starting at 1. Example: 2default
1 per_pageinteger- Number of items per page. Defaults to 20. Example: 50default
20 tagsstring- Comma-separated tag slugs. Only projects that have every listed tag are returned. Example: backend,pci
doppler_secret_getGet one secret from a Doppler config, including its plaintext value.Read-onlyGet Secret Value
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.
Inputs
configstringrequired- 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
namestringrequired- Name of the secret, from doppler_secret_names_list. Secret names are uppercase by convention. Example: STRIPE_KEY
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
doppler_secret_listList the secrets in a Doppler config with their plaintext values, optionally limited to named secrets.Read-onlyList Secrets With Values
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.
Inputs
configstringrequired- 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
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
include_managed_secretsboolean- Whether to include Doppler's auto-generated secrets (DOPPLER_PROJECT, DOPPLER_ENVIRONMENT, DOPPLER_CONFIG). Defaults to true. Example: falsedefault
true secretsstring- Comma-separated secret names to return instead of every secret in the config. Example: STRIPE_KEY,DATABASE_URL
doppler_secret_names_listList the names of the secrets in a Doppler config, without their values.Read-onlyList Secret Names
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.
Inputs
configstringrequired- 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
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
include_managed_secretsboolean- Whether to include Doppler's auto-generated secrets (DOPPLER_PROJECT, DOPPLER_ENVIRONMENT, DOPPLER_CONFIG). Defaults to true. Example: falsedefault
true
doppler_service_token_listList the service tokens that have access to a Doppler config.Read-onlyList Service Tokens
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.
Inputs
configstringrequired- 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
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
doppler_workplace_getGet the Doppler workplace the connected token belongs to.Read-onlyGet Workplace
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.
Inputs
This tool takes no inputs.
doppler_config_cloneCreate a new branch config by copying an existing branch config and all of its secrets.WriteClone Config
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.
Inputs
configstringrequired- Name of the branch config to copy, from doppler_config_list. Example: prd_aws
namestringrequired- Name of the new branch config. It must start with the same environment slug and an underscore. Example: prd_aws_copy
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
doppler_config_createCreate a new empty branch config in a Doppler environment.WriteCreate Branch Config
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.
Inputs
environmentstringrequired- Environment slug inside the project, from the `id` field returned by doppler_environment_list. Example: dev
namestringrequired- Name of the new branch config. It must start with the environment slug and an underscore. Example: prd_aws
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
doppler_config_renameRename an existing Doppler config.WriteRename Config
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.
- Idempotent
Inputs
configstringrequired- 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
namestringrequired- New name for the config. Branch config names keep the environment slug prefix. Example: prd_gcp
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
doppler_environment_createCreate a new environment in a Doppler project.WriteCreate Environment
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.
Inputs
namestringrequired- Display name of the new environment. Example: QA
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
slugstringrequired- Short slug for the new environment, used as its id and as the root config name. Example: qa
personal_configsboolean- Whether to enable personal configs for this environment. Defaults to false. Example: true
doppler_environment_renameChange an environment's name, slug or personal-configs setting in a Doppler project.WriteRename Environment
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.
- Idempotent
Inputs
environmentstringrequired- Environment slug inside the project, from the `id` field returned by doppler_environment_list. Example: dev
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
namestring- New display name for the environment. Example: Quality Assurance
personal_configsboolean- Whether to enable personal configs for this environment. Example: true
slugstring- New slug for the environment. Example: qa2
doppler_project_createCreate a new Doppler project.WriteCreate Project
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.
Inputs
namestringrequired- Name of the new project. Example: payments-api
descriptionstring- Optional description of the project. Example: Secrets for the payments service
doppler_project_updateRename a Doppler project or change its description.WriteUpdate Project
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.
- Idempotent
Inputs
namestringrequired- New name for the project. Send the current name to keep it. Example: payments-api-v2
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
descriptionstring- New description for the project. Example: Secrets for the payments service
doppler_secret_note_updateSet the note on a secret in a Doppler project.WriteSet Secret Note
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.
- Idempotent
Inputs
notestringrequired- Note text to set on the secret. Example: Rotated quarterly by the payments team
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
secretstringrequired- Name of the secret to annotate. Example: STRIPE_KEY
doppler_secret_updateCreate or update one or more secrets in a Doppler config.WriteSet Secrets
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.
Inputs
configstringrequired- 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
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
change_requestsarray- 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"}]
secretsobject- 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"}
doppler_secret_deletePermanently delete one secret from a Doppler config.DestructiveDelete Secret
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.
- Idempotent
Inputs
configstringrequired- 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
namestringrequired- Name of the secret to delete, from doppler_secret_names_list. Example: OLD_API_KEY
projectstringrequired- Project identifier: the project's slug (its `slug` from doppler_project_list, usually the lowercase project name). Example: backend
No tools match.