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 various resources related to projects, environments, secrets, configurations, and more. Specifically, for the Environment resource with the Delete operation, it deletes an environment within a specified project.
Use cases include automating environment cleanup in your Doppler projects, such as removing outdated or unused environments programmatically as part of CI/CD pipelines or infrastructure management workflows.
Example: Automatically delete a staging environment after deployment tests complete successfully.
Properties
| Name | Meaning |
|---|---|
| Project | The identifier (string) of the project that contains the environment to delete. |
| Environment | The identifier (string) of the environment to be deleted within the specified project. |
Output
The node outputs JSON data representing the response from the Doppler API after attempting to delete the environment. Typically, this will confirm successful deletion or provide error details if the operation failed.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Doppler API.
- The node sends HTTP DELETE requests to the Doppler API endpoint
/v3/environments/environment. - The base URL for the API is
https://api.doppler.com. - Proper configuration of the API key credential in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing project or environment identifiers can cause the API to reject the request.
- Insufficient permissions associated with the API key may prevent deletion.
- Network connectivity problems can cause request failures.
Error messages:
- "404 Not Found" — The specified project or environment does not exist. Verify the identifiers.
- "401 Unauthorized" — Authentication failed. Check the API key credential.
- "403 Forbidden" — The API key lacks permission to delete the environment. Ensure proper access rights.
- "400 Bad Request" — Possibly malformed parameters; ensure all required fields are correctly set.
Resolving these typically involves verifying input parameters, checking API credentials, and ensuring network access.
Links and References
- Doppler API Documentation (for detailed API endpoints and usage)
- n8n Documentation (for general node usage and credential setup)