Zalo Group icon

Zalo Group

Quản lý nhóm Zalo

Actions9

Overview

This node interacts with a group management API for the Zalo platform, specifically to retrieve detailed information about a particular group. It is useful in scenarios where you need to programmatically access group metadata such as members, admins, and other group-related details within an automation workflow.

A practical example would be automating the monitoring of group membership or fetching group info to display or process further in your workflow, such as syncing group data with a CRM or sending notifications based on group changes.

Properties

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

Output

The output JSON contains two main parts:

  • response: The full raw response from the API call that fetches the group information.
  • groupInfo: A subset of the response containing detailed information about the specified group identified by the provided group ID.

Example structure of the output JSON:

{
  "response": { /* full API response object */ },
  "groupInfo": { /* detailed info about the specific group */ }
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication token or cookie credential to authenticate requests to the Zalo group management API.
  • The node internally uses a helper class instance initialized with authentication details (cookie, imei, userAgent) extracted from credentials or previous nodes.
  • The environment must have network access to the Zalo API endpoints.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication tokens/cookies will cause authentication failures.
    • Providing an incorrect or non-existent group ID will result in empty or error responses.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • If the node cannot initialize the API client due to missing or invalid credentials, it throws an error indicating failure to create the client.
    • API errors returned from the Zalo service are caught and included in the output JSON under an error field if the node is configured to continue on failure.
    • If not continuing on failure, the node throws an error with the message from the API or internal exceptions.

Resolution tips:

  • Ensure valid and up-to-date API authentication credentials are configured.
  • Verify the group ID exists and is accessible by the authenticated user.
  • Check network connectivity and firewall settings.
  • Enable "Continue on Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion