Zalo Group icon

Zalo Group

Quản lý nhóm Zalo

Actions16

Overview

This node manages Zalo groups, allowing users to perform various group-related operations via the Zalo API. Specifically, the "Đổi Tên Nhóm" (Change Group Name) operation lets you rename an existing Zalo group by providing its ID and a new name.

Common scenarios for this node include:

  • Automating group management tasks such as renaming groups based on external triggers or workflows.
  • Integrating Zalo group administration into broader automation pipelines.
  • Keeping group names consistent with organizational changes or events.

For example, you could use this node to automatically update a group's name when a project phase changes or when a team is restructured.

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 related metadata returned by the API.

Example output structure:

{
  "groupId": "string",
  "newName": "string",
  "status": "success",
  // other API response fields
}

No binary data output is produced by this operation.

Dependencies

  • Requires valid Zalo API credentials including an API key credential that provides cookie, IMEI, and user agent information.
  • The node uses the zca-js library to interact with the Zalo API.
  • Proper configuration of the Zalo API credential in n8n is necessary before using this node.

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.
  • Empty or Invalid New Name: Ensure the new group name is not empty and meets any naming requirements imposed by Zalo.
  • API Rate Limits or Network Issues: Temporary failures might happen due to network problems or API rate limits; retrying later can help.
  • Use the "Continue On Fail" option in n8n to handle errors gracefully within workflows.

Links and References

Discussion