Actions35
- Secret Actions
- Workplace Actions
- Workplace User Actions
- Workplace Role Actions
- Activity Log Actions
- Project Actions
- Project Role Actions
- Project Member Actions
- Config Actions
- Config Log Actions
- Environment Actions
- Trusted IP Actions
- Integration Actions
- Auth Actions
- Share Actions
Overview
This node integrates with the Doppler API to manage secrets and other related resources within Doppler projects. Specifically, for the Secret - Retrieve operation, it fetches the details of a specific secret from a given project and configuration. This is useful when you need to programmatically access secret values stored in Doppler for use in automation workflows, deployments, or secure environment setups.
Practical examples include:
- Retrieving API keys or credentials securely stored in Doppler before deploying an application.
- Accessing environment-specific secrets dynamically during CI/CD pipelines.
- Auditing or verifying secret values without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Project | The identifier (name or slug) of the Doppler project where the secret resides. |
| Config | The name of the configuration within the project that contains the secret. |
| Secret Name | The exact name of the secret to retrieve from the specified project and configuration. |
Output
The node outputs JSON data representing the retrieved secret's details as returned by the Doppler API. This typically includes the secret's value and metadata such as creation date, last updated timestamp, and any associated notes.
If the secret contains binary data, it would be represented accordingly, but this node primarily deals with textual secret values.
Dependencies
- Requires an active Doppler API key credential configured in n8n to authenticate requests.
- Network access to
https://api.doppler.comis necessary. - No additional external dependencies beyond the Doppler API and n8n credential setup.
Troubleshooting
Common Issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect project, config, or secret name parameters may result in "Not Found" errors.
- Network connectivity issues can prevent successful API calls.
Error Messages:
- 401 Unauthorized: Check that the API key credential is correctly set and has sufficient permissions.
- 404 Not Found: Verify that the project, config, and secret names are correct and exist in Doppler.
- 429 Too Many Requests: You may be hitting Doppler API rate limits; consider adding delays or retries.