Actions9
Overview
This node manages Zalo users, specifically providing an operation to unblock a user by their User ID. It is useful in scenarios where you have previously blocked a user on the Zalo platform and want to restore communication or interaction with them. For example, if a user was mistakenly blocked or if you want to allow messages from a user again, this node can perform that unblock action programmatically.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user to unblock |
Output
The node outputs JSON data containing the status of the unblock operation and the response from the Zalo API. The structure typically looks like:
{
"status": "success",
"response": { /* detailed response from Zalo API */ }
}
Each output item corresponds to an input item, paired by index. If an error occurs for a specific item and error handling is enabled, the output will contain an error field describing the issue.
Dependencies
- Requires a valid Zalo API credential with authentication details such as cookie, IMEI, and user agent.
- Uses the Zalo API client internally to perform login and user management operations.
- The node expects these credentials to be configured in n8n beforehand.
Troubleshooting
Common issues:
- Invalid or expired credentials may cause login failure.
- Incorrect User ID format or non-existent user may result in errors from the Zalo API.
- Network connectivity problems can prevent successful API calls.
Error messages:
"Login failed": Indicates the node could not authenticate with Zalo using provided credentials. Verify your API key/credentials.- Errors returned from the Zalo API are passed through; check the error message for details (e.g., user not found).
- If "Continue on Fail" is disabled, the node will stop execution on the first error.
Links and References
- Zalo Official Developer Documentation (for API details)
- n8n documentation on Credentials and Error Handling
If you need further details about other operations or resources, feel free to ask!