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 project roles within a Doppler project. Specifically, the "Delete" operation for the "Project Role" resource allows users to delete a specified project role by its identifier. This is useful in scenarios where you need to remove obsolete or unnecessary roles from your project's access control settings.
Practical examples include:
- Automating cleanup of project roles that are no longer needed.
- Integrating role management into CI/CD pipelines to maintain security hygiene.
- Removing roles as part of user offboarding processes.
Properties
| Name | Meaning |
|---|---|
| Role | The identifier (slug) of the project role to delete. |
Output
The node outputs the JSON response returned by the Doppler API after attempting to delete the specified project role. Typically, this will be an empty object or a confirmation message indicating successful deletion. 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/projects/roles/role/{role}, where{role}is URL-encoded. - Ensure the n8n workflow has the appropriate Doppler API credentials configured.
Troubleshooting
Common issues:
- Providing an invalid or non-existent role identifier will likely result in an error from the API.
- Missing or incorrect API authentication credentials will cause authorization failures.
- Network connectivity issues can prevent the request from reaching the Doppler API.
Error messages and resolutions:
- 404 Not Found: The specified role does not exist. Verify the role identifier is correct.
- 401 Unauthorized: Authentication failed. Check that the API key credential is valid and properly configured.
- 400 Bad Request: The request parameters may be malformed. Confirm the role parameter is correctly set.
- Network errors: Check internet connection and firewall settings.
Links and References
- Doppler API Documentation
- Doppler Project Roles API (for detailed info on managing project roles)