Zalo User icon

Zalo User

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

Actions10

Overview

This node manages Zalo user account operations, specifically for the "Zalo User" resource. The selected operation "Thay đổi cài đặt tài khoản" (Change Account Setting) allows updating a user's profile information such as display name, date of birth, and gender.

Typical use cases include automating profile updates in bulk or integrating Zalo user management into workflows where user data needs to be synchronized or modified programmatically. For example, a company could update employee profiles on Zalo after importing new HR data.

Properties

Name Meaning
Name Display name of the Zalo user to set on the account
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, e.g., "vi" for Vietnamese or "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 updating the profile.

Example output JSON structure:

{
  "status": "Thành công",
  "response": {
    // API response details about the updated profile
  }
}

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential to authenticate with the Zalo platform.
  • Uses a third-party library (zca-js) to interact with the Zalo API.
  • Node expects credentials to provide cookie, IMEI, and user agent strings for authentication.
  • Proper configuration of these credentials in n8n is necessary for successful API calls.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials leading to authentication failure.
    • Incorrect date format for the Date of Birth property causing API errors.
    • Missing required fields like Name, Date of Birth, or Gender.

  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      Means the node failed to authenticate with Zalo. Check that the API key credential is correctly configured and valid.
    • Errors thrown during execution will include the message from the underlying API call. If continueOnFail is enabled, errors will be returned in the output JSON under the error field.

  • Resolution tips:

    • Verify all required input properties are provided and correctly formatted.
    • Ensure the API credential includes valid cookie, IMEI, and user agent values.
    • Enable continueOnFail to handle partial failures gracefully in batch executions.

Links and References

Discussion