Zalo User icon

Zalo User

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

Overview

This node manages Zalo user interactions, specifically for the "Zalo User" resource. The operation Chấp nhận lời mời kết bạn (Accept Friend Request) allows you to programmatically accept a friend request from another Zalo user by specifying their user ID.

Common scenarios where this node is beneficial include automating social interactions on Zalo, such as managing friend requests in bulk or integrating Zalo user management into broader workflows like CRM systems or customer engagement platforms.

For example, you could use this node to automatically accept friend requests from users who meet certain criteria, enabling seamless connection building without manual intervention.

Properties

Name Meaning
User ID The ID of the Zalo user whose friend request you want to accept.

Output

The output JSON contains:

  • status: A string indicating the result status, typically "Thành công" meaning "Success".
  • response: The raw response object returned from the Zalo API after accepting the friend request.

Example output JSON structure:

{
  "status": "Thành công",
  "response": {
    // API response details here
  }
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential with valid authentication details for Zalo, including cookie, device IMEI, and user agent information.
  • Uses the external zca-js library to interact with the Zalo API.
  • The node expects these credentials to be configured properly in n8n before execution.

Troubleshooting

  • Invalid Credentials or Authentication Failure: If the node cannot create an API instance, it throws an error: "No API instance found. Please make sure to provide valid credentials." Ensure that the API key credential includes valid cookie, IMEI, and user agent values.
  • User ID Not Found or Invalid: Providing an incorrect or non-existent user ID may cause the API call to fail. Verify the user ID before running the node.
  • API Rate Limits or Network Issues: Temporary failures might occur due to network problems or API rate limits. Consider enabling "Continue On Fail" to handle intermittent errors gracefully.
  • Error Messages: Errors thrown during execution will include the message from the underlying API call. Review these messages to identify issues such as permission problems or invalid parameters.

Links and References

Discussion