Actions12
Overview
This node interacts with the Zalo platform to manage user-related actions. Specifically, the "Bỏ Chặn Người Dùng" (Unblock User) operation allows you to remove a block on a specified user by their User ID. This is useful in scenarios where you previously blocked a user and want to restore communication or interaction with them.
Practical examples include:
- Unblocking a user who was mistakenly blocked.
- Re-enabling interactions with a user after resolving a dispute.
- Managing user access dynamically based on business rules or user requests.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user to unblock. |
Output
The node outputs a JSON object containing at least two fields:
status: A string indicating the result status, typically"success"when the unblock operation completes successfully.response: The detailed response from the Zalo API regarding the unblock action, which may include confirmation or additional metadata.
Example output JSON structure:
{
"status": "success",
"response": { /* API response details */ }
}
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Zalo API.
- The node depends on an internal Zalo API client library that handles cookie, IMEI, and user agent management for authentication.
- Proper configuration of the Zalo API credential within n8n is necessary.
- The node expects valid session information (cookie, IMEI, user agent) to be available for API calls.
Troubleshooting
Common issues:
- Invalid or expired API credentials can cause authentication failures.
- Missing or incorrect User ID input will prevent the unblock operation.
- Network connectivity problems may lead to request timeouts or errors.
Error messages:
- If the node throws an error like "Failed to initialize Zalo API client," it indicates missing or invalid session data (cookie, IMEI, user agent). Ensure credentials are correctly set up.
- Errors related to the unblock operation usually contain the API's error message; verify the User ID is correct and the user is currently blocked.
- If the node continues on failure is enabled, errors per item will be returned in the output JSON under an
errorfield.
Resolution tips:
- Double-check the API key credential and refresh if needed.
- Confirm the User ID exists and is currently blocked.
- Verify network access to the Zalo API endpoints.
- Enable detailed logging in the node settings to get more insight into failures.