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, 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 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 a Zalo API client library internally to authenticate and listen for events.
- Needs a valid webhook URL configured in n8n to receive POST requests from the Zalo event listener.
- Requires proper configuration of credentials including cookie, device identifier, and user agent for authentication.
Troubleshooting
- Connection failures: If the node cannot establish a connection to Zalo, ensure that the provided credentials are correct and have not expired.
- No events received: Verify that the webhook URL is publicly accessible and correctly set up in n8n. Also, confirm that the selected event types match the events being triggered on Zalo.
- Error messages like "No API instance found": This indicates invalid or missing credentials; re-authenticate or update the credentials.
- Webhook not triggering: Check network connectivity and firewall settings to allow incoming requests to the webhook endpoint.