Actions10
Overview
This node manages Zalo groups by interacting with the Zalo API. It supports various group-related operations such as creating groups, retrieving group information, managing members and deputies, changing group details, and creating notes within groups.
The specific operation "Lấy Thông Tin Nhóm" (Get Group Info) retrieves detailed information about a specified Zalo group by its ID. This is useful for scenarios where you need to fetch metadata or member details of a group for reporting, monitoring, or automation purposes.
Practical example:
You have an automation workflow that needs to monitor activity in certain Zalo groups. Using this node's "Get Group Info" operation, you can retrieve current group details like members, admins, and other metadata to analyze or trigger further actions.
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 output JSON contains two main fields:
response: The full raw response object returned from the Zalo API containing all available data about the group.groupInfo: A more focused subset of the response corresponding to the requested group's detailed information, extracted from a map keyed by the group ID.
Example output structure:
{
"response": { /* full API response object */ },
"groupInfo": {
"memberIds": [/* array of member IDs */],
"adminIds": [/* array of admin IDs */],
"currentMems": [/* current members info */],
"updateMems": [/* updated members info */],
"totalMember": 123,
// ... other group-specific metadata
}
}
No binary data output is produced by this operation.
Dependencies
- Requires a valid Zalo API credential configured in n8n, which includes authentication details such as cookies, device IMEI, and user agent strings.
- Uses the external
zca-jslibrary to interact with the Zalo API. - The node expects these credentials to be present and valid to successfully perform API calls.
Troubleshooting
Common issues:
- Invalid or expired credentials (cookie, IMEI, user agent) will cause login failure and prevent API access.
- Providing an incorrect or non-existent group ID will result in empty or error responses.
- Network connectivity issues may cause timeouts or failed requests.
Error messages:
"No API instance found. Please make sure to provide valid credentials."
Means the node could not authenticate with the Zalo API. Check your credential configuration and ensure they are up to date.- Errors thrown during execution will include the message from the underlying API call. If
continueOnFailis enabled, errors will be returned in the output JSON under anerrorfield instead of stopping the workflow.
Resolution tips:
- Verify and refresh your Zalo API credentials.
- Double-check the group ID input for correctness.
- Ensure stable internet connection.
- Enable "Continue On Fail" if you want the workflow to proceed despite individual item errors.
Links and References
- Zalo Official API Documentation (general reference for Zalo API capabilities)
- n8n Documentation for configuring credentials and using custom nodes.