Zalo Group icon

Zalo Group

Quản lý nhóm Zalo

Overview

This node interacts with Zalo Group functionalities, specifically allowing users to manage group members and roles. The "Thêm Phó Nhóm" (Add Group Deputy) operation enables adding a user as a deputy (co-admin) to a specified group. This is useful in scenarios where group management responsibilities need to be delegated to trusted members without transferring full ownership.

Practical examples include:

  • Adding moderators or deputies to large community groups to help manage content and membership.
  • Delegating administrative tasks in business or project groups on Zalo.
  • Automating group role assignments based on external triggers or workflows.

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 assigned as the deputy in the group.

Output

The output JSON contains:

  • status: A string indicating the success status of the operation, typically "Thành công" meaning "Success".
  • response: The raw response object returned from the API call that adds the deputy user to the group.

The output is paired with the input item index for traceability in batch operations.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Zalo platform.
  • Uses a client library internally to interact with Zalo's group management API, which requires valid session cookies, device IMEI, and user agent strings obtained from the credentials.
  • Proper configuration of these authentication details in n8n credentials is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication tokens/cookies can cause authorization failures.
    • Incorrect group ID or user ID may result in errors or no changes.
    • Network connectivity problems can interrupt API calls.
  • Error messages:

    • Errors thrown during API interaction are caught and returned as part of the output if the node is set to continue on failure; otherwise, they cause the workflow to fail.
    • Typical error messages relate to invalid parameters or permission denied, which usually require checking the provided IDs and credential validity.
  • Resolution tips:

    • Verify that the API key and session information are current and correctly configured.
    • Double-check the group and user IDs for correctness.
    • Ensure the user has sufficient permissions to add deputies in the target group.

Links and References

Discussion