Zalo User icon

Zalo User

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

Actions10

Overview

This node manages Zalo user interactions, specifically for the "User" resource and the "Đổi tên gợi nhớ" (Change Alias Name) operation. It allows you to change the alias name (a nickname or reminder name) of a Zalo user in your contacts. This is useful when you want to personalize how users appear in your contact list without changing their actual account names.

Common scenarios:

  • Personalizing contact names for easier recognition.
  • Organizing contacts with custom nicknames.
  • Automating updates of user aliases based on external data.

Example:
You have a list of user IDs and want to update their alias names to reflect recent changes or preferences. Using this node, you provide the user ID and the new alias name, and the node updates the contact accordingly.

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:

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

Example output JSON:

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

No binary data is produced by this operation.

Dependencies

  • Requires an active connection to the Zalo API via credentials that include authentication tokens such as cookies, device IMEI, and user agent strings.
  • The node depends on the external zca-js library to interact with the Zalo API.
  • Proper configuration of the Zalo API credential in n8n is necessary, including valid cookie and device information.

Troubleshooting

  • Invalid Credentials: If the node throws an error about missing or invalid API instance, ensure that the Zalo API credentials are correctly set up and contain valid cookie, IMEI, and user agent values.
  • User Not Found: Errors may occur if the provided User ID does not exist or is incorrect. Verify the User ID before running the node.
  • API Rate Limits or Restrictions: The Zalo API might limit requests; if you encounter errors related to rate limiting, consider adding delays or retries.
  • Continue On Fail: If enabled, the node will continue processing other items even if one fails, returning error messages in the output JSON under the error field.

Links and References

Discussion