Actions10
Overview
This node manages interactions with Zalo users, a popular messaging platform. Specifically, the "Gửi lời mời kết bạn" (Send Friend Request) operation allows you to send a friend request to a specified Zalo user along with a custom message.
Common scenarios where this node is useful include:
- Automating outreach by sending friend requests to multiple users programmatically.
- Integrating Zalo friend requests into marketing or customer engagement workflows.
- Personalizing connection requests with custom messages for better response rates.
For example, a business could use this node to automatically send friend requests to new leads collected from a CRM system, including a welcome message.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the Zalo user to whom the friend request will be sent. |
| Message | The text message that accompanies the friend request, allowing personalization. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains:
status: A string indicating the result status, typically"Thành công"meaning "Success".response: The raw response object returned from the Zalo API after sending the friend request.
Example output JSON structure for one item:
{
"status": "Thành công",
"response": {
// API response details here
}
}
No binary data is produced by this node.
Dependencies
- Requires valid Zalo API credentials including authentication cookies, device IMEI, and user agent strings.
- Uses an external library (
zca-js) to interact with the Zalo API. - The node expects these credentials to be configured in n8n beforehand.
Troubleshooting
- Invalid Credentials: If the node throws an error about missing or invalid API instance, verify that the Zalo API credentials are correctly set up with valid cookie, IMEI, and user agent values.
- User ID Errors: Ensure the provided User ID exists and is correct; otherwise, the API may reject the friend request.
- Message Length: Some APIs limit message length; if errors occur, check the message size.
- Continue on Fail: If enabled, the node will continue processing other items even if some fail, returning error messages per failed item.