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 social engagement workflows, such as:
- Automatically sending friend requests to new leads or contacts imported from other systems.
- Personalizing outreach by including a custom message with each friend request.
- Integrating Zalo user management into broader marketing or CRM automation pipelines.
For example, a business could use this node to automatically send friend requests to customers who sign up on their website, including a welcome message to start a conversation.
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 for a personalized note. |
Output
The node outputs JSON data for each input item processed. The output JSON 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. This may include details about the request status or any metadata provided by the API.
Example output JSON structure:
{
"status": "Thành công",
"response": {
// API response details here
}
}
No binary data output is produced by this node.
Dependencies
- Requires an API key credential to authenticate with the Zalo platform.
- Uses the
zca-jslibrary internally to interact with the Zalo API. - The node expects valid authentication credentials including cookie, device IMEI, and user agent information.
- Proper configuration of these credentials in n8n is necessary for successful API calls.
Troubleshooting
- Invalid Credentials: If the node throws an error stating no API instance was found, verify that the provided API credentials are correct and contain valid cookie, IMEI, and user agent values.
- API Errors: Errors returned from the Zalo API (e.g., invalid user ID, rate limits) will be surfaced as node errors unless "Continue On Fail" is enabled, in which case the error message will appear in the output JSON under
error. - Missing Required Parameters: Ensure that both "User ID" and "Message" fields are provided; otherwise, the node will fail.
- Network Issues: Connectivity problems can cause timeouts or failures; check network access to the Zalo API endpoints.
Links and References
(Note: The above links are general references; specific API details depend on the used SDK and credentials.)