Actions9
Overview
This node enables interaction with Zalo user accounts through various operations such as sending friend requests, accepting friend requests, blocking/unblocking users, changing account settings or avatar, retrieving user information, and more. It is particularly useful for automating social interactions on the Zalo platform, managing contacts, and customizing user profiles programmatically.
A practical example is automating the process of sending personalized friend requests to multiple users by specifying their user IDs and accompanying messages, which can save time in marketing or community-building scenarios.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the Zalo user to whom the friend request will be sent. |
| Message | The message text that accompanies the friend request being sent to the specified user. |
Output
The node outputs JSON data containing:
status: A string indicating the success status of the operation (e.g., "Thành công" meaning "Success").response: The raw response object returned from the Zalo API for the performed operation.
Each output item is paired with its corresponding input item index.
No binary data output is produced by this operation.
Dependencies
- Requires a valid Zalo API credential including authentication details such as cookies, device IMEI, and user agent.
- Uses an external library (
zca-js) to interact with the Zalo API. - The node expects these credentials to be configured properly within n8n to establish a session with Zalo.
Troubleshooting
Common Issues:
- Invalid or expired credentials may cause login failure, resulting in no API instance found error.
- Incorrect or missing User ID or Message parameters will cause the operation to fail.
- Network issues or API rate limits might interrupt requests.
Error Messages:
"No API instance found. Please make sure to provide valid credentials."
Resolution: Verify that the Zalo API credentials are correctly set up and not expired.- Errors related to specific user operations will include the error message from the API; enabling "Continue On Fail" allows processing subsequent items despite errors.