Actions10
- User Action Actions
- Message Action Actions
Overview
This node integrates with the Zalo Web platform, enabling users to interact with Zalo messaging and social features programmatically. It supports operations such as sending messages (including styled text and attachments), sending videos, managing friend requests, retrieving user information, and handling QR codes.
Common scenarios where this node is beneficial include automating customer support conversations on Zalo, broadcasting messages or media to groups or individual users, managing contacts and friend requests, and integrating Zalo user data into workflows.
For example, a business could use this node to automatically send promotional messages with images or videos to customers who have opted in, or to fetch user profiles for CRM enrichment.
Properties
| Name | Meaning |
|---|---|
| Type | Selects the thread type: "User" (individual chat) or "Group" (group chat). |
Note: The provided property list only includes the "Type" property (threadType) with options User (0) and Group (1). The node internally uses other parameters like operation, resource, userId, fMessage (message content), style (text styles), attachments, urgency, and quote depending on the operation, but these were not included in the input properties JSON.
Output
The node outputs an array of items, each containing a json object with a data field holding the result of the executed operation. The structure of data varies depending on the operation performed:
- For message sending operations, it contains confirmation or message metadata.
- For user or group info retrieval, it contains user/group profile data.
- For friend request operations, it contains the status of the request.
- For video sending, it confirms the sent video details.
If binary data is involved (e.g., attachments), the node handles downloading or processing files internally but outputs only JSON data summarizing the operation results. Binary data is managed temporarily during execution and cleaned up afterward.
Dependencies
- Requires an API key credential for authenticating with the Zalo Web API.
- Uses internal helper functions and modules for login, fetching user info, sending messages, and file handling.
- Relies on environment supporting Node.js streams, temporary file creation, and Blob handling.
- No external service configuration beyond the API credential is explicitly required.
Troubleshooting
- Authentication errors: If the node fails to authenticate, ensure the API key credential is valid and has proper permissions.
- File download failures: Errors downloading attachments from URLs may occur if URLs are invalid or inaccessible; verify URLs and network connectivity.
- Invalid parameters: Providing incorrect user IDs, phone numbers, or unsupported operation types will cause errors; double-check parameter values.
- Binary data handling: When using binary attachments, ensure the input binary data is correctly formatted and accessible.
- Operation not supported: Using unsupported combinations of resource and operation parameters will result in no action or errors.
Common error messages:
"Thao tác không được hỗ trợ"(Operation not supported): Indicates an unsupported or invalid operation was requested.- Network or fetch errors when downloading files: Check URL validity and internet connection.
Links and References
- Zalo Official Website
- Zalo Developer Documentation
- n8n documentation on Creating Custom Nodes
If you need details on specific operations or additional properties, please provide those parameters.