How many n8n templates use the Telegram node?

1,691 of the 13,574 public templates on n8n.io (12.5%), in our snapshot of 2026-10-20.

What is the Telegram node most often used with?

Code, which appears in 60.7% of its templates. The most distinctive partner is Error Trigger (lift 2.2×).

Why does the n8n Telegram node say "can't parse entities"?

With Parse Mode left empty, the node sends your text as Telegram legacy Markdown, so an unclosed _ or * fails. Add Parse Mode, choose HTML and escape the ampersand and angle brackets in the text.

Why does my Telegram trigger only work in test or in production?

A Telegram bot has a single webhook, so whichever URL registered last wins. Use a separate test bot.

How do I stop n8n adding a line to Telegram messages?

Turn off the attribution option in the node.

RecipeAgents / n8n nodes / Telegram

Node reference · data pulled Oct 26, 2026

n8n Telegram node: what the data shows

Sends and edits Telegram messages and files (Telegram node), and starts workflows from bot updates (Telegram Trigger).

1,691public templates use it (12.5% of 13,574)

69.5%of those also contain an AI node

54.9score out of 80 · rank 10 of 22

167commits to its source folder on GitHub

What it does

This page covers both nodes because they work as a pair: the trigger receives what users send, the node replies. The action node works on chats, callbacks, files and messages (27 operations), including a send-and-wait approval. The trigger registers a webhook for your bot and fires on the update types you pick: messages, callback queries, channel posts and more. It can be limited to chosen chat or user IDs.

Most Telegram templates in the library also include an AI node (see the AI share above). If you want to build a Telegram AI bot step by step, our Telegram AI agent recipe has an importable workflow; this page is the reference for the nodes themselves.

Counts on this page treat the two Telegram nodes as one family: 1,659 templates use the Telegram node, 825 use the Telegram Trigger and 793 use both, so 1,691 use at least one.

How often public templates use it

1,691 of the 13,574 public templates on n8n.io (12.5%) contain this node, in the snapshot we took on 2026-10-20. The table splits that by the year each template was published. 2026 runs to October 20.

Year published	Templates with the node	Share of that year
2024	36 of 462	7.8%
2025	940 of 6,564	14.3%
2026	675 of 5,845	11.5%

The median template using this node has 398 views on n8n.io, against 284 for all templates. Template counts show what people publish, not what runs in production.

What it is used with

The most frequent partners are the nodes that appear most often in the same templates. "Lift" compares that with the whole library: 2× means the partner turns up twice as often next to this node as in an average template.

Most frequent partner	Share of its templates	Lift
Code	60.7%	1.02×
Edit Fields (Set)	59.1%	1.06×
If	58.2%	1.15×
HTTP Request	50.7%	0.98×
AI Agent	43.8%	1.40×
Schedule Trigger	36.4%	1.14×

Strong pairings (in at least 5% of its templates, lift 1.5× or more): 7. The top ones:

Strong partner	Share of its templates	Lift
Error Trigger	5.9%	2.20×
Google Gemini	6.0%	1.96×
Simple Memory	15.4%	1.92×
OpenRouter Chat Model	7.5%	1.89×
OpenAI	22.6%	1.81×
Switch	25.5%	1.67×
Gemini Chat Model	15.7%	1.66×

Most viewed public templates that use it: Automate multi platform social media content creation with ai (442,651 views); Angie personal ai assistant with telegram voice and text (429,283 views); Personal life manager with telegram google services and voice enabled ai (246,872 views).

Versions and changes

Node versions from the npm packages n8n-nodes-base and @n8n/n8n-nodes-langchain, version 2.44.4. New workflows get the default version; workflows built earlier keep the version they were built with until you replace the node.

Node	Versions	Default	Credential types	Scope
Telegram	1, 1.1, 1.2	1.2	Telegram bot token	4 resources, 27 operations
Telegram Trigger	1, 1.1, 1.2, 1.3, 1.4, 1.5	1.5	Telegram bot token	–

