Zalo User icon

Zalo User

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

Actions10

Overview

This node manages interactions with Zalo users, specifically providing operations to handle friend requests, user blocking, profile updates, retrieving user information, and message management within Zalo. The "Thu hồi tin nhắn" (Undo Message) operation allows users to revoke or delete a previously sent message in a conversation thread.

Common scenarios for this node include:

  • Automating friend request acceptance or sending.
  • Managing user blocks/unblocks.
  • Updating user profile settings programmatically.
  • Retrieving detailed user info or friends list.
  • Undoing messages that were sent by mistake or need to be retracted.

For example, the "undoMessage" operation can be used in a customer support chatbot workflow to automatically retract incorrect or sensitive messages sent to a user.

Properties

Name Meaning
Thread ID The identifier of the conversation thread where the message was sent.
Thread Type The type/category of the user or conversation thread.
msgId The unique ID of the message to be undone (revoked).
cliMsgId The client-side message ID corresponding to the message to be undone.

Output

The output JSON contains:

  • status: A string indicating the success status, typically "Thành công" meaning "Success".
  • response: The raw response from the Zalo API after attempting to undo the message. This may include confirmation details or error information if the operation failed.

Example output structure:

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

No binary data is output by this node.

Dependencies

  • Requires an API key credential to authenticate with the Zalo platform.
  • Uses the zca-js library internally to interact with Zalo's API.
  • Requires valid cookie, IMEI, and user agent values either from credentials or input data for authentication.
  • Must be configured with proper Zalo API credentials in n8n.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials causing authentication failure.
    • Incorrect threadId, msgId, or cliMsgId leading to unsuccessful undo attempts.
    • Network or API rate limiting errors from Zalo.

  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      Means the node could not authenticate with Zalo. Check your API credentials and ensure they are correctly set.
    • Errors returned from the Zalo API will be included in the response field; verify IDs and parameters are correct.

  • To resolve errors, verify all required properties are provided and valid, refresh credentials if needed, and check network connectivity.

Links and References

Discussion