Actions22
- Get Actions
- Message Actions
- Friend Actions
- Group Actions
- Tool Actions
Overview
This node enables sending a voice message to a specified Zalo user or group chat. It is useful in scenarios where you want to automate voice communication via the Zalo messaging platform, such as sending alerts, notifications, or personalized voice messages to users or groups.
Practical examples include:
- Sending a voice alert to a support team group when a critical incident occurs.
- Delivering personalized voice greetings or reminders to individual users.
- Automating voice-based marketing campaigns by sending prerecorded audio clips.
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 | Specifies whether the recipient is a User or a Group. Options: User, Group. |
| Voice URL | The URL of the audio file to be sent as the voice message. |
Output
The node outputs JSON data representing the result of the send operation. This typically includes confirmation details such as message IDs, status, timestamps, or error information if the send failed.
If the node supports binary data output (not explicitly shown here), it would represent the voice message content or related media metadata.
Dependencies
- Requires an active connection to the Zalo messaging platform API.
- Needs valid API authentication credentials configured in n8n (e.g., an API key or token).
- The
Voice URLmust point to an accessible audio file (e.g., hosted on a public server or cloud storage).
Troubleshooting
- Invalid User/Group ID: If the provided
threadIddoes not correspond to a valid user or group, the API call will fail. Verify the ID is correct and that the bot has permission to message the target. - Incorrect Thread Type: Ensure the
threadTypematches the type of the recipient ID (user vs. group). Mismatches can cause errors. - Unreachable Voice URL: The audio file URL must be publicly accessible. Private URLs or inaccessible files will cause the send operation to fail.
- Authentication Errors: Missing or invalid API credentials will prevent the node from sending messages. Check credential configuration.
- API Rate Limits: Excessive requests may trigger rate limiting by Zalo. Implement retries or delays as needed.
Common error messages usually indicate one of the above issues and should be resolved by verifying inputs and credentials.
Links and References
- Zalo Official API Documentation (for detailed API usage)
- n8n Documentation (for general node and credential setup)
Note: Internal implementation details, obfuscated code, and internal credential names have been omitted for clarity and security.