Zalo User icon

Zalo User

Quản lý người dùng Zalo

Actions12

Overview

This node allows interaction with Zalo user accounts through various operations such as sending friend requests, accepting friend requests, blocking/unblocking users, updating profile settings, retrieving user information, managing friends list, and handling message status. It is particularly useful for automating social interactions on the Zalo platform, such as programmatically sending friend invitations with custom messages or managing contacts in bulk.

A practical example is using this node to send personalized friend requests to multiple users by specifying their User IDs and accompanying messages, streamlining outreach campaigns or community building efforts on Zalo.

Properties

Name Meaning
User ID The unique identifier of the Zalo user to whom the friend request will be sent.
Message The text message that accompanies the friend request invitation.

Output

The output JSON object contains at least two fields:

  • status: A string indicating the result of the operation, typically "Thành công" (meaning "Success").
  • response: The raw response data returned from the Zalo API for the performed action.

Each output item corresponds to an input item, preserving pairing for traceability.

No binary data output is produced by this operation.

Dependencies

  • Requires a valid Zalo API credential containing authentication details such as cookies, device IMEI, and user agent.
  • Uses the external zca-js library to interact with the Zalo API.
  • The node expects these credentials to be configured properly within n8n before execution.

Troubleshooting

  • Invalid Credentials: If the node throws an error stating no API instance was found, verify that the provided Zalo API credentials are correct and include valid cookie, IMEI, and user agent values.
  • Operation Failures: Errors during API calls (e.g., invalid User ID or message content) will cause the node to throw exceptions unless "Continue On Fail" is enabled, in which case errors are returned per item.
  • Missing Parameters: Ensure all required properties (User ID and Message) are provided; missing inputs will cause failures.
  • Rate Limits or API Restrictions: The Zalo API may impose limits; repeated failures might indicate throttling or permission issues.

Links and References

Discussion