Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
The "Remove Member" operation in the Members resource allows you to remove a user from a specified project. This is useful for managing project team members by revoking their access or membership when they no longer need to be part of the project. For example, if a team member leaves an organization or changes roles, this operation can be used to cleanly remove their membership from the project.
Properties
| Name | Meaning |
|---|---|
| userId | The unique identifier of the user/member to remove from the project. |
| project | The identifier of the project from which the member will be removed. Defaults to "default". |
Output
The output of this operation typically contains the response from the API indicating the success or failure of the removal request. The json output field will include details such as confirmation of removal or error messages if the operation failed. There is no indication that binary data is returned for this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests.
- The node makes HTTP DELETE requests to the endpoint
/api/v1/projects/{project}/members/{userId}. - The
projectparameter must correspond to an existing project identifier. - The
userIdmust be a valid member ID within the specified project.
Troubleshooting
- Common issues:
- Providing an invalid or non-existent
userIdwill result in an error indicating the member could not be found. - Using an incorrect
projectidentifier may cause the API to return a "project not found" or similar error. - Missing or invalid API credentials will prevent successful authentication and cause authorization errors.
- Providing an invalid or non-existent
- Error messages:
- 404 Not Found: The specified user or project does not exist. Verify the
userIdandprojectvalues. - 401 Unauthorized: Authentication failed due to missing or invalid API key. Check your credential configuration.
- 403 Forbidden: The authenticated user does not have permission to remove members from the project. Ensure proper permissions.
- 404 Not Found: The specified user or project does not exist. Verify the
- To resolve these errors, verify all input parameters, ensure correct API credentials are set up, and confirm that the authenticated user has sufficient rights.
Links and References
- GateKit API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding how API calls are made within n8n nodes