Actions16
- ZNS Message Actions
- ZNS Template Actions
- ZNS Info Actions
ZNS Message → Send Message with RSA
AI-generatedOverview
This node integrates with the Zalo Notification Service (ZNS) API to send messages using RSA-encrypted phone numbers. It is designed for scenarios where secure messaging is required, such as sending personalized notifications or alerts to users with encrypted phone data. For example, it can be used to send templated messages to customers where the phone number is encrypted for privacy and security.
Use Case Examples
- Sending a ZNS message to a customer with an RSA-encrypted phone number using a predefined message template.
- Sending personalized notifications with dynamic template data to encrypted phone numbers for secure communication.
Properties
| Name | Meaning |
|---|---|
| Encrypted Phone | The RSA-encrypted phone number to which the message will be sent. |
| Template ID | The ID of the ZNS message template to use for the message. |
| Template Data | JSON-formatted data to replace parameters in the message template. Parameter names must match those registered in the template. Use {} if the template has no parameters. |
| Tracking ID | Optional ID used to track the message. |
Output
JSON
json- The JSON response from the Zalo ZNS API after sending the message, including status and any returned data.
Dependencies
- Zalo OA API Credential for authentication with the Zalo Notification Service API
Troubleshooting
- Common issues include invalid or missing RSA-encrypted phone numbers, incorrect template IDs, or malformed template data JSON. Ensure all required fields are correctly filled and formatted.
- Error messages may indicate unknown operations or resource mismatches if the operation or resource parameters are incorrect. Verify that the operation is 'sendMessageRSA' and the resource is 'znsMessage'.
- API authentication errors may occur if the Zalo OA API credential is invalid or expired. Refresh or reconfigure the credential as needed.