Zalo User icon

Zalo User

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

Actions12

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 memorable name) of a specific Zalo user identified by their user ID. This is useful in scenarios where you want to personalize or organize your contacts by assigning custom names that are easier to remember.

Practical examples:

  • Automatically updating contact nicknames based on CRM data.
  • Renaming users in bulk after importing contacts from another system.
  • Personalizing friend lists with meaningful aliases for better identification.

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 of the operation, typically "Thành công" which means "Success".
  • response: The raw response returned 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 is output by this node.

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.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials can cause login failures.
    • Incorrect user IDs may result in errors or no changes.
    • Network connectivity problems can prevent API calls.

  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      Means the node could not authenticate with Zalo. Verify that the API key and related credentials are correctly configured.
    • Errors thrown during execution will include the message from the underlying API call. If continueOnFail is enabled, errors for individual items will be included in the output JSON under the error field.

  • Resolution tips:

    • Ensure all required credentials are set and valid.
    • Double-check the user ID values passed to the node.
    • Enable continueOnFail to handle partial failures gracefully.

Links and References

Discussion