eTelecom Zalo Oa Send ZNS icon

eTelecom Zalo Oa Send ZNS

Send ZNS via eTelecom Zalo OA

Overview

This node sends Zalo Notification Service (ZNS) messages via the eTelecom Zalo Official Account (OA) platform. It is designed to facilitate automated sending of templated notifications to recipients' phone numbers through Zalo's messaging system, leveraging eTelecom's API.

Common scenarios where this node is beneficial include:

  • Sending transactional alerts or updates to customers using predefined message templates.
  • Automating customer communication for order confirmations, delivery updates, or promotional messages.
  • Testing message templates in development mode before going live.

Practical example: A business can use this node to send a shipping confirmation message to a customer's phone number by selecting the appropriate Zalo OA, choosing a message template, and providing dynamic data to populate the template fields.

Properties

Name Meaning
Development Mode Whether to send the message in development mode (true/false).
Zalo Official Account Name or ID Select from a list of available Zalo Official Accounts or specify an ID via expression.
Phone Recipient's phone number to which the ZNS message will be sent.
Template Name or ID Select from a list of available message templates or specify an ID via expression.
Tracking ID Optional tracking identifier for the message.
Template Data (JSON) JSON-formatted string containing data to populate the selected message template's placeholders.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output object has the following structure:

  • success: Boolean indicating whether the message was sent successfully.
  • response: The full response object returned by the eTelecom API when the message is sent successfully.
  • error: If sending failed, contains the error message describing the failure.

Example output JSON for a successful send:

{
  "success": true,
  "response": {
    /* API response details */
  }
}

Example output JSON for a failure:

{
  "success": false,
  "error": "Error message describing what went wrong"
}

The node does not output binary data.

Dependencies

  • Requires an API key credential to authenticate with the eTelecom API.
  • The node makes HTTP POST requests to eTelecom endpoints to:
    • Retrieve lists of Zalo Official Accounts.
    • Retrieve available message templates.
    • Send ZNS messages.
  • Proper configuration of the API domain and token in the credential is necessary.

Troubleshooting

  • No credentials provided: The node requires valid API credentials to function. Ensure that the API key credential is configured correctly.
  • Invalid JSON in Template Data: If the Template Data (JSON) property contains malformed JSON, the node will throw an error. Validate JSON syntax before input.
  • Invalid response from API: If the API returns unexpected data structures, the node may fail to load options or send messages. Check API availability and correctness of credentials.
  • API request failures: Network issues or incorrect API tokens can cause request errors. Verify network connectivity and credential validity.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details per item.

Links and References

Discussion