Actions10
Overview
This node manages personal Zalo groups, enabling various group-related operations such as creating groups, retrieving group information, managing members and deputies, changing group details, and handling group notes. It is particularly useful for automating workflows involving Zalo group administration, such as syncing group data, bulk member management, or updating group settings programmatically.
A practical example includes fetching all groups a user belongs to, then iterating over them to update group names or add new members automatically based on external criteria.
Properties
| Name | Meaning |
|---|---|
| Giới Hạn | Maximum number of results to return when fetching groups (limit). Must be at least 1. |
Note: This property applies specifically to the "Lấy Tất Cả Nhóm" (Get All Groups) operation under the Group resource.
Output
The output JSON structure for the "Lấy Tất Cả Nhóm" operation contains:
response: An array or object representing all groups retrieved from the Zalo API.
Each item in the output corresponds to one input item processed, paired by index.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Zalo API.
- Uses the
zalo-api-finallibrary internally to interact with Zalo services. - The node expects valid authentication cookies, device IMEI, and user agent strings either from credentials or incoming input data.
- Proper configuration of the Zalo API credential within n8n is necessary.
Troubleshooting
Common Issues:
- Invalid or expired authentication cookie may cause login failure.
- Missing or incorrect device IMEI or user agent can lead to API errors.
- Exceeding API rate limits or permission restrictions on the Zalo account.
Error Messages:
"No API instance found. Please make sure to provide valid credentials."
Indicates failure to authenticate with Zalo API. Verify that the API key credential is correctly configured and valid.- Errors during execution will include the specific message returned by the API or thrown internally. If "Continue On Fail" is enabled, errors are returned in the output JSON under an
errorfield.
Resolution Tips:
- Ensure credentials are up-to-date and have required permissions.
- Confirm that input parameters like
limitare within allowed ranges. - Use "Continue On Fail" cautiously to handle partial failures gracefully.
Links and References
- Zalo Official API Documentation
- n8n Documentation on Credentials
- Zalo API Final GitHub Repository (for underlying API client used)