Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
This node operation removes a member from a specified project. It is useful in scenarios where you need to manage project team members by revoking access or removing users who no longer should be part of the project. For example, if a user leaves an organization or changes roles, this operation can be used to remove their membership from the project to maintain proper access control.
Properties
| Name | Meaning |
|---|---|
| userId | The unique identifier of the member (user) to remove from the project. |
| project | The identifier of the project from which the member will be removed. Defaults to "default". |
Output
The output JSON contains the response from the API after attempting to remove the member. Typically, this would include confirmation of successful removal or error details if the operation failed. There is no binary data output 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
projectanduserIdparameters must be provided to correctly target the member to remove.
Troubleshooting
- Missing or invalid userId: If the
userIdis not provided or incorrect, the API will likely return an error indicating that the member could not be found. Ensure the correct user ID is supplied. - Invalid project identifier: Providing a non-existent or unauthorized project ID may cause errors. Verify the project exists and the API key has permissions.
- Authentication errors: If the API key credential is missing or invalid, authentication will fail. Check the credential configuration.
- Permission issues: The authenticated user must have sufficient rights to remove members from the project; otherwise, the request will be denied.
- Network or API availability: Network issues or API downtime can cause failures. Retry or check service status if persistent.
Links and References
- MsgCore API Documentation (generic reference, replace with actual URL)
- n8n documentation on HTTP Request Node for understanding how API calls are made within n8n nodes.