Telegram Multi Actions icon

Telegram Multi Actions

Send all Telegram content types (text, media, video note, sticker, location, poll, dice, etc.) via Grammy. Supports URL, file_id, and n8n binary. Optional Redis rate limit, retry on 429, separate output for 403 (user blocked bot).

Actions16

Send Voice

AI-generated

Summary

Send a Telegram voice message to the specified chat using the bot token. The operation accepts a URL or Telegram file ID, or uploads a selected n8n binary property; it can include a caption, caption entities, reply markup, and a reply-to message ID.

Inputs

  • Bot Token (required) — Telegram bot token; defaults to the incoming item's access_token or token.
  • Chat ID (required) — Destination chat ID; defaults to the incoming item's chatId or channel.external_id.
  • Media Source (required) — Choose URL or File ID, or Binary Data.
  • Media (URL or File ID) (required) — URL or Telegram file_id to send when Media Source is URL or File ID; defaults to the incoming item's media[0].url or url.
  • Binary Property (required) — Name of the incoming item's binary property to upload when Media Source is Binary Data; defaults to data.
  • Caption — Optional voice message caption; defaults to the incoming item's caption or text.
  • Caption Entities — Optional JSON array of Telegram caption entities; defaults to the incoming item's entities.
  • Reply to Message ID — Telegram message ID to reply to; defaults to 0, which sends without a reply reference.
  • Reply Markup — Optional JSON reply markup, such as a keyboard; defaults to the incoming item's reply_markup.
  • Use Redis Rate Limit — Enable per-bot throttling with a Redis credential; defaults to false.

Output shape

A Telegram Message object for each successful send, on the Success output.

The node also has a User Blocked (403) output and an Error output. With Continue On Fail enabled, non-403 errors go to Error; otherwise they are thrown. Telegram 429 responses are retried when a retry_after value can be read. When Redis rate limiting is enabled but Redis credentials cannot be loaded, the node proceeds without Redis throttling.

Links

Discussion