Integration · Security and identity
AI agents for Doppler
Manage secrets in Doppler: list projects and their configs (environments), list secret names, read a secret's value, set or change secrets, add notes and delete secrets, with a Doppler service token.
- Actions
- 8
- Read
- 5
- Write
- 3
Actions
What your agents can do in Doppler
Manage secrets in Doppler: list projects and their configs (environments), list secret names, read a secret's value, set or change secrets, add notes and delete secrets, with a Doppler service token (one config) or a service account or personal token (many).
Read 5
Look things up. Nothing changes.
List projects
Lists the workplace's projects the token can see, as projects: each with its slug (use it as the project), name, description and created_at.
List configs
Lists a project's configs (dev, stg, prd and their branch configs), as configs.
List secret names
Lists the names of the secrets in a config, as names, without their values.
Read a secret
Reads one secret's value from a config: value.raw (as typed, with references like ${OTHER} unresolved), value.computed (references resolved; what apps receive), value.note and the visibility.
Read several secrets
Reads the named secrets of a config (or all of them when no names are given), as secrets: a map from each name to its raw, computed and note.
Write 3
Create, change or send.
Set secrets
Creates or changes one or more secrets in a config in one change, like {"STRIPE_API_KEY": "sk_live_…", "LOG_LEVEL": "info"}; secrets not named are left alone.
Set a secret's note
Sets the note shown beside a secret in the Doppler dashboard (what it is for, who owns it, how to rotate it).
Delete a secretDeletes data
Deletes one secret from a config.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Doppler account.
What you enter
- Token
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Doppler data
Ask a question in plain words. The agent can list projects, list configs or list secret names in Doppler, then answers with what it found.
- 02
Let an agent update Doppler
Have the agent set secrets or set a secret's note in Doppler as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Doppler and Slack: it can list projects in Doppler and post a summary to a Slack channel in the same run.
FAQ
Doppler and MyDeepAgents
Can MyDeepAgents connect to Doppler?
Yes. The Doppler connector has 8 actions: 5 read and 3 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Doppler?
Paste an API key from your Doppler account. You'll need: Token. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Doppler without asking?
Only if you let it. Each of the 3 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Doppler in workflows as well as agents?
Yes. Every Doppler action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Doppler to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.