Zalo CN Friend Trigger icon

Zalo CN 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 welcome messages, logging new connections, or integrating with CRM systems.

Practical examples:

  • Automatically send a greeting message when a new friend request is received.
  • Log friend requests into a database or spreadsheet for tracking.
  • Trigger notifications to team members about new connection requests.

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 of the event, such as the type and associated data about the friend request.

Example output JSON structure:

{
  "friendEvent": {
    "type": 2,
    "data": {
      // Details about the friend request event
    }
  }
}

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 establish a connection and listen for events.
  • Needs webhook URL configuration in n8n to receive event callbacks from Zalo.
  • Requires valid authentication cookies, device identifiers, and user agent strings as part of the credentials to authenticate with Zalo's API.

Troubleshooting

  • Connection failures: If the node cannot connect to Zalo, ensure that the provided credentials are correct and include valid authentication cookies and device information.
  • No events received: Verify that the webhook URL is correctly set up and accessible by Zalo. Also, confirm that the selected event types match the incoming events.
  • Error messages about missing credentials: Make sure the required API key credential is configured in n8n and linked to the node.
  • Unexpected errors during login or event listening: Check network connectivity and the validity of the Zalo API client library version.

Links and References

Discussion