Zalo User icon

Zalo User

Quản lý người dùng Zalo - Kết bạn, chặn, đổi tên, lấy thông tin và quản lý danh sách bạn bè

Actions12

Overview

This node interacts with the Zalo platform to perform user-related operations. Specifically, the "Tìm Kiếm Người Dùng" (Find User) operation allows searching for Zalo users by their phone number. This is useful in scenarios where you want to retrieve user information based on a known phone number, such as verifying user identities, enriching contact lists, or integrating Zalo user data into other workflows.

Practical examples:

  • Automatically find and fetch details of a user who just signed up using their phone number.
  • Enrich customer records in a CRM system with Zalo user information.
  • Validate if a phone number corresponds to an active Zalo user before sending messages.

Properties

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

Output

The node outputs JSON data containing the search results for the specified phone number. The structure typically includes user details returned by the Zalo API corresponding to the phone number query.

Example output JSON structure:

{
  "userId": "string",
  "name": "string",
  "avatar": "string",
  "phoneNumber": "string",
  "status": "string",
  ...
}

The exact fields depend on the Zalo API response but generally include identifiers and profile information of matched users.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Zalo API.
  • The node depends on a Zalo API client library internally to make requests.
  • Proper configuration of the API key credential within n8n is necessary.
  • The node uses stored cookies, IMEI, and user agent strings for authentication/session management with Zalo.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials can cause authentication failures.
    • Providing an incorrectly formatted phone number may result in no matches or errors.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • Errors thrown during execution will be reported with the message from the underlying API or network layer.
    • If the node cannot initialize the Zalo client session (e.g., missing cookie or device info), it throws an error indicating failure to create the client instance.

  • Resolutions:

    • Verify that the API key credential is correctly set up and valid.
    • Ensure phone numbers are provided in the expected format.
    • Check network access and proxy settings if applicable.
    • Re-authenticate or refresh stored session data if authentication errors persist.

Links and References

Discussion