Zalo Web icon

Zalo Web

Zalo Web.

Overview

This node integrates with the Zalo Web platform, enabling automation of various user-related and messaging operations. Specifically, for the User Action > Get User Profile operation, it retrieves detailed profile information about a specified user on Zalo by their unique user ID.

Common scenarios where this node is beneficial include:

  • Fetching user profile details to personalize communications or workflows.
  • Automating user data retrieval for CRM or customer support systems.
  • Integrating Zalo user information into broader business processes.

For example, you might use this node to get profile data of a user who just sent a message, then use that data to customize your response or log user details in your database.

Properties

Name Meaning
User ID Unique identifier for the target user whose profile is to be retrieved. This is required.

The "User ID" property expects a string representing the unique identifier of the user on Zalo. The description suggests using a bot (@get_id_bot) to find the chat ID if unknown.

Output

The node outputs an array of items, each containing a json object with a data field. For the "Get User Profile" operation, the data field holds the detailed profile information of the requested user as returned by the Zalo Web API wrapper.

Example output structure (simplified):

[
  {
    "json": {
      "data": {
        "uid": "123456789",
        "name": "John Doe",
        "avatar": "https://...",
        "status": "...",
        // other profile fields
      }
    }
  }
]

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for Zalo Web API authentication.
  • Relies on internal session management (accountID) to maintain login state.
  • Uses helper functions from n8n core for handling input/output data.
  • Depends on external modules for file handling and streaming, but these are not relevant for this specific operation.

Troubleshooting

  • Invalid or missing User ID: The node requires a valid user ID. If the ID is incorrect or empty, the operation will fail to retrieve user data.
  • Authentication errors: Ensure the provided API key credential is valid and has active session cookies. Expired or invalid credentials will cause failures.
  • Network issues: Since the node communicates with Zalo Web services, network connectivity problems can lead to timeouts or errors.
  • Unexpected API responses: If Zalo changes its API or user privacy settings restrict access, the node may return incomplete or no data.

To resolve common errors:

  • Verify the user ID format and existence.
  • Re-authenticate or refresh the API key credential.
  • Check internet connection and firewall settings.
  • Consult Zalo API documentation or support if API behavior changes.

Links and References

Discussion