Actions6
- Conversation Settings Actions
Overview
This node manages conversation settings for Zalo chats, specifically allowing users to modify the visibility of conversations. The "Set Hidden Conversations" operation lets you hide or unhide specific chat threads by their ID and type (user or group). This is useful in scenarios where you want to programmatically control which conversations appear in the user's chat list, for example, to declutter the interface or manage privacy.
Practical examples:
- Automatically hiding archived or inactive conversations.
- Unhiding conversations when a user re-engages with a chat.
- Managing visibility of group chats versus individual chats based on business logic.
Properties
| Name | Meaning |
|---|---|
| Hidden | Boolean flag to hide (true) or unhide (false) the specified conversation. |
| Thread ID | The unique identifier of the conversation thread to be hidden or unhidden. |
| Thread Type | The type of conversation: either User (1) for individual chats or Group (2) for groups. |
Output
The output JSON contains:
status: A string indicating success, e.g.,"Thành công"("Success").response: The raw response from the underlying API call confirming the action.
Example output structure:
{
"status": "Thành công",
"response": { /* API response object */ }
}
No binary data is produced by this node.
Dependencies
- Requires valid Zalo API credentials including cookie, IMEI, and user agent information.
- Uses an external Zalo API client library (
zca-js) to perform operations. - The node expects these credentials to be configured in n8n under a generic API key credential for Zalo.
Troubleshooting
- Invalid Credentials: If the node throws "No API instance found," verify that the provided Zalo credentials (cookie, IMEI, user agent) are correct and active.
- Missing Thread IDs: An error will occur if no Thread ID is provided. Ensure the "Thread ID" property is set and not empty.
- Incorrect Thread ID Type: Using message IDs instead of user or group IDs may cause errors. Use the appropriate thread ID corresponding to the thread type.
- API Errors: Any API-level errors will be returned in the
responsefield. Check the raw response for details. - Continue On Fail: If enabled, the node will continue processing other items even if one fails, returning error messages per item.