Actions16
Send Video
AI-generatedSummary
Send a video to a Telegram chat using the configured bot token. The node returns Telegram’s sent message on the Success output; 403 errors go to User Blocked, while other errors follow the node’s error handling settings.
Inputs
- Bot Token (required) — Bot token, defaulting to the input item’s access_token or token.
- Chat ID (required) — Telegram chat to send the video to; defaults to chatId or channel.external_id from the input item.
- Media Source — Choose URL or File ID, or Binary Data.
- Media (URL or File ID) — When Media Source is URL or File ID, provide a video URL or Telegram file_id. Defaults to media[0].url or url from the input item.
- Binary Property — When Media Source is Binary Data, name the input binary property containing the video; defaults to data.
- Caption — Optional caption for the video; defaults to caption or text from the input item.
- Caption Entities — Optional JSON array of Telegram caption entities; defaults to entities from the input item and is used when it parses as an array.
- Has Spoiler — When enabled, marks the video as a spoiler. Defaults to false.
- Reply to Message ID — Positive Telegram message ID to reply to; defaults to 0, which sends without a reply.
- Reply Markup — Optional JSON reply markup, such as a keyboard; defaults to reply_markup from the input item.
- Use Redis Rate Limit — Enable per-bot throttling using the optional Redis credential. Defaults to false.
Output shape
A Telegram Message object for each successfully sent video, on the Success output.
The node also has User Blocked (403) and Error outputs. A 403 is routed to User Blocked; other failures are thrown unless Continue On Fail is enabled, in which case they are routed to Error. Telegram 429 responses are retried when a retry_after value can be read from the error.
Examples
Example 1: Testing the operation
To try this operation, first configure Bot Token and Chat ID, then send a media URL/file ID or binary file, with optional caption and reply markup.