Actions10
Overview
This node manages Zalo user interactions, specifically allowing you to unblock a user on the Zalo platform. It is useful in scenarios where you have previously blocked a user and want to restore communication with them. For example, if you manage customer relationships or social contacts via Zalo, this node can automate unblocking users based on certain triggers or workflows.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user to unblock |
Output
The node outputs a JSON object for each input item processed. The output JSON contains:
status: A string indicating the operation result, typically"Thành công"(meaning "Success" in Vietnamese).response: The raw response from the Zalo API confirming the unblock action.
Example output JSON:
{
"status": "Thành công",
"response": {
// API response details about the unblock operation
}
}
No binary data is produced by this node.
Dependencies
- Requires valid Zalo API credentials including an API key credential that provides cookie, IMEI, and user agent information.
- Uses the external
zca-jslibrary to interact with the Zalo API. - The node expects these credentials to be configured properly in n8n before execution.
Troubleshooting
Common issues:
- Invalid or expired credentials may cause login failure.
- Missing or incorrect User ID will prevent the unblock operation.
- Network or API errors from Zalo service could interrupt the process.
Error messages:
"No API instance found. Please make sure to provide valid credentials."
This indicates that the node failed to authenticate with Zalo due to missing or invalid credentials. Verify your API key and related settings.- Errors thrown during the unblock call will be reported per item unless "Continue On Fail" is enabled, in which case errors are returned as part of the output JSON under an
errorfield.
Links and References
- Zalo Official Developer Documentation
- n8n Documentation on Credentials
- zca-js GitHub Repository (for the underlying Zalo API client used)