Actions22
- Get Actions
- Message Actions
- Friend Actions
- Group Actions
- Tool Actions
Overview
This node operation allows sending a voice message to a specified Zalo user or group chat. It is useful in scenarios where you want to automate voice notifications, alerts, or personalized audio messages through the Zalo messaging platform. For example, businesses can use this node to send voice reminders to customers or team members, or developers can integrate voice-based communication into workflows.
The node requires specifying the target conversation (user or group) and providing a URL to the voice file to be sent.
Properties
| Name | Meaning |
|---|---|
| User/Group Id | The ID of the Zalo user or group chat to which the voice message will be sent. |
| Thread Type | The type of conversation: either "User" (individual chat) or "Group" (group chat). |
| Voice URL | The URL of the audio file that contains the voice message to be sent. |
Output
The node outputs an array of JSON objects representing the result of the send voice message operation for each input item. Each object typically contains:
- A success indicator.
- Details about the sent message such as message ID or status.
- Error information if the sending failed.
The output does not include binary data; it focuses on metadata about the sent voice message.
Dependencies
- Requires an active connection to the Zalo API with appropriate authentication credentials (e.g., an API key or token).
- The voice message must be accessible via a valid URL.
- The node internally uses HTTP requests to interact with the Zalo messaging service.
- No additional external libraries beyond those bundled with n8n are required.
Troubleshooting
- Invalid User/Group ID: If the provided thread ID is incorrect or does not exist, the node will fail to send the message. Verify the ID corresponds to a valid Zalo user or group.
- Incorrect Thread Type: Ensure the thread type matches the nature of the thread ID (user vs. group). Mismatches may cause errors.
- Voice URL Issues: The voice URL must point to a valid audio file accessible over the internet. Broken links or unsupported formats will cause failures.
- Authentication Errors: Missing or invalid API credentials will prevent the node from communicating with Zalo's API.
- API Rate Limits: Sending too many messages in a short time may trigger rate limiting by Zalo, resulting in temporary failures.
- Error Messages: The node logs error details in its output. Common errors include network issues, permission denied, or invalid parameters. Review these messages to identify and fix problems.
Links and References
Note: This summary is based on static analysis of the provided source code and property definitions without executing the code.