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 onboarding workflows for new contacts added via friend requests.
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 contains a friendEvent object with 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 to the Zalo platform.
- Uses the Zalo API client library (
zca-js) to manage connection and event listening. - Needs valid authentication cookies, device IMEI, and user agent information as part of the credentials.
- The node sets up a webhook URL where Zalo sends friend event notifications.
Troubleshooting
- Connection failures: If the node cannot establish a connection to Zalo, it throws an error indicating "Zalo connection failed". Ensure that the provided credentials are correct and include valid cookie, IMEI, and user agent values.
- Missing credentials: The node requires credentials to function. If none are found, it will throw an error stating "No credentials found".
- Webhook issues: Make sure the webhook URL is accessible from Zalo's servers and properly configured in your environment.
- Event filtering: If no events trigger the workflow, verify that the selected event types match those sent by Zalo.