Actions10
Overview
This node manages Zalo groups, specifically allowing operations such as creating groups, retrieving group info, managing members, changing group details, and creating notes within groups. The "Đổi Tên Nhóm" (Change Group Name) operation updates the name of an existing Zalo group.
Typical use cases include:
- Renaming a Zalo group to reflect new purposes or membership changes.
- Automating group management tasks in workflows involving Zalo messaging.
- Integrating Zalo group administration into broader automation pipelines.
For example, you might use this node to rename a project discussion group automatically when a project phase changes, ensuring all participants see the updated group name without manual intervention.
Properties
| Name | Meaning |
|---|---|
| ID Nhóm | The unique identifier of the Zalo group to rename. This is required to specify which group will be affected. |
| Tên Mới | The new name to assign to the specified group. This must be provided to update the group's display name. |
Output
The output JSON contains the response from the Zalo API after attempting to change the group name. It typically includes confirmation details about the updated group name or status information returned by the API.
Example output structure:
{
"groupId": "string",
"newName": "string",
"status": "success"
}
(Note: The exact fields depend on the Zalo API's response for the changeGroupName method.)
No binary data output is produced by this operation.
Dependencies
- Requires valid Zalo API credentials including authentication cookies, device IMEI, and user agent strings.
- The node depends on the external
zca-jslibrary to interact with the Zalo API. - Proper configuration of the Zalo API credential in n8n is necessary to authenticate requests.
Troubleshooting
- Invalid Credentials: If the node throws an error indicating no API instance found, verify that the Zalo API credentials are correctly configured and valid.
- Group Not Found: Errors may occur if the provided group ID does not exist or the authenticated user lacks permission to modify it.
- Network Issues: Connectivity problems can cause request failures; ensure stable internet access.
- API Rate Limits: Frequent calls might hit Zalo API limits; consider adding delays or handling rate limit errors gracefully.
- Input Validation: Ensure that the group ID and new name are non-empty strings; empty or malformed inputs will cause errors.
If the node is set to continue on fail, errors for individual items will be included in the output JSON under an error field.
Links and References
- Zalo Official API Documentation
- n8n Documentation - Creating Custom Nodes
- zca-js GitHub Repository (for the underlying Zalo API client used)