Telegram Message TypeInstall

Summary

Detects a Telegram publication’s message type from its media, buttons, and content, then routes each input item to an output for the matching send kind. Use the result to choose a Telegram sending operation or pass the normalized fields to a compatible node.

Inputs

• Media — Array of media objects with url and optional type MIME type; accepts an array or a JSON string. Defaults to the incoming Media or media field, then an empty array. MIME type and URL determine the Telegram media type.
• Buttons — Array of button rows with layout and buttons; accepts an array or a JSON string. Defaults to the incoming Button or buttons field, then an empty array. A button URL creates a URL button; otherwise its action or label is used as callback data.
• Content — Message text or HTML, used as the trimmed output caption. Defaults to the incoming Content or content field, then an empty string.
• Output — Choose whether to merge detection fields into each input item (merge, the default) or return only the detection result (replace).

Output shape

Items routed across 11 named outputs: Send Text, Send Photo, Send Video, Send Video Note, Send Audio, Send Voice, Send Document, Send Animation, Send Sticker, Send Media Group, and Other/Unknown.

Each item includes type, sendKind, hasButtons, normalized media, caption, and reply_markup; multi: true is included for video notes, voice, stickers, or media groups with buttons. Media types are inferred from MIME type, with .tgs URLs treated as stickers; a single video file whose basename starts with circle or cirkle is classified as a video note, and audio/ogg or audio/opus as voice. Media groups with buttons are marked for multi-step sending. The node routes by sendKind and, for single media, its detected Telegram type; Other/Unknown receives any unmatched kind.

Links

• n8n community nodes installation guide