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 interacts with the Doppler API to manage configurations within a specified project. Specifically, for the "Config" resource and the "List" operation, it retrieves a list of all configuration sets associated with a given project. This is useful when you want to programmatically fetch all configuration profiles available in a Doppler project, for example, to audit configurations, synchronize them with other systems, or display them in a dashboard.
Practical examples:
- Automatically retrieving all configs in a project to back them up.
- Listing configs to verify which environments or setups exist before deploying changes.
- Integrating Doppler config lists into CI/CD pipelines for validation or reporting.
Properties
| Name | Meaning |
|---|---|
| Project | The identifier (name or slug) of the Doppler project whose configurations you want to list. |
Output
The node outputs JSON data representing the list of configurations retrieved from the Doppler API for the specified project. Each item in the output typically corresponds to a configuration object containing details such as configuration name and metadata.
No binary data output is involved in 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/with the project query parameter. - Ensure that the Doppler API key credential is properly configured in n8n for successful authentication.
Troubleshooting
- Empty or no results: Verify that the project name provided is correct and that the project contains configurations.
- Authentication errors: Check that the API key credential is valid and has sufficient permissions to access the project's configurations.
- Network or API errors: Confirm network connectivity and Doppler API availability.
- Incorrect property usage: Make sure the "Project" property is set when listing configs; otherwise, the request may fail or return unexpected results.