Actions9
Overview
The Zalo Group node with the "Đổi Tên Nhóm" (Change Group Name) operation allows users to rename an existing Zalo group by specifying its ID and the new desired name. This is useful for administrators or automation workflows that need to update group names dynamically, such as reflecting organizational changes, event updates, or correcting naming conventions.
Practical Example:
Automatically renaming a project discussion group when the project's phase changes, or updating a group's name to include the current month for recurring events.
Properties
| Name | Type | Meaning |
|---|---|---|
| ID Nhóm | String | The unique identifier of the Zalo group whose name you want to change. |
| Tên Mới | String | The new name to assign to the group. |
Output
The output will be the direct response from the Zalo API's changeGroupName method. Typically, this includes information about the success or failure of the operation. The structure may look like:
{
// Response fields as returned by the Zalo API after changing the group name.
}
- If the operation fails and "Continue On Fail" is enabled, the output will contain an
errorfield with the error message.
Dependencies
- External Service: Requires access to the Zalo platform via the
zca-jslibrary. - Credentials: Needs valid Zalo credentials (
zaloApi) including cookie, IMEI, and user agent. - n8n Configuration: Ensure the Zalo credential is set up in n8n and assigned to this node.
Troubleshooting
Common Issues:
- Invalid Credentials: If the provided Zalo credentials are incorrect or expired, the node will throw an error:
"No API instance found. Please make sure to provide valid credentials."- Resolution: Update your Zalo credentials in n8n.
- Missing Required Fields: If either "ID Nhóm" or "Tên Mới" is missing, the operation will fail.
- API Errors: Any issues from the Zalo API (e.g., invalid group ID, insufficient permissions) will be returned as error messages in the output if "Continue On Fail" is enabled.
- Invalid Credentials: If the provided Zalo credentials are incorrect or expired, the node will throw an error:
Error Handling:
- When "Continue On Fail" is enabled, errors are returned in the output under the
errorkey. - Otherwise, the workflow execution will stop, and the error will be shown in n8n.
- When "Continue On Fail" is enabled, errors are returned in the output under the