eTelecom Zalo Oa Check Consent icon

eTelecom Zalo Oa Check Consent

Check consent status via eTelecom Zalo Oa

Overview

This node checks the consent status of a phone number for a specific Zalo Official Account (OA) using the eTelecom API. It is useful in scenarios where you need to verify if a user has given consent to receive messages or notifications via Zalo, a popular messaging platform. For example, marketing teams can use this node to ensure compliance with consent regulations before sending promotional messages to customers.

Properties

Name Meaning
Zalo Official Account Name or ID Select from a list of available Zalo Official Accounts or specify an OA ID directly. This identifies the Zalo OA for which consent is being checked.
Phone The phone number whose consent status you want to check.

Output

The node outputs JSON data containing:

  • success: Boolean indicating if the request was successful.
  • oa_id: The ID of the Zalo Official Account used for the check.
  • phone: The phone number checked.
  • response: The full response object returned by the eTelecom API, which includes details about the consent status.

If the node encounters an error and is set to continue on failure, it outputs:

  • success: false
  • error: The error message describing what went wrong.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential to connect to the eTelecom API.
  • The node makes HTTP POST requests to the eTelecom domain endpoints /shop.Zalo/ListOA to load available Zalo OAs and /shop.Zalo/CheckConsent to check consent status.
  • Proper configuration of the API credentials with domain and token is necessary.

Troubleshooting

  • No credentials provided: The node will throw an error if the required API authentication token is missing. Ensure that valid credentials are configured.
  • Invalid response from API: If the API returns unexpected data or fails to parse JSON, the node will report an error. Verify the API service availability and credentials.
  • Network issues: Connectivity problems may cause request failures. Check network access and firewall settings.
  • Incorrect OA ID or phone number: Providing invalid or malformed inputs may result in errors or unsuccessful consent checks. Validate input values before running the node.

Links and References

Discussion