Zalo Bot icon

Zalo Bot

Interact with Zalo Bot Platform

Overview

This node integrates with the Zalo Bot Platform, allowing users to interact programmatically with their Zalo bot. Specifically, the getMe operation under the Bot resource retrieves information about the bot itself, such as its identity and basic details.

Common scenarios for using this node include:

  • Verifying the bot's credentials and connection status.
  • Fetching bot profile information for display or logging.
  • Debugging API connectivity by retrieving the bot's own data.

For example, a user might use the getMe operation to confirm that their bot is correctly set up before sending messages or setting webhooks.

Properties

Name Meaning
Debug Mode When enabled (true), the node returns the full URL of the API call for easier debugging.

Output

The output JSON contains the response from the Zalo Bot API for the getMe request. It typically includes the bot's profile information such as its ID, name, and other metadata provided by the platform.

If "Debug Mode" is enabled, the output also includes a debug object containing:

  • The actual URL called (with the access token redacted).
  • The HTTP status code of the response.

This helps in troubleshooting API requests.

The node does not output binary data.

Example output structure (simplified):

[
  {
    "response": {
      "id": "123456789",
      "name": "My Zalo Bot",
      ...
    },
    "debug": {
      "url": "https://bot-api.zapps.me/bot/getMe/<REDACTED_TOKEN>",
      "status": 200
    }
  }
]

Dependencies

  • Requires an API key credential for authenticating with the Zalo Bot Platform.
  • Uses the external service endpoint at https://bot-api.zapps.me.
  • Depends on the node-fetch library for making HTTP requests.
  • No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Missing or invalid API credentials: The node requires a valid API key credential to authenticate requests. Ensure the credential is configured properly.
  • API errors: If the API returns an error (e.g., invalid token, rate limits), the node will include the error response in the output. Enabling Debug Mode can help identify the exact request URL and status code.
  • Network issues: Connectivity problems may cause request failures. Verify network access to https://bot-api.zapps.me.
  • Unexpected response format: If the API response cannot be parsed as JSON, the raw response text and status code are returned for inspection.

Links and References

Discussion