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 update a specific user within a workplace. It allows modifying the access level (role) of a user identified by their unique slug. This is useful in scenarios where you need to programmatically manage user permissions or roles within a workplace environment, such as promoting a collaborator to an owner or adjusting access rights based on project needs.
Practical examples:
- Automatically updating user roles when onboarding new team members.
- Changing access levels during role transitions without manual intervention.
- Integrating with HR systems to sync workplace user permissions.
Properties
| Name | Meaning |
|---|---|
| The Slug of the User | The unique identifier (slug) of the user to update within the workplace. |
| Access | The identifier of the workplace role to assign to the user, e.g., owner, collaborator, etc. |
Output
The node outputs JSON data representing the updated workplace user object returned from the Doppler API after the PATCH request. This typically includes details about the user and their updated access level within the workplace.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Doppler API.
- The node sends HTTP PATCH requests to the Doppler API endpoint
/v3/workplace/users/{user_slug}. - Proper configuration of the API base URL (
https://api.doppler.com) and authentication headers is necessary.
Troubleshooting
Common issues:
- Invalid or missing user slug will cause the API to fail to locate the user.
- Providing an invalid access role identifier may result in an error or no change.
- Network or authentication errors if the API key is incorrect or expired.
Error messages:
- "User not found" — Verify the user slug is correct.
- "Unauthorized" or "Authentication failed" — Check that the API key credential is valid and has required permissions.
- "Invalid access role" — Ensure the access value corresponds to a valid workplace role identifier.
Resolving these usually involves verifying input parameters and ensuring the API credentials are correctly set up.
Links and References
- Doppler API Documentation (for workplace user management endpoints)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes