Actions9
Overview
This node operation removes one or more users from a specified group in the Zalo platform. It is useful when managing group memberships dynamically, such as moderating group participants, cleaning up inactive members, or enforcing group policies by removing certain users.
Practical examples:
- Automatically removing users who violate group rules.
- Cleaning up a group by removing users who have left an associated project.
- Managing membership lists programmatically based on external triggers or workflows.
Properties
| Name | Meaning |
|---|---|
| ID Nhóm (groupId) | The unique identifier of the group from which users will be removed. |
| ID Người Dùng (nếu nhiều người dùng vui lòng phân cách bằng dấu phẩy) (userIds) | One or multiple user IDs to remove from the group, separated by commas if multiple users. |
Output
The output JSON contains the response from the Zalo API after attempting to remove the specified users from the group. This typically includes status information and any relevant messages returned by the API.
Example structure:
{
"status": "Thành công",
"response": {
// API-specific details about the removal operation
}
}
No binary data output is produced by this node operation.
Dependencies
- Requires an active connection to the Zalo platform via an API key credential configured in n8n.
- Uses authentication cookies, IMEI, and user agent strings internally to authenticate requests.
- Relies on the Zalo API client library bundled with the node for making API calls.
Troubleshooting
Common issues:
- Invalid or expired API credentials may cause authentication failures.
- Incorrect group ID or user IDs can result in errors or no changes.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors thrown by the node include descriptive messages from the Zalo API or internal validation errors.
- If the node is set to continue on failure, error details are included in the output JSON under an
errorfield. - To resolve errors, verify that the group ID and user IDs are correct and that the API credentials are valid and have sufficient permissions.