Source on GitHub: packages/nodes-base/nodes/Telegram: 167 commits since 2019-10-04, last on 2026-10-14.

Recent fixes and features

2026-07-14: feat(Telegram Node): Add advanced HITL configuration for one-tap in-chat approval (PR #34009)
2026-07-01: fix(Telegram Trigger Node): Apply chat/user ID filters to all update types (PR #32417)
2026-06-18: feat(Telegram Node): Add rich message and message draft operations (PR #32173)
2026-04-29: fix(Telegram Trigger Node): Drop pending updates when creating a new webhook (PR #29103)
2025-09-09: fix(Telegram Node): Use parameter index instead of 0 for binaryData (PR #19236)
2025-07-28: fix(Telegram Node): Determine the MIME type when downloading the file (PR #17725)

Merged dates from GitHub. A fix only helps once your n8n instance runs a release that includes it, so check your version.

Known problems

Bot not a participant. To post in a channel, the bot must be added as an administrator. Source: n8n docs
Finding the chat ID. Group chat IDs start with a minus sign; a helper bot or the trigger's output shows the ID. Source: n8n docs
30 messages a second. Telegram limits bulk sending. Loop in batches with a Wait between them. Source: n8n docs
Test and production fight over the bot. A bot can have only one webhook, so the test URL and production URL overwrite each other. Use a second bot for testing. Source: n8n docs
HTTPS required. Telegram only sends updates to an HTTPS address, so n8n must be reachable over HTTPS (set WEBHOOK_URL when self-hosting). Source: n8n docs
Chat/user filters. Chat and user ID filters applied to all update types only from July 2026. Source: n8n PR #32417
Bad Request: can't parse entities. If you never add the Parse Mode field, Send Message still sends Telegram legacy Markdown: we read the node source in n8n 2.44.7 (current stable on Oct 27, 2026) and it fills in Markdown whenever Parse Mode is empty. So one stray _ or * in AI output, or in a name like My_Workflow, breaks the message. Leaving attribution on can hide the bug, because its _..._ footer happens to close the open tag. Adding the field is a trap too: its preset is HTML, so a < in the text fails with “Unsupported start tag”. Fix: add Parse Mode, pick HTML and escape &, < and > in the text (our Telegram recipe does this). A community PR to send plain text by default has not been merged (checked Oct 27, 2026); a reviewer called it a breaking change and suggested a separate Plain Text mode instead. Telegram's own escaping rules: Bot API formatting options. Source: n8n PR #35786

Forum trouble signal: not measured. The n8n community forum's terms forbid automated access, so we don't count forum threads.

Our recipes that use it

1 of our 25 importable workflows uses this node:

Telegram AI agent with memory in n8nn8n JSON you can import

Official docs and sources

Usage, pairings, AI share and views: our count of 13,574 public n8n.io templates (snapshot 2026-10-20). Versions: npm packages, version 2.44.4. Changes: n8n's GitHub repository. Docs read and data pulled Oct 26, 2026. We describe each node in our own words; the docs are the authority on settings.

Related nodes

Questions

How many n8n templates use the Telegram node?: 1,691 of the 13,574 public templates on n8n.io (12.5%), in our snapshot of 2026-10-20.
What is the Telegram node most often used with?: Code, which appears in 60.7% of its templates. The most distinctive partner is Error Trigger (lift 2.2×).
Why does the n8n Telegram node say "can't parse entities"?: With Parse Mode left empty, the node sends your text as Telegram legacy Markdown, so an unclosed _ or * fails. Add Parse Mode, choose HTML and escape the ampersand and angle brackets in the text.
Why does my Telegram trigger only work in test or in production?: A Telegram bot has a single webhook, so whichever URL registered last wins. Use a separate test bot.
How do I stop n8n adding a line to Telegram messages?: Turn off the attribution option in the node.