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
Integration → Delete
AI-generatedOverview
This node interacts with the Doppler API to manage integrations within a Doppler account. Specifically, for the "Integration" resource and the "Delete" operation, it deletes an existing integration identified by its slug. This is useful when you want to programmatically remove integrations that are no longer needed or valid in your Doppler environment.
Practical examples include:
- Automating cleanup of unused integrations as part of a CI/CD pipeline.
- Managing integrations dynamically based on project lifecycle events.
- Removing compromised or deprecated integrations to maintain security hygiene.
Properties
| Name | Meaning |
|---|---|
| Integration Slug | The unique identifier (slug) of the integration to delete. This specifies which integration will be removed. |
Output
The node outputs the JSON response from the Doppler API after attempting to delete the specified integration. Typically, this will confirm whether the deletion was successful or provide error details if it 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:
https://api.doppler.com/v3/integrations/integration. - Proper configuration of the API key credential in n8n is necessary for authorization.
Troubleshooting
Common issues:
- Invalid or missing integration slug: The API call will fail if the integration slug is not provided or incorrect.
- Authentication errors: If the API key credential is invalid or expired, the request will be unauthorized.
- Network connectivity problems can prevent reaching the Doppler API.
Error messages:
- Unauthorized (401): Check that the API key credential is correctly configured and has sufficient permissions.
- Not Found (404): The specified integration slug does not exist; verify the slug value.
- Bad Request (400): Possibly due to malformed parameters; ensure the integration slug is properly URL encoded.
Resolving these typically involves verifying input values, ensuring valid credentials, and checking network access.
Links and References
- Doppler API Documentation (for detailed API usage and error codes)
- n8n Documentation (for configuring credentials and using HTTP request nodes)