Actions25
- 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 by providing the target thread ID, thread type (user or group), and a URL pointing to the voice audio file. It is useful in scenarios where automated voice notifications, alerts, or messages need to be sent programmatically via Zalo's messaging platform.
Practical examples include:
- Sending voice reminders or alerts to customers or team members.
- Broadcasting voice announcements to a group chat.
- Automating customer support voice messages.
Properties
| Name | Meaning |
|---|---|
| User/Group Id | The unique identifier of the Zalo user or group 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 containing the voice message to send. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. Each object contains the result of the send voice message operation, typically including success status and any response data from the Zalo API.
If the node supports binary data output (not explicitly shown here), it would represent the voice message content or related media metadata.
Dependencies
- Requires access to the Zalo messaging API.
- Needs an API key or authentication token configured in n8n credentials for authorization with Zalo.
- The voice message must be accessible via a publicly reachable URL.
Troubleshooting
- Invalid Thread ID: If the provided user/group ID is incorrect or does not exist, the API call will fail. Verify the ID is correct.
- Incorrect Thread Type: Ensure the thread type matches the ID type (user vs group).
- Voice URL Issues: The voice URL must point to a valid audio file accessible over the internet. Invalid URLs or unsupported formats will cause errors.
- Authentication Errors: Missing or invalid API credentials will prevent sending messages.
- API Rate Limits: Excessive requests may trigger rate limiting; handle retries accordingly.
- Error Messages: The node logs error details including message and stack trace. Review these logs to identify issues.
Links and References
- Zalo Official API Documentation (for message sending endpoints)
- n8n Documentation (for general node usage and credential setup)
Note: Internal variable names, credential types, and obfuscated code details have been omitted to comply with guidelines.