Zalo Group

Quản lý nhóm Zalo

Actions3

Overview

This node interacts with Zalo Group functionalities, specifically allowing users to retrieve detailed information about a Zalo group. It is useful in scenarios where you need to programmatically access group metadata such as member lists, admins, and other group details from the Zalo platform. For example, a community manager could use this node to fetch up-to-date group info for reporting or automation purposes.

The operation "Lấy Thông Tin Nhóm" (Get Group Info) fetches comprehensive information about a specified Zalo group by its ID.

Properties

Name Meaning
ID Nhóm The unique identifier of the Zalo group whose information you want to retrieve. This is a required string input.

Output

The output JSON contains two main fields:

  • response: The full raw response object returned by the Zalo API containing all available data about the group.
  • groupInfo: A specific subset of the response focused on the group's detailed information, extracted by the node for easier access.

Example output structure:

{
  "response": { /* full API response object */ },
  "groupInfo": { /* detailed info about the group identified by the given ID */ }
}

No binary data is output by this node.

Dependencies

  • Requires an API key credential to authenticate with the Zalo platform.
  • The node depends on a third-party Zalo SDK library (zca-js) to handle API interactions.
  • Proper configuration of credentials including cookie, device IMEI, and user agent strings is necessary for successful authentication.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials may cause authentication failures.
    • Providing an incorrect or non-existent group ID will result in errors or empty responses.
    • Network connectivity problems can prevent API calls from succeeding.

  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      This indicates that the node failed to authenticate with the Zalo API. Verify that the API key credential is correctly set up and contains valid cookie, IMEI, and user agent values.
    • Errors thrown during execution are caught and can be optionally continued on fail; otherwise, they stop the workflow with detailed error messages.

Links and References

Discussion