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:

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.

Trigger: Webhook (from Stripe, HubSpot, PagerDuty, any source) ↓ Node: IF → filter by event type / severity threshold ↓ Node: Code → build formatted Telegram message (Markdown supported) ↓ Node: Telegram → sendMessage to alert channel ↓ [Optional] Node: IF → if critical → also ping personal user ID directly

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:

💳 *New Payment — £3,400* Customer: Acme Corp Ltd Plan: Growth Annual MRR Impact: +£283/mo [View in Stripe](https://dashboard.stripe.com/payments/xxx)

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.

Trigger: Telegram Trigger (webhook mode) → new message received ↓ Node: IF → check if message is from authorised user ID list ↓ Node: Code → build prompt with system context (your business info, tools, tone) ↓ Node: OpenAI → chat completion (gpt-4o or equivalent) ↓ Node: Telegram → sendMessage reply to same chat_id ↓ Node: Google Sheets → log query + response for auditing

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.

// Real usage stats from a deployed client bot

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.

Trigger: Shopify Webhook → order.created / order.fulfilled / order.cancelled ↓ Node: Code → extract order details, customer Telegram ID (stored in notes/metafields) ↓ Node: Switch → branch by event type (created / fulfilled / cancelled) ↓ Branch A (created): Telegram → "✅ Order confirmed — #1234, ships within 2 days" Branch B (fulfilled): Telegram → "📦 Shipped! Track here: [courier link]" Branch C (cancelled): Telegram → "❌ Order cancelled. Refund in 3-5 days." ↓ Node: Airtable → log notification sent + timestamp

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.

Trigger: Schedule → weekdays at 08:00 (Europe/London timezone) ↓ Node: Stripe → yesterday's new MRR, churn, payment failures ↓ Node: Linear → open P1/P2 issues + issues closed yesterday ↓ Node: Google Calendar → today's events (team calendar) ↓ Node: HTTP Request → your uptime monitor (StatusPage / BetterUptime) ↓ Node: Code → compile into clean Telegram message (Markdown) ↓ Node: Telegram → send to team group chat

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.

Trigger: Telegram Trigger → message starting with / ↓ Node: Code → parse command name + arguments /report weekly → fetch weekly revenue summary /status acme → check Acme Corp's open tickets in Linear /invoice £500 freelancer-x → create draft invoice in Xero /uptime → check all monitored services /leads today → fetch today's new CRM leads ↓ Node: Switch → route to appropriate sub-workflow by command ↓ Node: [Tool-specific node] → fetch/create/update data ↓ Node: Telegram → send formatted reply (only visible to the sender)

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.

Trigger: Telegram Trigger → /start command or deep link (from website CTA) ↓ Node: Telegram → "What does your business do?" [wait for reply] ↓ Node: Telegram Trigger → capture answer → store in workflow context ↓ Node: Telegram → "What's your monthly budget for automation?" [wait for reply] ↓ Node: Telegram Trigger → capture answer ↓ Node: Telegram → "How soon do you need this built?" [with inline keyboard: ASAP / 1-2 months / Just exploring] ↓ Node: Code → calculate lead score (budget, urgency, fit) ↓ Node: IF → score > 70 → HubSpot create contact + Slack alert to sales team ↓ Node: IF → score < 30 → add to nurture sequence ↓ Node: Telegram → send personalised response + book a call link

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.

Trigger: Any event requiring approval (invoice, content piece, access request) ↓ Node: Telegram → send message with inline keyboard: [✅ Approve] [❌ Reject] [🔁 Request Changes] ↓ Node: Telegram Trigger → listen for callback_query (button press) ↓ Node: Code → identify which button pressed + who pressed it (user.id) ↓ Node: IF → Approve → execute action (pay invoice / publish content / grant access) ↓ Node: IF → Reject → notify requester with reason via Telegram DM ↓ Node: Telegram → edit original message to show final decision + actor + timestamp

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.

// Where Telegram beats Slack for automation

Error Handling and Reliability

Production Telegram bots need proper error handling. A few patterns that matter:

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.

Choosing the Right Workflow to Start With

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 (a failed payment, a high-value lead, a service outage) 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 — or if you want advice on which makes sense for your specific stack — get in touch and we'll scope it out.

📚 Further Reading