Actions9
Overview
This node manages Zalo groups, specifically allowing users to remove one or more members from a specified group. It is useful in scenarios where group administrators need to maintain or moderate group membership by removing unwanted or inactive users. For example, if a community manager wants to clean up a group by removing certain participants, this node can automate that process.
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 (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 be removed from the group, separated by commas if multiple. |
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 about the removal operation. The exact structure depends on the API response but generally confirms success or failure of the removal action.
Example output structure:
{
"status": "success",
"details": { /* additional info from API */ }
}
If an error occurs and the node is set to continue on failure, the output will contain an error
field with the error message.
Dependencies
- Requires valid Zalo API credentials including an API key credential with cookie, IMEI, and user agent details.
- The node uses an external Zalo API client library (
zca-js
) to interact with the Zalo platform. - Proper configuration of these credentials within n8n is necessary for successful API communication.
Troubleshooting
Common issues:
- Invalid or expired credentials leading to authentication failures.
- Incorrect group ID or user IDs causing the API to reject the request.
- Network connectivity problems preventing access to the Zalo API.
Error messages:
"No API instance found. Please make sure to provide valid credentials."
Resolution: Verify that the API credentials are correctly configured and valid.- Errors returned from the API when user IDs or group ID are invalid.
Resolution: Double-check the IDs provided and ensure they exist and are accessible. - If the node throws errors during execution and "Continue On Fail" is disabled, the workflow will stop. Enabling "Continue On Fail" allows processing subsequent items despite errors.
Links and References
- Zalo Official Developer Documentation
- n8n Documentation on Credentials
- zca-js GitHub Repository (Zalo Client Library) (for reference on API client used)