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 "Đổi Tên Gợi Nhớ" (Change Alias Name) operation allows you to update the alias name (a nickname or a custom display name) of a specific Zalo user in your contacts. This is useful when you want to personalize how contacts appear in your Zalo app or system by assigning memorable or meaningful names.

Practical examples:

  • Automatically updating contact nicknames based on CRM data.
  • Personalizing friend lists with aliases for easier identification.
  • Managing large contact lists by setting aliases programmatically.

Properties

Name Meaning
User ID The unique identifier of the Zalo user whose alias name you want to change.
Alias Name The new alias name (nickname) to assign to the specified user.

Output

The output JSON contains two main fields:

  • status: A string indicating the success status, typically "Thành công" which means "Success".
  • response: The raw response from the Zalo API after attempting to change the alias name. This may include details about the updated alias or confirmation data.

Example output JSON:

{
  "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 to connect to the Zalo platform.
  • Uses stored credentials including cookie, IMEI, and user agent strings for authentication.
  • Depends on the external zca-js library to interact with the Zalo API.
  • Requires proper configuration of the Zalo API credentials within n8n.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials can cause authentication failures.
    • Incorrect User ID may result in errors or no changes applied.
    • Network connectivity problems can prevent API calls from succeeding.
  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      Resolution: Verify that the Zalo API credentials are correctly set up and valid.
    • Errors related to invalid parameters usually indicate missing or incorrect User ID or Alias Name inputs.
    • If the node fails but "Continue On Fail" is enabled, error details will be included in the output JSON under the error field.

Links and References

Discussion