Automate Telegram with n8n: 7 Bot Workflows That Deliver Results (2026)
Telegram has 900 million users and one of the most capable bot APIs on the internet. n8n turns it into a fully programmable automation surface — alerts, AI assistants, order updates, and slash commands — without writing a single line of custom bot code.
Telegram's bot platform is deceptively powerful. Most people think of bots as novelty — meme generators, weather checkers, simple Q&A. But with n8n's Telegram node, you can build production-grade business automation that runs entirely through Telegram messages. No app to install. No dashboard to log into. Just Telegram, which your team is already using.
This guide covers seven workflows we've deployed for real clients — e-commerce founders, agency operators, SaaS teams, and solo consultants who use Telegram as their primary async channel. Each workflow has a clear business problem it solves and measurable output.
Setting Up the Telegram Integration in n8n
Before building anything, you need a bot token. The process is intentionally simple:
- Open Telegram and search for
@BotFather - Send
/newbot, follow the prompts to name your bot - BotFather returns a token like
7123456789:AAHdqTcvCH... - In n8n, go to Credentials → Add → Telegram API → paste your token
- Get your chat ID by sending a message to
@userinfobot
For group bots (sending to a channel or group), add the bot as an admin and use the group's chat ID (negative number, e.g. -1001234567890). For personal notifications, your own user ID works directly.
n8n's Telegram node supports both polling (n8n checks Telegram periodically) and webhooks (Telegram pushes updates to n8n instantly). Use webhooks in production — lower latency, lower resource usage.
Workflow 1: Business Event Alerts to a Private Channel
This is the fastest win. Any significant business event — new Stripe payment, failed subscription, form submission, server alert — fires a formatted Telegram message to a private channel or group. No email chains, no dashboard checks. It just arrives.
Telegram supports a useful subset of Markdown in messages — bold, italic, inline code, hyperlinks. A well-formatted alert beats a raw JSON notification every time. Example message format:
The hyperlink in Telegram message format means your team can tap directly through to the relevant record. No copy-pasting IDs.
Workflow 2: AI Assistant Bot (Powered by OpenAI)
This is the workflow that gets the most visible reaction from clients. You create a Telegram bot that any team member can message in natural language — and n8n routes the query to OpenAI, optionally with context from your business data, and replies in seconds.
The authorisation check is important. Without it, anyone who finds your bot's username can query it. Maintain a list of allowed Telegram user IDs in n8n's workflow settings or a Google Sheet, and reject messages from unknown users with a polite refusal.
Use cases we've built: internal FAQ bots (team members ask questions about internal processes, the bot queries a knowledge base via RAG and replies), client support pre-triage (routes to human if confidence is low), and personal productivity assistants that can query your calendar, send emails, or look up CRM records via tool calls.
Workflow 3: E-Commerce Order Update Bot
If you're running a Shopify or WooCommerce store, your customers already expect order updates. Telegram is now a genuine alternative delivery channel — and customers who opt in get faster, richer updates than SMS or email.
The friction point is capturing the customer's Telegram user ID at checkout. The cleanest approach: add an optional "Telegram username" field to checkout, then use Telegram's getChat API to resolve it to a user ID. Alternatively, send a unique opt-in link that routes through a registration bot to capture their ID before their first order.
Open rates on Telegram messages from bots are dramatically higher than email — typically 80-90%+ for customers who opted in vs 20-30% for email order confirmations. It's the channel people actually read.
Workflow 4: Scheduled Daily Digest for Your Team
Every morning, before anyone opens a tool, your team receives a clean briefing: revenue from yesterday, open issues, today's calendar, and anything that needs attention. It arrives in a shared Telegram group.
The message uses Telegram's Markdown to create visual hierarchy — bold for numbers, italics for context, headers for sections. A well-designed daily digest takes 30 seconds to read and replaces a 15-minute "what's happening today" conversation.
Key design principle: include only the things that would change what someone does that day. Revenue snapshot, critical issues, today's commitments. Not a full data dump — a decision-ready brief.
Workflow 5: Slash Command Interface for Your Entire Stack
This is the workflow that makes Telegram feel like a superpower. Any tool you use — CRM, project management, analytics, billing — becomes accessible via a simple Telegram command.
The trick is using Telegram's replyToMessageId to thread responses to the original command — so the conversation stays readable in a group context. If you're the only user, a private bot chat keeps everything clean without threading.
Clients who deploy this stop switching tabs. The whole toolstack lives in Telegram. /report, /status, /invoice — all from the same chat window.
Workflow 6: Lead Qualification Bot
Instead of a generic contact form that sends an email, build a Telegram bot that qualifies leads interactively. It asks the right questions, scores the responses, and routes hot leads immediately while filing cold ones for later follow-up.
Telegram's inline keyboard buttons make the bot feel conversational rather than form-like. Multiple choice answers — "ASAP / Next month / Just exploring" — are one tap. Completion rates on Telegram qualification flows are consistently higher than equivalent web forms.
Workflow 7: Internal Approval and Decision Flows
Small teams often have informal approval processes that create bottlenecks — "can you approve this invoice?", "is this design OK to send?" — that live in email or DMs and get lost. n8n's Telegram integration lets you build proper approval flows with inline keyboard buttons.
The final step — editing the original message to show the outcome — keeps the approval channel clean. Instead of an ever-growing thread, each approval message updates in place to show its resolved state.
Error Handling and Reliability
Production Telegram bots need proper error handling. A few patterns that matter:
- Rate limits: Telegram allows 30 messages/second globally, and 1 message/second to the same chat. For bulk sends, add a Wait node with 1.1s delay between messages
- Bot blocking: Users can block your bot. Telegram returns a 403 error — catch this in an IF node and flag the user as unsubscribed rather than retrying
- Webhook vs polling: If your n8n instance restarts, polling resumes naturally. Webhooks need re-registration after a server restart — add this to your n8n startup routine
- Message length: Telegram caps messages at 4096 characters. For long outputs, split into multiple messages or use a document/file send instead
- Idempotency: Telegram may deliver webhook updates more than once. Store the
update_idand deduplicate in n8n before processing
The most robust pattern: a dedicated Telegram group for bot errors. When any Telegram workflow in n8n encounters an unhandled exception, it sends a message to this error group with the workflow name, error message, and input data. You'll know within seconds when something breaks.
Where to Start
If your team is new to Telegram automation, start with Workflow 1 — business event alerts. Pick the single most important event your team currently discovers too late and build that one alert first. Get it reliable and well-formatted before adding more.
If you're building customer-facing automation, Workflow 3 (order updates) or Workflow 6 (lead qualification) deliver the clearest ROI. They run without human involvement and measurably outperform their email equivalents.
If your team already uses Telegram internally, Workflow 5 (slash commands) is the one that creates the most visible productivity change. The moment someone types /report weekly and gets a full revenue summary in 2 seconds, they stop opening Stripe manually.
All seven of these are workflows we build and maintain for clients. If you'd rather have them set up properly the first time — get in touch and we'll scope it out.