Skip to content

[platforms] Add Telegram Bot API — 27 workflow templates blocked, 2.9M views #17

@lucasygu

Description

@lucasygu

Summary

Telegram is the #1 most impactful missing platform integration on One CLI. It blocks 27 out of 51 blocked workflow templates (53%) in the top 150 by popularity, representing 2.9M combined views. 19 of these are sole-blocked by Telegram — connecting it would immediately unblock them.

Evidence

We replicated the top 150 n8n workflow templates as One CLI flows. 99 were replicable with current integrations. Of the 51 blocked:

  • Telegram blocks 27 (53% of all blocked)
  • 19 are sole-blocked — Telegram is the only missing platform
  • 2.9M combined views across blocked workflows
  • Next closest: WhatsApp (8 blocked), Facebook (9 blocked)

Sole-blocked workflows (connecting Telegram unblocks these immediately)

Rank Views Workflow
#8 310,663 Angie, personal AI assistant with Telegram
#17 223,496 Telegram AI chatbot
#28 161,568 Personal life manager with Telegram
#35 128,373 Clone viral TikToks with AI avatars & auto-post
#57 91,149 Conversational Telegram bot with GPT-5/GPT-4o
#63 85,228 AI powered RAG chatbot for your docs + Google Drive
#69 82,048 Proxmox AI agent with n8n and generative AI
#78 73,072 Auto-create TikTok videos with VEED.io AI avatars
#79 73,012 Telegram AI bot with LangChain nodes
#100 59,056 AI agent chatbot + LONG TERM memory
+ 9 more

Why Telegram matters for workflow automation

Telegram Bot API is the most popular messaging platform for AI agent interfaces in the n8n ecosystem. Common patterns:

  • AI chatbot interfaces (question → AI → response via Telegram)
  • Notification delivery (workflow results → Telegram message)
  • Content publishing (generated content → Telegram channel)
  • Personal assistant (voice/text → AI processing → Telegram reply)

Technical scope

Telegram Bot API is RESTful with straightforward endpoints:

  • sendMessage — send text to a chat
  • sendPhoto/sendDocument — send media
  • getUpdates — poll for incoming messages
  • setWebhook — receive messages via webhook

The API uses a simple bot token for authentication (no OAuth). Well-documented at https://core.telegram.org/bots/api

Impact on template marketplace

Adding Telegram would increase our n8n replication coverage from 66% (99/150) to 79% (118/150) — a 13 percentage point jump from a single integration.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions