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 and need to programmatically unblock users based on certain triggers or workflows, this node facilitates that action.
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 result status, typically"Thành công"(which means "Success" in Vietnamese).response: The raw response from the Zalo API after attempting to unblock the user. This may include details about the unblock operation's success or any relevant metadata.
Example output JSON structure:
{
"status": "Thành công",
"response": { /* API response data */ }
}
No binary data output is produced by this node.
Dependencies
- Requires an API key credential to authenticate with the Zalo platform.
- Uses stored credentials including cookie, IMEI, and user agent strings to establish a session.
- Depends on the external
zca-jslibrary to interact with the Zalo API. - Requires proper configuration of the Zalo API credentials within n8n to function correctly.
Troubleshooting
Common issues:
- Invalid or expired credentials can cause authentication failures.
- Missing or incorrect User ID parameter will prevent the unblock operation.
- Network connectivity problems may lead to request timeouts or errors.
Error messages:
"No API instance found. Please make sure to provide valid credentials."
This indicates that the node could not establish a connection to the Zalo API due to missing or invalid credentials. Verify your API key and credential setup.- Errors returned from the Zalo API during the unblock attempt will be surfaced with their message. Ensure the User ID exists and is correct.
Resolution tips:
- Double-check the provided User ID is accurate and corresponds to a blocked user.
- Confirm that the API credentials are up-to-date and have necessary permissions.
- Enable "Continue On Fail" in the node settings if you want the workflow to proceed despite individual item errors.
Links and References
- Zalo Official Developer Documentation
- n8n Documentation on Credentials
- zca-js GitHub Repository (for the underlying Zalo API client library)