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
The node integrates with the Doppler API to manage secrets within projects and configurations. Specifically, the "Secret" resource with the "List Names" operation allows users to retrieve a list of secret names associated with a specified project and configuration. This is useful for scenarios where you want to quickly enumerate all secret keys available in a given context without fetching their values.
Practical examples include:
- Auditing or inventorying all secret names in a project/configuration.
- Dynamically generating dropdowns or selection lists based on existing secret names.
- Preparing for bulk operations by first listing all secret identifiers.
Properties
| Name | Meaning |
|---|---|
| Project | The identifier of the project from which to list secret names. |
| Config | The specific configuration within the project to target when listing secret names. |
Output
The output JSON contains an array of secret names (strings) corresponding to the secrets available under the specified project and configuration. Each item represents the name/key of a secret without revealing its value or other metadata.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for authenticating with the Doppler API.
- The node makes HTTP GET requests to the Doppler API endpoint
/v3/configs/config/secrets/names. - No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Empty Result: If no secret names are returned, verify that the
ProjectandConfigproperties are correctly set and correspond to existing resources in Doppler. - Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to access the project's secrets.
- Invalid Parameters: The API expects URL-encoded strings for
projectandconfig. Make sure these inputs do not contain invalid characters or are empty if required. - Network Issues: Check connectivity to
https://api.doppler.comand ensure no firewall or proxy blocks the request.
Links and References
- Doppler API Documentation (for the endpoint to list secret names)
- n8n HTTP Request Node Documentation (general info on making API calls in n8n)