Actions6
- Conversation Settings Actions
Overview
This node manages conversation settings for Zalo chats, specifically allowing users to modify the visibility of conversations by setting them as hidden or visible. It is useful in scenarios where users want to programmatically control which conversations appear in their chat list without deleting or archiving them.
A practical example would be automating the hiding of certain group or user conversations based on specific criteria, such as muting notifications or decluttering the chat interface.
Properties
| Name | Meaning |
|---|---|
| Hidden | Boolean flag to hide (true) or show (false) the conversation |
| Thread ID | The unique identifier of the conversation thread to be hidden or shown |
| Thread Type | The type of conversation: either User (1) or Group (2) |
Output
The node outputs a JSON object containing:
status: A string indicating success, e.g.,"Thành công"("Success" in Vietnamese).response: The raw response from the Zalo API after attempting to set the hidden status of the conversation.
Example output JSON structure:
{
"status": "Thành công",
"response": { /* raw API response object */ }
}
No binary data output is produced by this operation.
Dependencies
- Requires valid Zalo API credentials including cookie, IMEI, and user agent information.
- Uses an external Zalo API client library (
zca-js) to interact with Zalo services. - The node expects these credentials to be configured properly in n8n before execution.
Troubleshooting
Common issues:
- Invalid or expired credentials may cause failure to authenticate with the Zalo API.
- Providing an incorrect or non-existent Thread ID will likely result in an error or no effect.
- Mismatched Thread Type (e.g., specifying User when the thread is actually a Group) can cause unexpected behavior.
Error messages:
"No API instance found. Please make sure to provide valid credentials."
Means the node could not initialize the Zalo API client due to missing or invalid credentials. Verify that the API key, cookie, IMEI, and user agent are correctly set.- Errors related to input validation (e.g., missing required Thread ID) will prompt the user to provide necessary parameters.
To resolve errors, ensure all required properties are provided and credentials are up to date.