Doppler

Overview

This node interacts with the Doppler API to manage project members among other resources. Specifically, for the "Project Member" resource and the "Delete" operation, it deletes a member from a specified project. This is useful in scenarios where you need to programmatically remove users or collaborators from a project within Doppler, such as when revoking access or cleaning up project membership.

Practical example: If a team member leaves an organization or no longer requires access to a project’s secrets and configurations, this node can be used to automate their removal from the project members list.

Properties

Note: Although the provided properties JSON only lists "Project", the actual deletion of a project member requires additional parameters (type and user_slug) to identify the member uniquely, as indicated by the URL pattern in the source code routing:

/v3/projects/project/members/member/{{ encodeURIComponent($parameter.type) }}/{{ encodeURIComponent($parameter.user_slug) }}

These two parameters are essential to specify the type of member and the user slug to delete the correct member.

Output

The node outputs the response from the Doppler API after attempting to delete the project member. The output is in JSON format and typically contains confirmation of the deletion or error details if the operation failed.

No binary data output is involved in this operation.

Dependencies

• Requires an API key credential for authenticating with the Doppler API.
• The node uses the Doppler API base URL: https://api.doppler.com.
• Proper permissions on the API key are necessary to delete project members.

Troubleshooting

• Missing Parameters: If type or user_slug parameters are not provided, the API call will fail because the endpoint requires these to identify the member to delete.
• Authentication Errors: Ensure that the API key credential is valid and has sufficient permissions.
• Not Found Errors: If the specified project or member does not exist, the API will return an error indicating the resource was not found.
• Permission Denied: The API key might lack rights to delete members; verify roles and permissions in Doppler.
• URL Encoding Issues: Parameters must be properly URL encoded; incorrect encoding may cause request failures.

Links and References

• Doppler API Documentation
• Doppler Projects API

If you want, I can help generate a more detailed property table including the required type and user_slug parameters based on the routing URLs seen in the source code.