Zalo User icon

Zalo User

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

Actions10

Overview

This node manages interactions with Zalo users, a popular messaging platform. It enables automating common user-related actions such as sending friend requests, accepting friend requests, blocking or unblocking users, changing alias names, retrieving user information, and more.

A typical use case is automating social engagement workflows, for example:

  • Automatically sending personalized friend requests with custom messages.
  • Managing friend lists by accepting incoming requests or blocking unwanted contacts.
  • Fetching user details to enrich CRM data.
  • Changing display names (aliases) for better contact organization.

These capabilities help streamline social media management, customer outreach, and community building on the Zalo platform.

Properties

Name Meaning
User ID The unique identifier of the Zalo user to perform the operation on.
Message The message text sent along with a friend request invitation.

Note: The "Message" property is only applicable when sending a friend request.

Output

The node outputs JSON objects containing the result of each operation per input item. Common output fields include:

  • status: A string indicating success, typically "Thành công" (meaning "Success").
  • response: The raw response from the Zalo API for the performed action.
  • For user info retrieval operations, the output JSON contains detailed user data as returned by the API.
  • For listing friends, the output includes a friends array with user summaries.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential to authenticate with the Zalo platform.
  • Uses stored cookies, device IMEI, and user agent strings for session management.
  • Depends on the external zca-js library to interact with the Zalo API.

Ensure that valid credentials with proper permissions are configured in n8n before using this node.

Troubleshooting

  • Invalid Credentials or Session: If the node throws "No API instance found," verify that the provided API credentials (cookie, IMEI, user agent) are correct and active.
  • Operation Failures: Errors during specific operations (e.g., sending friend requests) will be reported with error messages. Enable "Continue On Fail" to process subsequent items despite errors.
  • Missing Required Parameters: Ensure all required properties like "User ID" and "Message" (for friend requests) are provided; otherwise, the node will fail.
  • API Rate Limits: Frequent calls may hit Zalo API rate limits; consider adding delays or batching requests.

Links and References

Note: These links provide general guidance on Zalo APIs but may not directly reference this node's implementation.

Discussion