Actions9
Overview
This node interacts with Zalo Group functionalities, specifically to retrieve the list of members in a Zalo group. It is useful for scenarios where you need to manage or analyze group membership data, such as auditing group participants, syncing group members with other systems, or automating notifications based on group composition.
A practical example: You have a Zalo group for your project team and want to regularly export the list of current members to keep your internal records updated or to send targeted messages.
Properties
| Name | Meaning |
|---|---|
| ID Nhóm | The unique identifier (ID) of the Zalo group from which to fetch the member list. |
| Giới Hạn | The maximum number of group members to retrieve in one execution (limit on the count). |
Output
The output is an array of JSON objects, each representing the response from the Zalo API regarding group members. The structure typically includes:
members: An array of member details retrieved from the group.admins: An array of admin user IDs within the group.currentMems,updateMems: Arrays related to current and updated members (likely metadata about membership status).totalMember: Total number of members in the group.
If errors occur during execution, the output will include an error field describing the issue for the corresponding item.
No binary data output is involved.
Dependencies
- Requires valid Zalo API credentials including authentication tokens and cookies.
- The node uses an external Zalo API client library internally to perform requests.
- Proper configuration of credentials in n8n is necessary to authenticate API calls.
- User agent and device identifiers (like IMEI) are also used internally, sourced from credentials or input data.
Troubleshooting
Common issues:
- Invalid or expired API credentials leading to authentication failures.
- Incorrect group ID causing "group not found" or empty member lists.
- Exceeding API rate limits or request quotas.
- Network connectivity problems affecting API calls.
Error messages:
"No API instance found. Please make sure to provide valid credentials."
Means the node could not initialize the API client due to missing or invalid credentials. Solution: Verify and re-enter the API key and authentication details.- Errors returned from the Zalo API (e.g., permission denied, invalid parameters) will be included in the output's
errorfield per item. Review these messages to adjust inputs accordingly. - If the node is set to continue on failure, errors will appear in the output JSON; otherwise, execution stops at the first error.
Links and References
- Zalo Official Developer Documentation (for detailed API capabilities and parameters)
- n8n documentation on Creating Custom Nodes (for understanding node development concepts)
This summary is based solely on static analysis of the provided source code and property definitions.