Automate Telegram Bots with n8n: 5 Powerful Workflows You Can Build

Automating Telegram bots with n8n opens up a massive range of possibilities — from sending instant notifications to building full AI-powered assistants that handle customer conversations. With over 950 million active users, Telegram is one of the most automation-friendly messaging platforms available, and n8n's dedicated Telegram node makes it straightforward to connect your bot to hundreds of other services without writing code.

Whether you're running an e-commerce store, managing a community, or monitoring infrastructure, these five workflows will show you exactly how to put Telegram bots to work.

Why Telegram + n8n Is a Perfect Match

Telegram's Bot API is one of the most developer-friendly messaging APIs out there. Bots can send text, images, documents, inline keyboards, and even process payments. But wiring all of that up with custom code takes time and maintenance.

That's where n8n comes in. The Telegram node and Telegram Trigger node handle the API complexity for you. The Trigger node listens for incoming messages, commands, or callback queries in real time. The regular Telegram node sends messages, photos, documents, and more back to users or channels.

Together, they let you build two-way conversational workflows that connect Telegram to your CRM, database, AI models, payment systems, and 400+ other integrations — all through n8n's visual workflow builder.

Key advantages of this pairing:

• No polling needed — the Telegram Trigger uses webhooks for instant response
• Rich message support — send formatted text, inline keyboards, images, and files
• Bidirectional — receive commands and send replies in the same workflow
• Scalable — handle multiple bots and channels from a single n8n instance

Setting Up the n8n Telegram Node

Before building any workflow, you need a Telegram bot token. Here's the quick setup:

1. Open Telegram and message @BotFather
2. Send /newbot and follow the prompts to name your bot
3. Copy the API token BotFather gives you (it looks like 123456789:ABCdefGHIjklMNOpqrsTUVwxyz)
4. In n8n, go to Credentials → New → Telegram API
5. Paste your bot token and save

For workflows that receive messages, add a Telegram Trigger node as your starting node. Set the Updates field to the event types you want to listen for — typically message for text, callback_query for inline button presses, or * to catch everything.

Workflow 1: Real-Time Order & Alert Notifications

The simplest and most popular use case: push notifications from your business tools directly to a Telegram chat or group.

How it works:

1. Trigger: Webhook node receives an event from your e-commerce platform (Shopify, WooCommerce, or any system that sends webhooks)
2. Format: A Set node structures the message — order number, customer name, total amount, items
3. Send: Telegram node sends a formatted message to your team's Telegram group

In the Telegram node, set Operation to Send Message, choose Parse Mode: MarkdownV2, and use an expression like:

🛒 *New Order \#{{ $json.order_number }}*
Customer: {{ $json.customer_name }}
Total: \${{ $json.total }}
Items: {{ $json.line_items.map(i => i.name).join(', ') }}

You can extend this with an IF node to route high-value orders (say, over $500) to a separate VIP channel, while regular orders go to the general notifications group.

Workflow 2: Support Ticket Bot with Auto-Routing

Turn your Telegram bot into a first-line support agent that creates tickets and routes them to the right team.

Workflow structure:

1. Telegram Trigger — listens for incoming messages
2. Switch node — checks the message for keywords or commands (/billing, /technical, /general)
3. HTTP Request node — creates a ticket in your helpdesk (Zendesk, Freshdesk, Linear, or any API)
4. Telegram node — replies with a confirmation and ticket number

For the Switch node, use conditions like {{ $json.message.text.toLowerCase().includes('billing') }} to route messages. You can also use Telegram's inline keyboards to present category buttons instead of relying on keyword matching:

// In the Telegram Send Message node, set Reply Markup:
{
  "inline_keyboard": [
    [
      { "text": "💳 Billing", "callback_data": "billing" },
      { "text": "🔧 Technical", "callback_data": "technical" }
    ],
    [
      { "text": "📋 General", "callback_data": "general" }
    ]
  ]
}

When a user taps a button, the Telegram Trigger fires a callback_query event with the callback_data value, which your Switch node can route cleanly.

Workflow 3: Automated Content Delivery Channel

Use n8n to automatically publish content to a Telegram channel — perfect for news aggregation, blog updates, or curated content delivery.

Workflow structure:

