Zalo User icon

Zalo User

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

Actions9

Overview

This node interacts with the Zalo platform to manage user-related actions, specifically allowing you to block a user by their User ID. It is useful in scenarios where you want to programmatically restrict certain users from interacting with your Zalo account or application, such as blocking spam accounts or unwanted contacts.

A practical example: If you receive messages from a user that you want to block, you can use this node to automate the blocking process by providing the user's ID, instead of manually blocking them through the Zalo app.

Properties

Name Meaning
User ID The unique identifier of the user you want to block on Zalo.

Output

The node outputs JSON data containing:

  • status: A string indicating the success status of the block operation (e.g., "success").
  • response: The detailed response from the Zalo API regarding the block action, which may include confirmation or additional metadata.

The output is paired with the input item index for traceability.

No binary data output is produced by this node.

Dependencies

  • Requires valid Zalo API credentials configured in n8n to authenticate requests.
  • Uses an external Zalo API client library to perform operations.
  • The node expects proper API authentication tokens and session cookies to be available and valid.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials will cause authentication failures.
    • Providing an incorrect or non-existent User ID will result in errors or no effect.
    • Network connectivity problems can prevent communication with the Zalo API.

  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      This indicates missing or invalid API credentials; verify and reconfigure your Zalo API authentication in n8n.
    • Errors returned from the Zalo API (e.g., user not found) will be included in the output JSON under an error field if "Continue On Fail" is enabled.
    • General request failures will throw exceptions; enabling "Continue On Fail" allows processing other items despite individual errors.

Links and References

Discussion