Actions9
Overview
This node interacts with Zalo Groups, specifically allowing users to retrieve detailed information about a particular group. It is useful in scenarios where you need to programmatically access group metadata such as members, admins, and other group-related details from Zalo, a popular messaging platform.
A practical example would be automating the monitoring of group membership changes or fetching group info for reporting purposes within an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| ID Nhóm | The unique identifier (ID) of the Zalo group whose information you want to retrieve. This is a required string input. |
Output
The node outputs JSON data containing detailed information about the specified group. The structure includes:
members: List of group members.admins: List of group administrators.currentMems: Current members in the group.updateMems: Members who have been updated recently.totalMember: Total number of members in the group.
The output is paired with the input item index for traceability.
No binary data output is indicated by the source code.
Dependencies
- Requires an API authentication token or cookie credential to authenticate requests to the Zalo service.
- Uses an external Zalo API client library internally to perform operations.
- Requires configuration of credentials that provide:
- A valid session cookie.
- Device IMEI.
- User agent string.
These are necessary to establish authenticated communication with the Zalo backend.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials may cause failures.
- Incorrect or missing group ID will result in errors or empty responses.
- Network connectivity problems can prevent successful API calls.
Error messages:
- If authentication fails, the node throws an error indicating failure to connect or invalid credentials.
- If the group ID does not exist or is inaccessible, the response may contain an error message or empty group info.
- When running in "continue on fail" mode, errors for individual items are returned in the output JSON under an
errorfield instead of stopping execution.
Resolutions:
- Verify and refresh your API authentication credentials.
- Double-check the group ID input for correctness.
- Ensure stable network connection.
- Use the "continue on fail" option to handle partial failures gracefully.
Links and References
- Zalo Official API Documentation (for reference on group operations)
- n8n documentation on Creating Custom Nodes