Actions4
- Zalo Send Message Actions
Overview
This node allows sending voice messages through the Zalo messaging platform. It is designed to send audio content as a message to either individual users or groups within a specified conversation thread on Zalo.
Common scenarios where this node is beneficial include:
- Automating customer support by sending pre-recorded voice responses.
- Broadcasting voice announcements to group chats.
- Integrating voice notifications into workflows, such as alerts or reminders.
For example, a business could use this node to automatically send a voice message to a customer’s chat thread confirming an appointment or order status.
Properties
| Name | Meaning |
|---|---|
| Thread ID | The unique identifier of the conversation thread where the voice message will be sent. |
| Type | The type of the message recipient: 0 for an individual user, 1 for a group chat. |
| Message | The content of the voice message to be sent (likely a URL or reference to the audio). |
Output
The node outputs a JSON object with the following structure:
success: A boolean indicating whether the message was sent successfully.response: The raw response from the Zalo API after attempting to send the message.threadId: The ID of the thread where the message was sent.threadType: The type of the thread (user or group).messageContent: The content details of the sent message.
No binary data output is indicated in the code; the output focuses on JSON metadata about the sent voice message.
Dependencies
- Requires an authenticated connection to the Zalo API using an API key credential.
- Uses internal helper libraries for handling Zalo API interactions and file operations (e.g., saving images or videos if attachments are involved).
- Node expects environment setup with valid Zalo API credentials including cookie, IMEI, and user agent information.
Troubleshooting
- Zalo API not initialized: This error occurs if the node cannot establish a connection to the Zalo API, likely due to missing or invalid credentials. Ensure that the API key and related authentication details are correctly configured.
- Cannot send typing event: This warning indicates failure to send a "typing" indicator before the message. It does not block message sending but may indicate network or permission issues.
- Video ready errors: If the node is extended to handle video messages, errors related to downloading or processing video files might occur. Verify URLs and file accessibility.
- Message sending failures: Could be caused by invalid thread IDs, incorrect message types, or API rate limits. Double-check input parameters and API quotas.
Links and References
- Zalo Official API Documentation — For detailed API usage and authentication.
- n8n Documentation — For general guidance on creating and using custom nodes.
This summary is based solely on static analysis of the provided source code and property definitions.