Zalo User icon

Zalo User

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

Actions10

Overview

This node manages interactions with Zalo users, specifically providing operations to handle friend requests, user info, messaging, and account settings on the Zalo platform. 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 management (accepting, sending, blocking/unblocking).
  • Retrieving or updating user profile information.
  • Managing friends list and aliases.
  • Undoing messages that were sent by mistake or need to be retracted.

Practical example:
If you accidentally sent a wrong message to a contact on Zalo, you can use the "Undo Message" operation to revoke that message programmatically via this node.

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 response object returned from the Zalo API after attempting to undo the message. This usually includes details about the undo operation result.

Example output JSON structure:

{
  "status": "Thành công",
  "response": {
    // Details about the undo message operation result
  }
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential to authenticate with the Zalo platform.
  • Uses stored cookie, device IMEI, and user agent information for authentication.
  • Depends on the external zca-js library to interact with the Zalo API.
  • Requires proper configuration of credentials within n8n to provide valid authentication tokens.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials may cause authentication failures.
    • Incorrect threadId, threadType, msgId, or cliMsgId parameters will prevent successful message revocation.
    • Network connectivity problems can interrupt API calls.

  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      Means the node could not authenticate with Zalo API. Check your API key and credential setup.
    • Errors related to invalid parameters will typically indicate which input is incorrect. Verify all required IDs are correct and correspond to existing messages and threads.

  • To resolve errors, ensure:

    • Credentials are up-to-date and correctly configured.
    • Input parameters match actual Zalo user and message identifiers.
    • Network access to Zalo API endpoints is available.

Links and References

Discussion