Zalo User icon

Zalo User

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

Overview

This node manages Zalo user interactions, specifically allowing operations related to a Zalo user's contacts and profile. The "Đổi tên gợi nhớ" (Change Alias Name) operation lets you update the alias name (a nickname or memorable name) of a specific user in your Zalo contact list.

Common scenarios where this node is useful include:

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

For example, you could use this node to automatically rename a contact after receiving updated information from a CRM system or to standardize naming conventions across your contact list.

Properties

Name Meaning
User ID The unique identifier of the Zalo user whose alias name you want to change.
Alias Name The new alias (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 confirming the alias name change.

Example output JSON:

{
  "status": "Thành công",
  "response": {
    // API response details about the alias name change
  }
}

No binary data is produced by this operation.

Dependencies

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

Troubleshooting

  • Invalid Credentials: If the node throws "No API instance found," it means the provided credentials are invalid or incomplete. Ensure the API key credential includes valid cookie, IMEI, and user agent values.
  • User Not Found: Errors may occur if the specified User ID does not exist or is not accessible. Verify the User ID is correct.
  • Permission Issues: The API might reject requests if the authenticated user lacks permission to change the alias for the target user.
  • Network or API Errors: Temporary network issues or API downtime can cause failures. Retry after some time or check Zalo API status.

To handle errors gracefully, enable "Continue On Fail" in the node settings to process subsequent items even if one fails.

Links and References

Discussion