Zalo Friend Trigger icon

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 CRM systems.

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 database for analytics or record-keeping.
  • Trigger follow-up workflows to send welcome messages or gather additional user information.

Properties

Name Meaning
Event Types Friend events to listen for. Options: "Friend Requests" (listens for incoming friend requests on Zalo)

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 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 (zca-js) internally to manage connection and event listening.
  • Needs valid authentication cookies, device IMEI, and user agent strings provided through credentials.
  • The node sets up a webhook URL where Zalo sends friend event notifications.

Troubleshooting

  • Common issues:

    • Missing or invalid credentials will cause connection failures.
    • If the Zalo API instance cannot be created (e.g., due to expired cookies), the node will throw a connection error.
    • Webhook URL misconfiguration may prevent receiving events.

  • Error messages:

    • "No credentials found": Ensure you have configured the required API authentication token and related credential data.
    • "Zalo connection failed": Check that your credentials are valid and that the Zalo service is reachable.
    • If no events are received, verify that the webhook URL is correctly set and accessible by Zalo.

Links and References

Discussion