eTelecom Zalo Oa Send Message icon

eTelecom Zalo Oa Send Message

Send messages via eTelecom Zalo Oa

Overview

This node allows sending text messages to users via a Zalo Official Account (OA) using the eTelecom API. It is designed for scenarios where businesses or services want to communicate directly with their customers on Zalo, a popular messaging platform in Vietnam. Typical use cases include customer support notifications, marketing messages, appointment reminders, or any personalized communication sent from an official Zalo account.

For example, a company can automate sending order status updates or promotional messages to users who have interacted with their Zalo OA.

Properties

Name Meaning
Zalo Official Account Name or ID Select the Zalo Official Account (OA) from which the message will be sent. Options are loaded dynamically from the connected eTelecom API. You can also specify an OA ID using an expression.
User ID The unique identifier of the Zalo user who will receive the message.
Message The text content of the message to send to the specified user.

Output

The node outputs a JSON object for each input item processed, containing:

  • success: Boolean indicating if the message was sent successfully.
  • oa_id: The ID of the Zalo Official Account used to send the message.
  • user_id: The recipient user's ID.
  • response: The full response returned by the eTelecom API after attempting to send the message.
  • error (only if failed): Error message describing why the message could not be sent.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential to connect to the eTelecom API service.
  • The credential must provide:
    • A valid domain URL for the eTelecom API.
    • An authorization token (Bearer token) for authentication.
  • The node uses the eTelecom API endpoints:
    • /shop.Zalo/ListOA to load available Zalo Official Accounts.
    • /shop.Zalo/OASendText to send text messages.

Troubleshooting

  • No credentials provided: The node requires valid API credentials to function. Ensure you have configured and selected the appropriate API key credential.
  • Invalid response from API: If the list of Zalo OAs cannot be fetched or the message sending fails, verify that the API domain and token are correct and that the eTelecom service is operational.
  • Failed to parse API response: This indicates the API returned malformed JSON or unexpected data. Check network connectivity and API status.
  • Message sending errors: Errors returned from the API (e.g., invalid user ID, OA ID, or message content) will be included in the output error field. Review these messages to adjust inputs accordingly.
  • Enable "Continue On Fail" in the node settings if you want the workflow to proceed even when some messages fail.

Links and References

  • n8n Expressions Documentation
  • eTelecom API documentation (not publicly linked here; refer to your API provider)
  • Zalo Official Account developer resources (search for Zalo OA API)

Discussion