(Thong) Zalo Friend Trigger icon

(Thong) Zalo Friend Trigger

Lắng nghe sự kiện kết bạn trên Zalo

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 databases.

Practical examples:

  • Automatically notify a team via chat or email when a new friend request is received on Zalo.
  • Log friend request data into a CRM system for follow-up.
  • Trigger additional workflows to analyze or respond to 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.

If binary data were involved, it would be summarized here, but this node only outputs JSON event data.

Dependencies

  • Requires an API key credential to connect with the Zalo platform.
  • Uses the Zalo SDK (zca-js) to manage connection and event listening.
  • Needs valid authentication cookies, device IMEI, and user agent information provided through credentials.
  • The node sets up a webhook URL where Zalo sends friend event notifications.

Troubleshooting

  • No credentials found: Ensure that the required API authentication token and related credential data are properly configured in n8n.
  • Zalo connection failed: This error indicates failure to establish a connection with Zalo using the provided credentials. Verify that the cookie, IMEI, and user agent values are correct and have not expired.
  • Webhook not receiving events: Confirm that the webhook URL is correctly set in Zalo and accessible from the internet.
  • Event types not triggering: Make sure the selected event types in the node settings match the actual events sent by Zalo.

Links and References

Discussion