Block 1 - Send back an image
- Type / Role
- n8n-nodes-base.telegram - telegram
- Config choices
- Version 1.1
This workflow is provided as-is. Please review and test before using in production.
Telegram Rich Output Helper Workflow Who is this for? Builders of Telegram chat‑bots, AI assistants, or notification services who already run n8n and need to convert long, mixed‑media answers from ...
n8n-nodes-base.telegram, n8n-nodes-base.if, n8n-nodes-base.executeworkflowtrigger, n8n-nodes-base.splitinbatches, n8n-nodes-base.splitout, n8n-nodes-base.code, n8n-nodes-base.limit, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Dmitry Mikheev.
Original n8n.io sourceWho is this for?
Builders of Telegram chat‑bots, AI assistants, or notification services who already run n8n and need to convert long, mixed‑media answers from an LLM (or any upstream source) into Telegram‑friendly messages.
Prerequisites
A Telegram bot created with @BotFather.
The bot’s HTTP API token saved as a Telegram API credential in n8n.
n8n ≥ 1.0 with the built‑in Telegram node still installed.
A parent workflow that calls this one via Execute Workflow and passes:
chatId — the destination chat ID (integer). output — a string that can contain plain text and HTTP links to images, audio, or video.output, deduplicates URLs, and classifies each by file extension. sendPhoto, sendAudio, sendVideo) so users get inline previews or players.additionalFields in the three “Send back” nodes. With this template in place, your users receive the complete message, playable media, and zero manual formatting – all within Telegram’s API limits.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Convert LLM output into rich Telegram messages — Auto-Media & smart chunking |
|---|---|
| Complexity | advanced |
| Nodes | 19 |
| Categories | Engineering |
| Author | Dmitry Mikheev |
| Published | 09 May 2025 |
Use the JSON export at /data/workflows/3961/3961.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Telegram Rich Output Helper Workflow Who is this for? Builders of Telegram chat‑bots, AI assistants, or notification services who already run n8n and need to convert long, mixed‑media answers from ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Engineering use case.