eTelecom Zalo Oa Request User Info icon

eTelecom Zalo Oa Request User Info

Request user information via eTelecom Zalo Oa
Join our community

Overview

This node, eTelecom Zalo Oa Request User Info, is designed to request detailed user information from the Zalo platform via an eTelecom API integration. It targets scenarios where you need to retrieve profile or account data of a specific Zalo user associated with a particular Zalo Official Account (OA). Typical use cases include customer support automation, personalized marketing workflows, or CRM enrichment where user details from Zalo are required.

For example, you might use this node to fetch user info after receiving a message from that user on your Zalo Official Account, enabling you to tailor responses or update your database with the latest user attributes.

Properties

Name Meaning
Zalo Official Account Name or ID (oaId) Select the Zalo Official Account (OA) from which to request user information. You can choose from a dynamically loaded list of available OAs or specify an OA ID using an expression.
Zalo User ID (zlUserId) The unique identifier of the Zalo user whose information you want to retrieve. This must be provided as a string.

Output

The node outputs JSON data for each input item processed. The structure of the output JSON is:

{
  "success": true,
  "oa_id": "<Zalo Official Account ID>",
  "zl_user_id": "<Zalo User ID>",
  "response": { /* full response object from the eTelecom API containing user info */ }
}
  • success: Boolean indicating if the request was successful.
  • oa_id: The Official Account ID used in the request.
  • zl_user_id: The Zalo User ID requested.
  • response: The raw response data returned by the eTelecom API, containing detailed user information.

If the request fails and the node is configured to continue on failure, the output JSON will contain:

{
  "success": false,
  "error": "<Error message>"
}

The node does not output binary data.

Dependencies

  • Requires an API key credential to authenticate with the eTelecom API service.
  • The credential must provide:
    • A valid domain URL for the eTelecom API.
    • An authorization token (Bearer token) for API access.
  • The node uses HTTP POST requests to communicate with the eTelecom API endpoints:
    • /shop.Zalo/ListOA to load available Zalo Official Accounts.
    • /shop.Zalo/RequestUserInfo to request user information.

Troubleshooting

  • No credentials provided: The node requires valid API credentials. Ensure you have configured the necessary API authentication token and domain in the credentials section.
  • Invalid response from API: If the API returns unexpected data or errors, verify that the OA ID and Zalo User ID are correct and that the API token has sufficient permissions.
  • Failed to parse API response: This indicates the API returned malformed JSON or an unexpected format. Check network connectivity and API status.
  • Common error messages:
    • "No credentials provided": Add and select proper API credentials.
    • "Invalid response from ETelecom API": Confirm the API endpoint and parameters.
    • Network or authorization errors: Verify API token validity and network access.

To resolve issues, check logs for detailed error messages and ensure all input parameters are correctly set.

Links and References

  • n8n Expressions Documentation
  • Zalo Official Account API documentation (refer to eTelecom or Zalo developer portals)
  • eTelecom API documentation (if available internally or from your API provider)

Discussion