Actions10
- User Action Actions
- Message Action Actions
Overview
The node integrates with the Zalo Web platform to send messages as part of its "Message Action" resource, specifically supporting the "Send Message" operation. It allows sending styled text messages, optionally including attachments and quotes, to a specified user or chat identified by a unique user ID.
This node is beneficial in scenarios where automated communication via Zalo is needed, such as customer support notifications, marketing campaigns, or alert systems. For example, a business could automatically send styled promotional messages with images or documents attached to customers who have opted in.
Properties
| Name | Meaning |
|---|---|
| User ID | Unique identifier for the target chat or username. To find your chat ID, ask @get_id_bot on Zalo. |
| Message | The text content of the message to send. |
| Style | Styles to apply to parts of the message text. Multiple styles can be added, each specifying: - Msg: The substring in the message to style. - Style: One or more of [Big, Bold, Green, Indent, Italic, Orange, OrderedList, Red, Small, StrikeThrough, Underline, UnorderedList, Yellow]. - Index: Which occurrence of the substring to style (default 1). |
| Binary File | Boolean indicating whether the data to upload should be taken from a binary field. |
| Attachments | Attachments to add to the message. Each attachment is a string that can reference URLs or binary data fields. |
| Urgency | Urgency level of the message. Options are: Default, Important, Urgent. |
| Quote | JSON object representing a quote to include in the message. |
Output
The node outputs an array of items, each containing a json property with a data field holding the response from the Zalo API after sending the message. This typically includes confirmation details about the sent message.
If attachments are included and sourced from binary data, the node handles temporary file creation and cleanup internally but does not output binary data itself.
Dependencies
- Requires an API key credential for authenticating with the Zalo Web API.
- Uses internal helper functions for handling binary data and temporary files.
- Relies on external libraries for streaming and file system operations.
- Requires proper configuration of credentials within n8n to access the Zalo Web service.
Troubleshooting
Common Issues:
- Incorrect or missing User ID will cause the message sending to fail.
- Invalid or inaccessible attachment URLs or binary data references may result in errors or incomplete message delivery.
- Styling substrings not found in the message text will have no effect.
- Missing or invalid API credentials will prevent authentication.
Error Messages:
- Errors related to file downloads ("Error downloading file from URL") indicate issues fetching attachments; verify URLs and network connectivity.
- Authentication failures suggest checking the API key credential setup.
- If the node throws errors about unsupported operations or resources, ensure the correct Resource ("message") and Operation ("sendMessage") are selected.
Links and References
- Zalo Official Website
- Zalo Developer Documentation (for general API reference)
- n8n Documentation on Creating Custom Nodes