Actions10
Overview
This node manages Zalo groups, specifically allowing operations such as creating groups, retrieving group info, managing members, and modifying group details. The "Remove User From Group" operation enables users to remove one or multiple members from a specified Zalo group by their user IDs.
Practical scenarios include:
- Moderators or group admins automating the removal of inactive or unwanted members.
- Integrations where membership management is part of a larger workflow, e.g., syncing group membership with external systems.
- Bulk removal of users based on certain criteria without manual intervention.
Properties
| Name | Meaning |
|---|---|
| ID Nhóm (groupId) | The unique identifier of the Zalo group from which users will be removed. |
| ID Người Dùng (userIds) | One or more user IDs to remove from the group. Multiple IDs should be separated by commas. |
Output
The output JSON contains the response from the Zalo API after attempting to remove the specified users from the group. It typically includes status information about the removal operation.
Example output structure:
{
"response": {
// API-specific details about the removal result
}
}
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Zalo platform.
- The node depends on the
zca-jslibrary to interact with the Zalo API. - Proper configuration of credentials including cookie, IMEI, and user agent is necessary for successful API calls.
Troubleshooting
- Invalid Credentials: If the provided API authentication token or cookie is invalid or expired, the node will fail to create an API instance. Ensure that valid credentials are supplied.
- Incorrect Group ID or User IDs: Providing wrong or malformed group/user IDs may cause the API call to fail or return errors. Double-check the IDs before running the node.
- Empty User IDs: If the user IDs string is empty or improperly formatted (e.g., missing commas), the removal operation might not work as expected.
- API Rate Limits or Network Issues: Temporary failures due to network problems or API rate limits can occur. Retrying or handling errors gracefully in workflows is recommended.
- Error Messages: Errors thrown by the node will include messages from the underlying API or SDK. Reading these messages carefully helps identify issues like permission problems or invalid parameters.