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 when a friend request is received.
- Integrating Zalo friend events with other systems or databases.
For example, a user could set up this node to trigger a workflow that sends a welcome message whenever a new friend request is accepted.
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 triggered (e.g., a friend request). This allows downstream nodes to access and process the event data.
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 to authenticate and listen for events.
- Needs a valid webhook URL configured in n8n to receive event callbacks.
- Requires proper configuration of credentials including cookie, device identifier, and user agent for authentication.
Troubleshooting
- Connection failures: If the node cannot connect to Zalo, ensure the provided credentials are valid and contain the necessary authentication information (cookie, IMEI, user agent).
- No events received: Verify that the webhook URL is correctly set and publicly accessible so Zalo can send event data.
- Error messages like "Zalo connection failed": Usually indicate invalid or expired credentials; re-authenticate or update credentials.
- Webhook not triggering: Confirm that the workflow is active and listening on the correct webhook path.