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 retrieve information about a specific workplace role within a Doppler workplace. It is useful when you need to fetch details about a particular role, such as its permissions or metadata, in order to manage user access or audit roles programmatically.
Common scenarios include:
- Automating role management workflows by retrieving role details before updating or deleting them.
- Integrating Doppler workplace role data into other systems for reporting or synchronization.
- Validating role existence and properties during deployment or configuration processes.
Example: Retrieve the details of the "admin" role in your Doppler workplace to check its permissions before assigning it to a new user.
Properties
| Name | Meaning |
|---|---|
| Role | The identifier (slug) of the workplace role to retrieve. For example, "owner", "collaborator", or any custom role slug defined in the Doppler workplace. |
Output
The node outputs JSON data representing the retrieved workplace role's details. This typically includes all relevant information about the role as returned by the Doppler API, such as its name, permissions, and other metadata.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Doppler API.
- The node makes HTTP GET requests to the Doppler API endpoint
/v3/workplace/roles/role/{role}, where{role}is URL-encoded from the input property. - Ensure that the Doppler API key has sufficient permissions to read workplace role information.
Troubleshooting
- Role Not Found: If the specified role does not exist, the API will likely return a 404 error. Verify the role slug spelling and existence in the Doppler workplace.
- Authentication Errors: If the API key is invalid or lacks permissions, authentication errors will occur. Confirm the API key validity and scopes.
- Network Issues: Connectivity problems can cause request failures. Check network access to
api.doppler.com. - Empty Role Property: If the "Role" property is left empty, the request URL will be malformed, causing errors. Always specify a valid role slug.
Links and References
- Doppler API Documentation
- Doppler Workplace Roles API Endpoint (for detailed API response structure)