Overview
This node listens for friend-related events on the Zalo platform, specifically friend requests. It acts as a webhook trigger that activates when such events occur, allowing workflows to respond automatically to new friend requests on Zalo.
Common scenarios include:
- Automatically processing incoming friend requests.
- Sending notifications or logging friend request events.
- Integrating Zalo friend events with other systems or databases.
For example, when a user receives a friend request on Zalo, this node can trigger a workflow that sends an alert email or updates a CRM system.
Properties
| Name | Meaning |
|---|---|
| Event Types | Friend events to listen for. Options: "Friend Requests" (listens for friend request events) |
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 is provided in the json field of the output.
No binary data is produced by this node.
Dependencies
- Requires a valid API authentication credential for Zalo to connect and listen for events.
- Uses a third-party Zalo SDK/library to manage connection and event listening.
- Needs a publicly accessible webhook URL configured in n8n to receive event callbacks from Zalo.
Troubleshooting
- Connection failures: If the node cannot connect to Zalo, ensure the API credentials are correct and have not expired.
- No events received: Verify that the webhook URL is correctly set up and reachable by Zalo's servers.
- Invalid credentials error: The node throws an error if no credentials are found or if login fails; recheck the API key/token and related parameters.
- Event filtering issues: Make sure the selected event types match the actual events sent by Zalo; currently, only friend request events are supported.