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 Media Group

AI-generated

Summary

Send a Telegram media group to the specified chat using URLs, Telegram file IDs, or binary properties from the input item. The operation can add a caption to the first item and optionally reply to a message; it supports Redis rate limiting when enabled.

Inputs

  • Bot Token (required) — Telegram bot token; defaults to the input item's access_token or token.
  • Chat ID (required) — Destination chat ID; defaults to the input item's chatId or channel.external_id.
  • Media Group Source — Choose a list of URLs/file IDs or binary property names from the input item.
  • Media Items (URLs or File IDs) — For URL/file ID source, provide 2–10 comma-separated values or an expression returning an array. Values are sent in order.
  • Binary Property Names — For binary source, provide 2–10 comma-separated binary property names present on the input item.
  • Media Types (for group) — Comma-separated item types in the same order: photo, video, audio, or document. Missing type entries default to photo.
  • Caption — Optional caption applied to the first photo or document in the group.
  • Caption Entities — Optional JSON array of Telegram caption entities; applied to the first photo item. The source also passes entities for a first document, but the helper does not apply them there.
  • Reply to Message ID — Positive Telegram message ID to reply to; zero or omitted means no reply.
  • Reply Markup — JSON reply markup property is displayed for this operation, but the implementation does not pass it to the media-group request.
  • Use Redis Rate Limit — When enabled and Redis credentials are available, throttles requests per bot; API calls also retry eligible 429 errors.

Output shape

On success, each input item produces an output item whose JSON contains a messages array of Telegram messages returned for the media group.

The node has Success, User Blocked (403), and Error outputs. A 403 is routed to User Blocked with the input JSON plus error details. Other failures are thrown unless n8n Continue On Fail is enabled, in which case they go to Error with the input JSON and error details. The operation requires 2–10 media items; invalid counts or missing binary data cause errors.

Links

Discussion