Zalo User Interact icon

Zalo User Interact

Gửi tin nhắn và tương tác với Zalo User

Actions17

Overview

This n8n custom node provides integration with Zalo, a popular messaging platform. Specifically, for the Resource: Get and Operation: Find User, the node allows you to look up a Zalo user by their phone number. This is useful in automation scenarios where you need to verify if a user exists on Zalo or retrieve their information based on their phone number.

Practical examples:

  • Verifying if a customer has a Zalo account before sending them a message.
  • Enriching CRM data with Zalo user details.
  • Automating onboarding flows that require checking a user's presence on Zalo.

Properties

For the selected resource and operation, the following input property is supported:

Display Name Type Description
Phone Number String Số điện thoại của người dùng Zalo. (The phone number of the Zalo user.)
  • Phone Number is required and must be provided for the "Find User" operation.

Output

The output of this node for the "Find User" operation is structured as follows:

[
  {
    "json": {
      "success": true,
      "data": { /* Zalo user information, if found */ }
    }
  }
]

  • If the user is found, success will be true, and data will contain the user's information as returned by Zalo's API.

  • If the user is not found or an error occurs, the output may include:

    [
  {
    "json": {
      "success": false,
      "error": "Error message describing the issue"
    }
  }
]

  • The node does not output binary data for this operation.

Dependencies

  • Zalo API access: You must have valid credentials (such as an API key or token) configured in n8n to authenticate requests to the Zalo API.
  • Network access: The n8n instance must be able to reach Zalo's servers.
  • n8n configuration: Ensure any necessary environment variables or credentials are set up in n8n for Zalo integration.

Troubleshooting

Common issues:

  • Invalid or missing phone number: The "Phone Number" field is required. If omitted or incorrectly formatted, the node will return an error.
  • User not found: If the phone number does not correspond to a Zalo user, the output will indicate failure.
  • API authentication errors: If your Zalo credentials are invalid or expired, you'll receive an authentication error from the API.
  • Network errors: If n8n cannot reach the Zalo API, a network error will be reported.

Typical error messages:

  • "Missing required parameter: Phone Number" – Ensure you provide a valid phone number.
  • "Authentication failed" – Check your Zalo API credentials in n8n.
  • "User not found" – The specified phone number does not belong to a Zalo user.
  • "Network error" – Verify network connectivity between n8n and Zalo's API.

Links and References

Note: This summary is based on static code analysis and the provided property definitions. Actual runtime behavior may depend on your specific n8n setup and Zalo API responses.

Discussion