Actions7
Overview
This node operation removes one or more users from a specified group via an API call. It is useful in scenarios where you need to manage group memberships dynamically, such as automating user access control, cleaning up group members, or synchronizing group membership with external systems.
For example, if you have a chat or collaboration platform and want to automate the removal of inactive users from certain groups, this node can be configured to remove those users by their IDs from the target group.
Properties
| Name | Meaning |
|---|---|
| Send Option | Choose the message format to send: "Raw Json" (send message as raw JSON) or "Message" (send predefined message format). |
| Group ID | The unique identifier of the group from which users will be removed. |
| User IDs | A comma-separated list of user IDs to remove from the group. |
Output
The node outputs JSON data representing the response from the API after attempting to remove the specified users from the group. This typically includes status information about the success or failure of the removal operation.
If the node supports binary data output, it would represent any files or attachments returned by the API, but based on the provided code and properties, the output is JSON only.
Dependencies
- Requires access to the target API that manages groups and users.
- Needs appropriate API authentication credentials configured in n8n (e.g., an API key or token).
- The node internally uses HTTP request libraries to communicate with the API.
Troubleshooting
- Invalid Group ID: If the group ID does not exist or is incorrect, the API will likely return an error indicating the group was not found. Verify the group ID is correct.
- Invalid User IDs: If any user ID in the list is invalid or the user is not a member of the group, the API may return partial failure or error messages. Ensure all user IDs are valid and currently members of the group.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Check that the API key or token is correctly set up in n8n credentials.
- API Rate Limits: If too many requests are sent in a short time, the API might throttle or reject requests. Implement retry logic or reduce request frequency.
- Malformed Input: Ensure the "User IDs" property is a properly formatted comma-separated string without extra spaces or invalid characters.
Common error messages:
- "Group not found" — check the Group ID.
- "User not in group" — verify user membership before removal.
- "Unauthorized" or "Authentication failed" — check API credentials.
- "Invalid input" — validate the format of User IDs.
Links and References
- Refer to your specific API documentation for details on the endpoint used to remove users from groups.
- n8n documentation on creating and configuring custom nodes: https://docs.n8n.io/integrations/creating-nodes/
- General best practices for API authentication and error handling in n8n workflows.
Note: The source code was heavily obfuscated, so the summary is based on the provided input properties and typical patterns for such operations.