Doppler

Doppler is a universal secrets management platform and configuration management system designed to help development teams securely store, manage, and synchronize environment variables, application secrets, API keys, database credentials, and other sensitive configuration data across their entire infrastructure and development lifecycle. Organizations use Doppler to centralize secrets management, eliminate hardcoded credentials, prevent secrets sprawl, and maintain secure configuration across development, staging, and production environments.

Category	Secrets management
Direction	Query source
Sign-in	Doppler Token
Query languages	SQLite
Tables	7
Query templates	29
Website	Doppler.com

Before you start

Huntbase signs in to Doppler with Doppler Token. Create the credential in Doppler first, then keep it to hand for the Connect step.

1. In the Doppler dashboard, open the project and select the config you want to read.
2. Click the Access tab, then click Generate.
3. Enter a name for the token. Leave write access off, and optionally set an expiration date.
4. Click Generate Service Token and copy the token. It is only shown once.

Permissions:

• Read access (the default for a service token). Write access is not needed.

Watch out for

• A service token only grants access to one config within one project. Use a personal token if you need wider access.

For the vendor's own instructions, see Doppler service token documentation.

tip

Use a dedicated, read-only credential for Huntbase where the product allows it. Huntbase only needs to read.

Connect Doppler

1. Go to Connections and click New connection, or click New connection on the Doppler product page.
2. On Product, pick Doppler and choose the Owner.
3. On Details, give the connection a Name and, optionally, a Description.
4. On Connect, fill in the settings and credentials described below.
5. On Verify, review the summary and click Create & check.

For everything else on the setup page — saving a draft, I'll do this later, and what each check result means — see Connections.

Settings

Where your Doppler lives:

Field	Required	Notes
Project ID	Yes	The ID of the Doppler project to query, such as example-project.

Credentials

The only Method is Doppler Token. Enter a Credential label (for example Production), then fill in:

Field	Required	Notes
Doppler Token	Yes	A personal token (starts with dp.pt.) or a service token (starts with dp.st.). Secret — not shown again after you save it.

Query it

Once connected, Doppler can serve these languages in a query tab, and Scout can use it when you ask in Auto:

Language	Use it for
SQLite	SQL over the 7 tables listed below, alongside every other connected source.

Example: SQLite

Doppler Projects Basic Info — List all Doppler projects with their creation dates, unique identifiers, slugs, and descriptions.

select
  id,
  name,
  created_at,
  slug,
  description
from
  doppler_project;

Doppler ships with 29 query templates. Find them in Library › Queries — see Query templates.

Tables

Doppler adds 7 tables. Browse their columns from Schema in the query bar's ⋯ menu.

All 7 tables

Table	Contains
doppler_activity_log	Doppler Activity Log
doppler_config	Doppler config refer to the configuration files that define the settings, parameters, and environment variables used by your application or service
doppler_environment	Doppler Environment
doppler_project	A Doppler project defines app config and secrets for one service or app.
doppler_secret	CREATE TABLE IF NOT EXISTS doppler_secret (
doppler_service_token	Doppler Service Token
doppler_user	Doppler User

Next steps

• Connections — health, credentials and settings after you connect
• Query languages — syntax, parameters and time ranges
• Chatting with Scout — ask questions without writing a query
• All integrations — the rest of the catalog