Zalo User icon

Zalo User

Quản lý người dùng Zalo
Join our community

Actions9

Overview

This node allows users to interact with Zalo's user-related API functionalities, specifically enabling the search for Zalo users by phone number. It is useful in scenarios where you need to find or verify Zalo users based on their phone numbers, such as customer support, marketing outreach, or user data enrichment.

For example, a business could use this node to look up Zalo users who have provided their phone numbers during registration to fetch additional profile information or confirm their identity.

Properties

Name Meaning
Phone Number The phone number of the Zalo user you want to search for.
Limit The maximum number of search results to return.

Output

The node outputs JSON data containing the search results for Zalo users matching the given phone number. The structure typically includes:

  • status: A string indicating the success status of the operation (e.g., "success").
  • response: An array or object containing the user data returned from the Zalo API.
  • pairedItem: Metadata linking the output to the corresponding input item index.

No binary data output is indicated in the source code.

Dependencies

  • Requires an API key credential for authenticating with the Zalo API.
  • Uses an external library (zca-js) to handle communication with the Zalo API.
  • Requires proper configuration of the API credentials within n8n to function correctly.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing an incorrectly formatted phone number may result in no users found or errors.
    • Exceeding the limit parameter might cause partial results or API rate limiting.

  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials." — Indicates missing or invalid API credentials; ensure credentials are set up properly.
    • Errors related to network or API response issues may occur if the Zalo service is unreachable or returns unexpected data.

  • Resolution tips:

    • Verify that the API key credential is correctly configured and active.
    • Ensure phone numbers are in the correct format expected by Zalo.
    • Adjust the limit parameter to a reasonable number to avoid API throttling.

Links and References

Discussion