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 within projects and configurations. Specifically, for the Secret - Delete operation, it allows users to delete a secret from a specified project and configuration. This is useful in scenarios where sensitive information such as API keys, passwords, or tokens need to be removed securely from a configuration.
Practical examples include:
- Removing outdated or compromised secrets from a project's configuration.
- Cleaning up secrets that are no longer needed after a deployment.
- Automating secret lifecycle management by deleting secrets programmatically.
Properties
| Name | Meaning |
|---|---|
| Project | The identifier of the project containing the secret to delete. |
| Config | The name of the configuration within the project where the secret resides. |
| Secret Name | The exact name of the secret to be deleted from the specified project and configuration. |
Output
The node outputs JSON data representing the response from the Doppler API after attempting to delete the secret. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Doppler API.
- The node sends HTTP DELETE requests to the Doppler API endpoint
/v3/configs/config/secretwith query parameters specifying the project, config, and secret name. - No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common Issues:
- Providing incorrect project, config, or secret name values may result in failure to find or delete the secret.
- Insufficient permissions associated with the API key can cause authorization errors.
- Network connectivity issues can prevent communication with the Doppler API.
Common Error Messages:
- 404 Not Found: The specified secret does not exist in the given project/configuration. Verify the names are correct.
- 401 Unauthorized: Authentication failed due to invalid or missing API credentials. Check the API key setup.
- 400 Bad Request: Missing required parameters or malformed request. Ensure all required properties are set correctly.
Resolving these typically involves verifying input property values, ensuring valid API credentials, and checking network access.
Links and References
- Doppler API Documentation (for detailed API endpoints and usage)
- n8n Documentation (for general guidance on using HTTP request nodes and credentials)