Actions10
Overview
This node manages Zalo groups, specifically allowing operations such as creating groups, retrieving group info, managing members and deputies, changing group avatars or names, 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 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 rename a project discussion group automatically when a project phase changes, keeping group names relevant without manual intervention.
Properties
| Name | Meaning |
|---|---|
| ID Nhóm | The unique identifier of the Zalo group to rename. Must be provided. |
| Tên Mới | The new name to assign to the group. Must be provided. |
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: Actual fields depend on the Zalo API response.)
No binary data is output by this operation.
Dependencies
- Requires valid Zalo API credentials including an API key credential with cookie, IMEI, and user agent information.
- The node uses the
zca-jslibrary to interact with the Zalo API. - Proper configuration of the Zalo API credential in n8n is necessary for authentication.
Troubleshooting
- Invalid Credentials: If the node throws "No API instance found," it indicates invalid or missing credentials. Ensure the API key credential is correctly set up with valid cookie, IMEI, and user agent values.
- Group Not Found: Errors may occur if the provided group ID does not exist or the authenticated user lacks permission. Verify the group ID and permissions.
- API Rate Limits or Network Issues: Temporary failures might happen due to network problems or API rate limits. Retrying after some time or checking network connectivity can help.
- Continue On Fail: If enabled, errors for individual items will be captured in the output JSON under an
errorfield instead of stopping execution.
Links and References
- Zalo Official API Documentation
- n8n Documentation - Creating Custom Nodes
- zca-js GitHub Repository (for the underlying Zalo API client library)