Zalo Bot icon

Zalo Bot

Interact with Zalo Bot Platform
Join our community

Actions9

Overview

This node integrates with the Zalo Bot Platform, allowing users to manage and interact with their Zalo bots. Specifically, the getWebhookInfo operation under the Bot resource retrieves information about the current webhook configuration of the bot.

Common scenarios for this node include:

  • Checking the status and details of the webhook URL set for a Zalo bot.
  • Debugging webhook issues by retrieving webhook info and optionally returning the request URL for easier troubleshooting.
  • Managing bot integrations where webhook setup verification is necessary.

Practical example:

  • A user wants to verify if their webhook URL is correctly registered and active on the Zalo platform. Using this node with the getWebhookInfo operation, they can fetch the webhook details and confirm its status.

Properties

Name Meaning
Debug Mode When enabled (true), the node returns the actual API request URL and HTTP status to help with debugging. Otherwise, it returns only the API response data.

Output

The output is a JSON array containing one object per input item. For the getWebhookInfo operation, each object includes either:

  • A response field holding the parsed JSON response from the Zalo API about the webhook info, or
  • If debug mode is enabled or an error occurs, an object containing:
    • response: The API response (parsed JSON or raw text).
    • debug: An object with:
      • url: The full API request URL used (with the access token redacted).
      • status: The HTTP status code returned by the API.

No binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the Zalo Bot Platform.
  • Uses the external service endpoint at https://bot-api.zapps.me.
  • Requires network access to the Zalo Bot API.
  • No additional environment variables are needed beyond the API authentication credential.

Troubleshooting

  • Missing Confirm Delete: When deleting a webhook, the node requires explicit confirmation via the "Confirm Delete" property to prevent accidental removal. Without enabling this, deletion will throw an error.
  • Sticker ID Missing: For sending stickers (not relevant here but part of the node), missing sticker ID causes an error.
  • API Errors: If the API returns an error or non-OK status, the node returns debug information including the request URL and status code when debug mode is enabled.
  • Invalid Credentials: Ensure the API key credential is valid and has permissions to access the bot API.
  • Network Issues: Connectivity problems to the Zalo API endpoint will cause failures; check network and firewall settings.

Links and References

Discussion