Overview
This node integrates with the Zalo platform to register a webhook URL and obtain a unique request ID associated with a user email. It is designed to facilitate receiving webhook POST requests from Zalo, enabling automation workflows that react to events or messages sent by Zalo.
Common scenarios where this node is beneficial include:
- Automating responses or processing when Zalo sends event notifications.
- Linking Zalo user accounts via email to webhook endpoints for real-time updates.
- Using proxy and custom user agent settings to control network routing and client identification.
Practical example:
- A marketing automation workflow that triggers when a user interacts with a Zalo chatbot, using the webhook URL to receive event data and process it further in n8n.
Properties
| Name | Meaning |
|---|---|
| The user's email address associated with the Zalo account; required for identifying the user. | |
| Proxy | Optional HTTP(S) proxy URL (including credentials if needed) through which requests are routed. |
| User Agent | Optional custom User-Agent string to be used in HTTP requests to Zalo. |
| Webhook URL | The URL endpoint where Zalo will send webhook POST requests; must be publicly accessible. |
Output
The node outputs JSON data containing:
request_id: A unique identifier returned by Zalo for the webhook registration request.email: The email address provided as input.- Additional fields related to the webhook registration status and metadata.
The output also includes a boolean flag indicating success (success: true).
If binary data were involved, it would represent the content of the webhook payloads, but this node primarily deals with JSON data.
Dependencies
- Requires an active internet connection to communicate with Zalo's API.
- Needs a valid webhook URL accessible by Zalo.
- Supports optional proxy configuration for network routing.
- Uses standard HTTP requests; no special external libraries beyond bundled dependencies.
- Requires proper API authentication handled internally (not exposed in code).
Troubleshooting
Common Issues
- Invalid or unreachable webhook URL: Ensure the webhook URL is publicly accessible and correctly configured to accept POST requests.
- Incorrect email format or unregistered email: Verify the email corresponds to a valid Zalo user.
- Proxy misconfiguration: If using a proxy, confirm the proxy URL and credentials are correct.
- Network connectivity problems: Check firewall and network settings to allow outbound connections to Zalo.
Error Messages
- Errors related to HTTP request failures may indicate network issues or invalid URLs.
- Authentication errors suggest missing or invalid API credentials (handled internally).
- Timeout errors could result from slow network or unreachable webhook endpoints.
Resolving these typically involves verifying input parameters, network access, and webhook server readiness.
Links and References
Note: Internal credential names and obfuscated code details have been omitted to comply with security best practices.