Actions16
Send Document
AI-generatedSummary
Send a document to a Telegram chat using the configured bot token. The document can come from a URL or Telegram file ID, or from an n8n binary property; optionally add a caption, caption entities, reply markup, or a reply target.
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 Source — Choose URL or File ID (default) or Binary Data.
- Media (URL or File ID) — Document URL or Telegram file_id, used when Media Source is URL or File ID.
- Binary Property — Name of the input item's binary property containing the document; used when Media Source is Binary Data. Defaults to data.
- Caption — Optional document caption; defaults to the input item's caption or text.
- Caption Entities — Optional JSON array of Telegram caption entities; defaults to the input item's entities.
- Reply to Message ID — Optional Telegram message ID to reply to; a value greater than zero is sent as reply_to_message_id.
- Reply Markup — Optional JSON reply markup, such as a keyboard; defaults to the input item's reply_markup.
- Use Redis Rate Limit — Enable per-bot throttling using the optional Redis credential; disabled by default.
Output shape
A Telegram Message object for each successfully sent document, routed through the Success output.
The node also has User Blocked (403) and Error outputs. A 403 is routed to User Blocked; other errors go to Error when n8n is set to continue using the error output, otherwise the execution throws. HTTP 429 responses are retried when Telegram supplies a retry_after value.
Examples
Example 1: A user might send a PDF guide when an order is confirmed.
The node sends a document to the chat ID on each input item, attaching a caption and optionally replying to a previous message.