Zalo User icon

Zalo User

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

Actions9

Overview

This node manages Zalo users by performing various user-related operations on the Zalo platform. Specifically, for the "Chặn người dùng" (Block User) operation under the "Zalo User" resource, it allows you to block a specific user by their User ID. This is useful in scenarios where you want to restrict interactions with certain users, such as blocking spam accounts or unwanted contacts.

Practical example:

  • Automatically block users who send inappropriate messages by passing their User IDs to this node.
  • Manage your Zalo account's privacy by programmatically blocking users based on custom criteria.

Properties

Name Meaning
User ID The ID of the user to be blocked

Output

The node outputs JSON data containing the status and response from the Zalo API regarding the block action. The structure typically looks like:

{
  "status": "success",
  "response": { /* API response details about the block operation */ }
}

Each output item corresponds to an input item, paired by index. There is no binary data output.

Dependencies

  • Requires a valid Zalo API authentication credential (an API key or token) configured in n8n credentials.
  • Uses stored cookie, IMEI, and user agent information from the credential to authenticate requests.
  • Depends on the external Zalo API service to perform user management actions.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication credentials may cause login failures.
    • Incorrect User ID format or non-existent user IDs will result in errors from the Zalo API.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • "Login failed": Indicates that the node could not authenticate with Zalo using provided credentials. Check and refresh your credentials.
    • API error responses related to user blocking usually include descriptive messages; verify the User ID and permissions.
    • If the node is set to continue on failure, errors are returned in the output JSON under an error field for each failed item.

Links and References

Discussion