Actions9
Overview
This node allows users to manage groups on the Zalo platform, specifically focusing on creating new groups under the "Group" resource with the "Tạo Nhóm" (Create Group) operation. It is useful for automating group creation workflows in Zalo, such as setting up chat groups for teams, communities, or event participants.
A practical example would be automatically creating a group with a specified name and adding multiple members by their user IDs, which can streamline onboarding processes or community management tasks.
Properties
| Name | Meaning |
|---|---|
| Tên Nhóm (groupName) | The name of the new group to be created. |
| Danh Sách ID Thành Viên (userIds) | A comma-separated list of member user IDs to add to the group upon creation. |
Output
The output JSON contains the response from the Zalo API after attempting to create the group. This typically includes details about the newly created group such as its ID, name, and member information.
The output structure looks like this (example):
{
"json": {
"response": {
"groupId": "string",
"groupName": "string",
"members": ["userId1", "userId2", "..."]
}
},
"pairedItem": {
"item": 0
}
}
No binary data output is produced by this node.
Dependencies
- Requires valid Zalo API credentials including an API key or token, cookie, IMEI, and user agent string.
- The node uses an internal Zalo API client class to interact with the Zalo service.
- Users must configure these credentials properly in n8n before using the node.
Troubleshooting
Common issues:
- Invalid or missing credentials will cause the node to fail with an error indicating no API instance was found.
- Incorrectly formatted user ID lists (e.g., missing commas or invalid IDs) may result in API errors or partial group creation.
- Network or API rate limiting issues could cause intermittent failures.
Error messages:
"No API instance found. Please make sure to provide valid credentials."— Ensure that all required authentication details are correctly set up.- Errors returned from the Zalo API will be included in the output JSON under an
errorfield if the node is configured to continue on failure.
Resolution tips:
- Double-check credential configuration in n8n.
- Validate the format of the user IDs input.
- Handle errors gracefully by enabling "Continue On Fail" in the node settings to process multiple items without stopping.