Send Voice Message
AI-generatedOverview
This node sends a voice message to a specified conversation thread on a messaging platform. It supports sending either a direct URL to an audio file or a base64-encoded audio data URL. The node is useful for automating voice notifications, alerts, or personalized voice messages in user or group chats.
Practical examples include:
- Sending a voice alert to a user when a specific event occurs.
- Broadcasting a voice message to a group chat for announcements.
- Automating customer support responses with pre-recorded voice clips.
Properties
| Name | Meaning |
|---|---|
| Voice File | URL of the voice file or base64 data URL (e.g., data:audio/mp3;base64,...) to send. |
| Thread ID | Identifier of the conversation thread where the voice message will be sent. |
| Thread Type | Type of the conversation thread: "User" (individual chat) or "Group" (group chat). |
| Advanced Options | Collection of optional settings: - Time to Live (ms): Duration the message remains valid; 0 means unlimited. |
Output
The node outputs JSON data containing details about the sent voice message, including:
success: Boolean indicating if the operation was successful.operation: The performed operation name ("sendVoice").threadId: The ID of the conversation thread targeted.threadType: The type of the thread ("user" or "group").messageId: Identifier of the sent message.response: Raw response data from the messaging API.timestamp: Timestamp of when the message was sent.debug: Debug information including a snippet of the voice file URL and advanced options used.
No binary data output is produced by this node.
Dependencies
- Requires an API client configured to interact with the messaging platform's voice message endpoint.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node expects the environment to have network access to the provided voice file URLs if using remote files.
Troubleshooting
- Invalid Voice File: If the voice file URL or base64 data is invalid or missing, the node throws an error indicating the voice file must be a valid URL or base64 audio data URL.
- Missing Credentials: Errors occur if the API authentication token is not set or invalid. Ensure proper credential configuration.
- Thread Not Found: Providing an incorrect or non-existent thread ID may cause failures in sending the message.
- Network Issues: If the voice file URL is unreachable, the message sending will fail.
- Time to Live Misconfiguration: Setting TTL to negative values or extremely high values might cause unexpected behavior.
To resolve errors:
- Verify the voice file input is correctly formatted.
- Confirm that the thread ID and type are correct.
- Check API credentials and permissions.
- Ensure the voice file URL is accessible from the execution environment.
Links and References
- Base64 Audio Data URL Format
- Messaging platform API documentation (refer to your platform's official docs for sending voice messages)
- n8n documentation on creating custom nodes and handling credentials