Zalo ZNS icon

Zalo ZNS

Zalo Notification Service (ZNS) API

ZNS Message → Send Journey Message

AI-generated

Overview

This node integrates with the Zalo Notification Service (ZNS) API to send journey messages using predefined ZNS templates. It is useful for automating customer communications such as sending notifications, alerts, or updates via Zalo's messaging platform. For example, businesses can send order confirmations, delivery updates, or promotional messages to customers' phone numbers using registered ZNS templates.

Use Case Examples

  1. Sending a delivery status update to a customer using a logistics template.
  2. Notifying a customer about a coach bus schedule using a coach bus template.

Properties

Name Meaning
Phone Number The recipient's phone number including the country code, used to specify the message recipient.
Template ID The ID of the ZNS template to be used for the message, identifying the message format and content structure.
Template Data JSON data to replace placeholders in the template. The keys must match the registered template parameters. Use an empty JSON object if the template has no parameters.
Tracking ID Optional ID used to track the message for analytics or debugging purposes.
Token Type Specifies the type of journey token to use, which affects message validity duration and context.

Output

JSON

  • json - The response from the Zalo ZNS API after sending the journey message, including status and any returned data.

Dependencies

  • Zalo OA API Credential for authentication with the Zalo Notification Service

Troubleshooting

  • Ensure the phone number includes the correct country code and is in the proper format to avoid delivery failures.
  • Verify that the Template ID corresponds to a registered and approved ZNS template to prevent errors.
  • Make sure the Template Data JSON keys exactly match the template parameters; mismatches can cause message sending to fail.
  • Check that the Token Type is appropriate for the message context and duration requirements.
  • If the node throws an error related to authentication, verify that the Zalo OA API Credential is correctly configured and has valid access tokens.

Links

Discussion