Actions23
- Chat Actions
- Callback Actions
- File Actions
- Message Actions
Overview
The "Send Audio" operation of the Message resource in this Telegram node allows users to send audio files to a specified chat or channel on Telegram. It supports sending audio either by referencing an existing file on Telegram servers (using a file ID), providing an HTTP URL for Telegram to fetch the audio, or uploading binary audio data directly from the workflow.
This operation is useful in scenarios such as:
- Sending voice messages or music tracks automatically to a group or user.
- Broadcasting audio announcements or podcasts.
- Sharing audio content dynamically generated or retrieved within an automation workflow.
For example, you could automate sending a daily podcast episode to a Telegram channel or send personalized voice notes to users based on triggers in your system.
Properties
| Name | Meaning |
|---|---|
| Chat ID | Unique identifier for the target chat or username of the target channel (in the format @channelusername). Specifies where the audio will be sent. |
| Binary File | Boolean flag indicating whether the audio data should be taken from a binary field in the input data. |
| Input Binary Field | The name of the binary property containing the audio file data to upload when Binary File is true. |
| Audio | The audio file to send when not using binary data. Can be a Telegram file ID (to reuse an existing file) or an HTTP URL for Telegram to fetch the audio. |
| Reply Markup | Additional interface options for the message. Options include: Force Reply, Inline Keyboard, None, Reply Keyboard, and Reply Keyboard Remove. |
| Performer | Name of the performer of the audio track. |
| Title | Title of the audio track. |
| Caption | Caption text to accompany the audio message (0-1024 characters). |
| Disable Notification | Whether to send the message silently without notification sounds. |
| Duration | Duration of the audio clip in seconds. |
| Thumbnail | Thumbnail image for the audio file in JPEG format, less than 200 kB, with width and height not exceeding 320 pixels. Optional if server-side thumbnail generation is supported. |
| Parse Mode | How to parse the caption text. Options are Markdown (Legacy), MarkdownV2, or HTML. |
| Reply To Message ID | If replying to a specific message, the ID of that original message. |
| Message Thread ID | Identifier of the forum topic (used for threaded messages). |
| Reply Markup Details | Depending on the selected Reply Markup option, additional fields can be configured, such as buttons for inline keyboards or custom reply keyboards with options like resizing or selective display. |
| File Name | When uploading binary data, the file name to use for the audio file. Required if the binary data does not have a filename property set. |
Output
The node outputs JSON data representing the response from the Telegram API after sending the audio message. This typically includes details about the sent message such as message ID, date, chat information, and audio metadata.
If the audio was uploaded as binary data, the node handles the binary stream internally but the output JSON remains the main structured result.
Dependencies
- Requires a valid Telegram Bot API authentication token configured in n8n credentials.
- For binary uploads, the input data must contain the audio file in a binary property with a proper filename.
- Internet access is required for sending messages and optionally for Telegram to fetch audio files via URLs.
Troubleshooting
- Missing File Name Error: When uploading binary audio data, if the file name is not provided either in the binary property or manually in the node's "File Name" field under Additional Fields, the node will throw an error. Ensure the binary data includes a filename or specify it explicitly.
- Invalid Chat ID: Providing an incorrect or inaccessible chat ID or channel username will cause the Telegram API to reject the request. Verify the chat ID or username is correct and the bot has permission to send messages there.
- Unsupported Audio Format: Telegram supports certain audio formats; sending unsupported formats may cause failures. Confirm the audio file format is compatible.
- API Rate Limits: Sending too many messages in a short time may trigger Telegram rate limits. Implement delays or error handling to manage this.
- Network Issues: Connectivity problems can cause request failures. Check network status and retry as needed.