1. Schedule Trigger — runs every hour (or at whatever interval you choose)
2. RSS Feed Read node — pulls latest items from one or more RSS feeds
3. IF node — filters out items already posted (check against a Google Sheet, database, or n8n's static data)
4. Telegram node — posts new items to your channel with Operation: Send Message and Chat ID set to your channel's @username or numeric ID
5. Google Sheets node (or equivalent) — logs the posted item's URL to prevent duplicates on the next run

For channels with images, use the Send Photo operation instead, passing the article's featured image URL in the Photo field and the headline plus link in the Caption field.

You can layer in AI here too — add an OpenAI node or AI Agent to summarize each article before posting, so your channel delivers concise summaries rather than just headlines.

Workflow 4: AI-Powered Telegram Chatbot

This is where things get really interesting. Combine n8n's AI Agent node with Telegram to build a conversational assistant that can answer questions, look up data, and take actions.

Workflow structure:

1. Telegram Trigger — receives user messages
2. AI Agent node — processes the message with an LLM (OpenAI, Anthropic, Ollama, or any supported provider). Configure it with:
   • A system prompt defining your bot's personality and scope
   • Tools the agent can call — like an HTTP Request tool to look up order status, or a database tool to query product info
   • A Window Buffer Memory sub-node for conversation context, keyed by the Telegram chat ID ({{ $json.message.chat.id }})
3. Telegram node — sends the AI's response back to the user

The key to making this work well is the memory configuration. By setting the session key to the Telegram chat ID, each user gets their own conversation history, so the AI remembers prior messages in the thread.

If you want the bot to handle images too, add a branch that checks for photo messages and passes them to a vision-capable model for analysis.

Workflow 5: Server & Service Monitoring Alerts

Telegram is an excellent channel for infrastructure alerts — messages arrive instantly on mobile, and you can mute/unmute channels as needed.

Workflow structure:

1. Schedule Trigger — runs every 5 minutes
2. HTTP Request node — pings your endpoints or health check URLs
3. IF node — checks if the response status code isn't 200 or if response time exceeds a threshold
4. Telegram node — sends an alert to your DevOps group: ⚠️ Service {{ $json.service_name }} is DOWN — Status: {{ $json.status_code }} — Response time: {{ $json.response_time }}ms

To avoid alert fatigue, add a deduplication step: use n8n's static data ($getWorkflowStaticData('global')) to track which services are currently in an alert state. Only send a new Telegram message when a service transitions from healthy to unhealthy (or back), rather than on every failed check.

You can also build a daily digest — a separate workflow that runs once per day, compiles uptime stats from your monitoring data, and sends a summary to your Telegram channel with response time graphs as images.

Tips for Running Telegram Bots in Production

Building the workflow is the easy part. Keeping it reliable requires a few best practices:

• Always handle errors. Add an Error Trigger workflow that sends Telegram error notifications to an admin chat. If your bot workflow fails silently, users get no response — which is worse than an error message.
• Use webhook mode, not polling. The Telegram Trigger node uses webhooks by default in production mode, which is faster and more efficient than polling. Make sure your n8n instance is accessible via HTTPS.
• Rate limits matter. Telegram's Bot API limits you to about 30 messages per second to different chats, and 1 message per second to the same chat. If you're sending bulk notifications, add a Wait node with a short delay between batches.
• Keep bot tokens secret. Never commit tokens to version control. Store them exclusively in n8n's credential manager.
• Test with a staging bot. Create a separate bot via BotFather for development and testing, so you don't accidentally spam your production channels while building workflows.

The most common failure point for Telegram bots is the webhook URL becoming unreachable — this happens when your n8n instance goes down or changes URL. Running on a managed platform like n8nautomation.cloud eliminates this entirely — your instance stays online with a fixed subdomain, automatic backups, and 24/7 uptime starting at $15/month, so your bots keep running without server babysitting.

Telegram bots are one of the most versatile automation endpoints you can wire up with n8n. Start with a simple notification workflow, then build up to more complex conversational bots as you get comfortable with the Telegram Trigger and message formatting. The five workflows above cover the most common patterns, but the real power comes from combining them — an AI support bot that also logs tickets, sends alerts to your team, and updates your CRM, all from a single n8n canvas.