Zalo ZNS icon

Zalo ZNS

Zalo Notification Service (ZNS) API

Actions16

ZNS Template → Update Template

AI-generated

Overview

This node interacts with the Zalo Notification Service (ZNS) API, specifically supporting operations related to ZNS templates such as updating a template. It is useful for managing message templates used in Zalo notifications, allowing users to update template details like name, type, tag, layout, parameters, notes, and tracking ID. Practical applications include maintaining up-to-date notification templates for OTPs, transaction confirmations, order updates, account updates, and general information messages.

Use Case Examples

  1. Updating an existing ZNS template to change its layout or parameters.
  2. Modifying the tag or type of a ZNS template to better categorize notification messages.

Properties

Name Meaning
Template Name The name of the template to be updated.
Template Type The type of the template, either Text Template (1) or Rich Template (2).
Tag Classification label for the template, such as OTP, Transaction Confirmation, Order Update, Account Update, or General Information.
Layout The JSON structure defining the layout of the template, including header, body, and footer components.
Parameters A JSON list of parameters used in the template, specifying types, names, and sample values.
Note Optional note for review or approval purposes.
Tracking ID Optional tracking identifier for the template.

Output

JSON

  • json - The response from the Zalo ZNS API after updating the template, containing details of the updated template or error information.

Dependencies

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

Troubleshooting

  • Common issues include providing invalid or incomplete template data, which may cause API errors.
  • Errors related to authentication failures if the Zalo OA API credential is missing or invalid.
  • Malformed JSON in the layout or parameters fields can cause request failures.
  • The node throws errors with messages from the API response; enabling 'Continue On Fail' allows processing subsequent items despite errors.

Discussion