Zalo User icon

Zalo User

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

Actions12

Zalo User → Đánh Dấu Tin Nhắn Chưa Đọc

AI-generated

Overview

This node is designed to interact with Zalo User messaging threads, specifically to mark messages as unread. It allows users to specify a particular conversation thread by its ID and type, then mark the messages within that thread as unread. This functionality is useful in scenarios where you want to programmatically manage message read statuses, for example:

  • Automatically marking important messages as unread to remind yourself to follow up later.
  • Managing message states in bulk for customer support workflows.
  • Integrating with other systems to synchronize message read/unread status.

Properties

Name Meaning
Thread ID The unique identifier of the user or conversation thread whose messages will be marked.
Thread Type The type/category of the user or thread (e.g., individual chat, group chat).

Output

The node outputs JSON data containing the status of the operation and the response from the underlying API call. Each output item corresponds to an input item processed, paired with the result of marking the message(s) as unread.

Example structure of one output item:

{
  "json": {
    "status": "success",
    "response": { /* API response details */ }
  },
  "pairedItem": {
    "item": 0
  }
}

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Zalo User service.
  • Depends on an external Zalo User API client library to perform the marking of messages as unread.
  • The node expects proper configuration of authentication credentials within n8n to access the Zalo User API.

Troubleshooting

  • Common Issues:

    • Invalid or missing Thread ID or Thread Type properties will cause the node to fail.
    • Authentication errors if the API key credential is not set up correctly.
    • Network or API downtime may lead to request failures.

  • Error Messages:

    • Errors related to missing credentials indicate that the API key must be configured.
    • API response errors typically include status codes and messages; ensure the Thread ID and Thread Type are valid.
    • If the node throws an error about no response or invalid response, verify network connectivity and API availability.

  • Resolution Tips:

    • Double-check the Thread ID and Thread Type values.
    • Confirm that the API key credential is properly configured and has necessary permissions.
    • Retry after some time if the issue is due to temporary API unavailability.

Links and References

Discussion