Zalo Group icon

Zalo Group

Quản lý nhóm Zalo
Join our community

Actions9

Overview

This node manages Zalo groups by interacting with the Zalo API. It supports various group-related operations such as creating groups, retrieving group information, managing members and deputies, changing group details, and more. The "Thêm Phó Nhóm" (Add Group Deputy) operation specifically adds a user as a deputy (co-admin) to an existing Zalo group.

Practical scenarios include:

  • Automating group management tasks in Zalo for community managers or businesses.
  • Adding trusted users as deputies to help moderate or manage group activities.
  • Integrating Zalo group management into broader workflows, e.g., syncing group roles with other systems.

Properties

Name Meaning
ID Nhóm The unique identifier of the Zalo group where the deputy will be added.
ID Người Dùng The unique identifier of the user who will be added as a deputy to the specified group.

Output

The output JSON contains:

  • status: A string indicating the result of the operation, typically "Thành công" meaning "Success".
  • response: The raw response from the Zalo API after attempting to add the deputy user.

Example output structure:

{
  "status": "Thành công",
  "response": { /* API response object */ }
}

No binary data is output by this operation.

Dependencies

  • Requires valid Zalo API credentials including cookie, device IMEI, and user agent information.
  • The node uses an external Zalo API client library (zca-js) to perform API calls.
  • Credentials must be configured in n8n with appropriate access rights to manage Zalo groups.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials may cause authentication failures.
    • Incorrect group ID or user ID can lead to errors or no effect.
    • Network connectivity problems can interrupt API communication.

  • Error messages:

    • If the API instance is not found or login fails, the node throws an error indicating invalid credentials.
    • Errors returned from the Zalo API are caught and either stop execution or, if "Continue On Fail" is enabled, are returned as error messages in the output JSON.

  • Resolutions:

    • Verify that the provided API credentials are correct and have not expired.
    • Double-check the group and user IDs for correctness.
    • Enable "Continue On Fail" to handle partial failures gracefully in batch executions.

Links and References

Discussion