Zalo User icon

Zalo User

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

Actions9

Overview

This node manages Zalo user accounts by interacting with the Zalo platform through an API. It supports various operations such as accepting or sending friend requests, blocking/unblocking users, changing account avatars, updating account settings, retrieving user information, listing friends, and finding users by phone number.

The specific operation "Thay đổi cài đặt tài khoản" (Change Account Setting) allows updating a user's profile details including display name, date of birth, gender, and language preference.

Common scenarios:

  • Automating updates to user profiles in bulk.
  • Integrating Zalo user management into workflows for customer support or marketing.
  • Synchronizing user data from other systems into Zalo accounts.

Example:
A marketing team could use this node to update the language preference and display names of multiple Zalo users based on their regional campaigns automatically.

Properties

Name Meaning
Name Display name of the Zalo user to be set.
Date of Birth User's date of birth in the format YYYY-MM-DD.
Gender User's gender; options are Male (1), Female (2), Other (3).
Language Optional language code for the user interface, e.g., "vi" for Vietnamese, "en" for English.

Output

The output JSON contains:

  • status: A string indicating success, typically "Thành công" (Success).
  • response: The raw response object returned from the Zalo API after performing the change account setting operation.

Each output item is paired with its corresponding input item index.

No binary data output 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 external zca-js library to interact with the Zalo API.
  • The node expects these credentials to be configured properly in n8n before execution.

Troubleshooting

  • No API instance found error: This occurs if the credentials are missing or invalid. Ensure the API key credential is correctly set up with valid cookie, IMEI, and user agent values.
  • API call failures: Could be due to network issues, expired tokens, or incorrect parameter formats. Verify all input parameters especially date format and gender value.
  • Continue on Fail: If enabled, errors for individual items will be captured in the output JSON under an error field instead of stopping the entire workflow.

Links and References

Discussion