Skip to content
Scalekit Docs
Talk to an Engineer Dashboard

Connect AI agents to Doppler

Scalekit connector
Open markdown

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

Setup

  1. Install the SDK

    Terminal window
    npm install @scalekit-sdk/node dotenv
  2. Set your credentials

    Add your Scalekit credentials to your .env file. 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>
  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.

  4. 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.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)
    Terminal window
    npx tsx quickstart.mts

    Each 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 to execute_tool
Try in PlaygroundRequest a tool
  • doppler_activity_log_getGet one entry from the Doppler workplace activity log by ID.Read-only

    Get 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-only

    List 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-only

    Get 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-only

    List 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-only

    Get 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-only

    List 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-only

    Get 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-only

    List 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