Overview
This node is a webhook-based trigger designed to listen for specific friend-related events from the Zalo platform, particularly friend requests. It establishes a connection using provided credentials and listens for incoming friend event notifications. When such an event occurs, it triggers the workflow with the event data.
Common scenarios where this node is beneficial include:
- Automating responses or workflows when a new friend request is received on Zalo.
- Integrating Zalo friend events into CRM systems or notification services.
- Monitoring friend activity in real-time for analytics or engagement purposes.
Practical example:
- Automatically send a welcome message or add the requester to a mailing list whenever a friend request event is detected.
Properties
| Name | Meaning |
|---|---|
| Event Types | Friend events to listen for. Options: "Friend Requests" |
The property allows selecting which types of friend events the node should listen for. Currently, only "Friend Requests" is available as an option.
Output
The node outputs JSON data representing the friend event received from Zalo. The output structure includes at least a friendEvent object containing details about the event type and associated data.
The output is delivered via the webhook response and can be used downstream in the workflow for further processing.
No binary data output is involved.
Dependencies
- Requires valid Zalo API credentials (an API key or token) configured in n8n to authenticate and establish the connection.
- Depends on the Zalo API client library bundled within the node to handle event subscriptions and communication.
- Needs the node to be set up with a publicly accessible webhook URL to receive event callbacks from Zalo.
Troubleshooting
- Connection errors: If the node fails to connect, ensure that the provided Zalo credentials are correct and have the necessary permissions.
- No events received: Verify that the webhook URL is correctly configured and publicly accessible. Also, confirm that the selected event types match those being sent by Zalo.
- API instance missing error: This indicates that the node could not instantiate the Zalo API client, likely due to invalid or missing credentials.
- Unexpected disconnections: The node attempts to maintain a persistent connection; network instability may cause issues. Check network connectivity and firewall settings.