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 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 SDK/library (
zca-js) to handle authentication and event listening. - Needs valid credentials including cookie, IMEI, and user agent information for login.
- The node sets up a webhook URL where Zalo sends friend event notifications.
Troubleshooting
Common issues:
- Missing or invalid credentials will cause connection failures.
- Incorrect webhook URL configuration may prevent receiving events.
- Network issues could disrupt event listening.
Error messages:
"No credentials found": Ensure you have configured the required API key credential properly."No API instance found. Please make sure to provide valid credentials.": Check that the provided credentials are correct and include all necessary fields (cookie, IMEI, user agent)."Zalo connection failed": Indicates failure during login or event listener setup; verify network connectivity and credential validity.