Overview
This node listens for friend-related events on the Zalo platform, specifically friend requests. It acts as a trigger that activates workflows when such events occur. This is useful for automating responses or actions based on incoming friend requests on Zalo, such as sending notifications, logging events, or updating CRM systems.
Practical examples:
- Automatically notify a team member when a new friend request arrives.
- Log friend requests into a database for analytics.
- Trigger a welcome message workflow when a friend request is accepted.
Properties
| Name | Meaning |
|---|---|
| Event Types | Friend events to listen for. Options: "Friend Requests" |
Output
The node outputs JSON data representing the friend event received from Zalo. The output structure includes a friendEvent object containing details about the specific friend event (e.g., a friend request). This data can be used downstream in the workflow for further processing.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential to connect with the Zalo platform.
- Uses the Zalo API client library (
zca-js) to manage connection and event listening. - Needs valid credentials including cookie, device IMEI, and user agent information for authentication.
- The node sets up a webhook URL where Zalo sends friend event notifications.
Troubleshooting
- No credentials found: Ensure that the required API authentication token or credentials are properly configured in n8n before activating the node.
- Zalo connection failed: This error indicates issues with authenticating or connecting to Zalo's API. Verify that the provided credentials (cookie, IMEI, user agent) are correct and have not expired.
- Webhook not receiving events: Confirm that the webhook URL is correctly set and publicly accessible. Also, verify that the selected event types match the events sent by Zalo.
- If the node does not trigger, check that the workflow is active and the node is connected (the node stores connection state internally).