Zalo User

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

Actions12

Zalo User Actions

Overview

This node manages interactions with Zalo users, a popular messaging platform. Specifically, the "Đánh Dấu Tin Nhắn Chưa Đọc" (Mark Message As Unread) operation allows users to mark messages in a conversation thread as unread. This can be useful for reminding oneself to revisit certain conversations later or managing message notifications.

Practical scenarios include:

Automatically marking important messages as unread to ensure follow-up.
Managing message states programmatically in bulk workflows.
Integrating Zalo message status updates into broader automation processes.

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 a JSON object containing:

status: A string indicating success, typically "Thành công" (meaning "Success").
response: The raw response from the Zalo API after attempting to mark the message as unread.

This output confirms whether the operation succeeded and provides any additional data returned by the API.

Dependencies

Requires an API key credential to authenticate with the Zalo platform.
Uses stored cookie, IMEI, and user agent information from credentials or input data to establish a session.
Depends on the external zca-js library for interacting with the Zalo API.

Troubleshooting

Common issues:
- Invalid or expired credentials may cause authentication failures.
- Incorrect Thread ID or Thread Type values can lead to errors or no effect.
- Network connectivity problems might prevent successful API calls.
Error messages:
- "No API instance found. Please make sure to provide valid credentials."
  Means the node could not authenticate with Zalo. Verify that the API key credential is correctly configured and valid.
- Errors related to invalid parameters usually indicate incorrect or missing Thread ID or Thread Type. Double-check these inputs.
- If the node throws errors but continueOnFail is enabled, it will output error details per item instead of stopping execution.