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 workplace roles. Specifically, for the Workplace Role resource and the Delete operation, it deletes a specific role within a workplace. This is useful in scenarios where you need to programmatically remove roles that are no longer needed or valid, such as cleaning up outdated permissions or managing user access dynamically.
Practical example:
If your organization uses Doppler to manage workplace roles and you want to automate the removal of a role named "contractor" when a contract ends, this node can be configured to delete that role automatically.
Properties
| Name | Meaning |
|---|---|
| Role | The identifier (slug) of the workplace role to delete. For example, "admin", "developer", or any custom role slug defined in your Doppler workplace. |
Output
The node outputs the response from the Doppler API after attempting to delete the specified workplace role. The output is structured as JSON data representing the result of the deletion request. Typically, this will confirm successful deletion or provide error details if the deletion failed.
There is no binary data output associated with this operation.
Dependencies
- Requires an active connection to the Doppler API.
- Requires an API authentication token credential configured in n8n to authorize requests to Doppler.
- The node sends HTTP DELETE requests to the Doppler API endpoint
/v3/workplace/roles/role/{role}, where{role}is URL-encoded.
Troubleshooting
Common issues:
- Attempting to delete a role that does not exist will likely result in an error response from the API.
- Insufficient permissions or invalid API credentials will cause authorization errors.
- Network connectivity issues may prevent the node from reaching the Doppler API.
Error messages and resolutions:
- 404 Not Found: The specified role does not exist. Verify the role name is correct.
- 401 Unauthorized or 403 Forbidden: Check that the API key credential is valid and has sufficient permissions.
- Network errors/timeouts: Ensure network connectivity and that the Doppler API is reachable.
Links and References
- Doppler API Documentation (for detailed API endpoints and authentication)
- n8n Documentation (for general usage of HTTP request nodes and credential setup)