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 interacts with the Doppler API to retrieve configuration logs for a specified project and configuration. Specifically, the "Config Log" resource with the "Retrieve" operation fetches details of a single configuration log entry identified by its Log ID. This is useful for auditing changes or reviewing historical configuration states within a project.
Common scenarios include:
- Auditing configuration changes in a project.
- Debugging issues by examining specific config log entries.
- Tracking who made changes and when in a configuration.
Example: Retrieve a specific configuration log entry by providing the project name, configuration name, and the log ID to get detailed information about that change.
Properties
| Name | Meaning |
|---|---|
| Project | The name or identifier of the project containing the configuration. |
| Config | The name or identifier of the configuration whose log is being retrieved. |
| Log ID | The unique identifier of the specific configuration log entry to retrieve. |
Output
The node outputs JSON data representing the details of the requested configuration log entry. This typically includes metadata such as timestamps, user information, and the changes made in that log entry.
No binary data output is indicated 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
https://api.doppler.com/v3/configs/config/logs/log. - Proper network access to Doppler's API service is necessary.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key credential is correctly configured and has sufficient permissions.
- Incorrect Project, Config, or Log ID values: Verify that the provided identifiers exist and are correctly spelled/encoded.
- Network connectivity issues: Confirm that the n8n instance can reach the Doppler API endpoint.
- API rate limits or errors: Check Doppler API usage limits and error messages returned; handle retries or backoff accordingly.
Common error messages might include 404 Not Found if the log ID does not exist, or 401 Unauthorized if authentication fails.
Links and References
- Doppler API Documentation (general reference for API endpoints)
- Doppler Configuration Logs (for understanding config logs conceptually)