n8n + Telegram Integration: 5 Powerful Bot Workflows You Can Build Today

The n8n Telegram integration is one of the most popular combinations in the automation community — and for good reason. Telegram's Bot API is generous, fast, and free, while n8n gives you the visual workflow builder to wire it into hundreds of other services without writing a backend from scratch. Whether you want a simple alert bot or a conversational AI assistant, this pairing gets you there quickly.

Telegram boasts over 900 million monthly active users and its bot ecosystem is one of the most developer-friendly in messaging. Unlike WhatsApp or SMS, there are no per-message fees, no approval processes for templates, and no rate limits that will trip you up at moderate scale. Combined with n8n's 400+ integrations, you get a powerful command center right inside your chat app.

Why Telegram and n8n Work So Well Together

n8n provides two dedicated Telegram nodes: the Telegram node (for sending messages, photos, documents, and performing actions) and the Telegram Trigger node (for receiving incoming messages and callback queries in real time). Together they cover both directions of communication.

Here's what makes this pairing stand out:

• Real-time triggers — The Telegram Trigger node uses webhooks, so your workflows fire instantly when a message arrives. No polling delays.
• Rich message formats — Send text with Markdown or HTML formatting, photos, documents, locations, stickers, and inline keyboards with callback buttons.
• Group and channel support — Bots can post to groups, supergroups, and channels, making them ideal for team notifications.
• No cost per message — Unlike SMS gateways or WhatsApp Business API, Telegram Bot API is completely free.
• Callback queries — Inline keyboard buttons let users interact with your workflows directly from the chat, enabling approval flows and interactive menus.

Setting Up Your Telegram Bot Credentials in n8n

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

1. Open Telegram and search for @BotFather.
2. Send /newbot and follow the prompts to name your bot.
3. BotFather will reply with an API token that looks like 123456789:ABCdefGhIJKlmNoPQRsTUVwxYZ.
4. In n8n, go to Credentials → New → Telegram API and paste the token.
5. Send a test message to your bot in Telegram, then use the Telegram Trigger node to verify the connection.

Workflow 1: Server Monitoring Alerts

Get instant Telegram alerts when something goes wrong with your infrastructure.

Nodes used: Schedule Trigger → HTTP Request → IF → Telegram

1. Schedule Trigger — Set to run every 5 minutes.
2. HTTP Request node — Point it at your health check endpoint (e.g., https://yourapp.com/api/health). Set Options → Never Error so the workflow continues even on failure.
3. IF node — Check if {{ $json.statusCode }} is not equal to 200, or if the response time exceeds your threshold.
4. Telegram node — On the true branch, send a message to your ops channel: 🚨 Health check failed for yourapp.com — Status: {{ $json.statusCode }}. Set Parse Mode to Markdown for clean formatting.

This simple four-node workflow replaces paid uptime monitoring tools for basic checks. Add a second IF branch to send a recovery message when the service comes back up.

Workflow 2: Instant Form Submission Notifications

Get notified in Telegram the moment someone submits a form — whether it's a contact form, lead capture, or support request.

Nodes used: Webhook → Set → Telegram

1. Webhook node — Creates a unique URL you can point your form's action to. Use POST method and JSON body.
2. Set node — Format the message cleanly. Map fields like name, email, and message into a single text string: New lead: {{ $json.name }} ({{ $json.email }}) — {{ $json.message }}.
3. Telegram node — Send the formatted message to your sales or support channel. Enable Reply Markup → Inline Keyboard to add a "Reply to Lead" button that opens a mailto link.

This workflow works with any form backend that can POST JSON — Webflow, WordPress (via webhook plugin), static sites with Formspree, or your own custom forms. Response time from submission to Telegram notification is typically under two seconds.

Workflow 3: Automated RSS News Digest

Stay on top of industry news without manually checking feeds. This workflow collects articles and delivers a daily digest to your Telegram chat.

Nodes used: Schedule Trigger → RSS Feed Read (×3) → Merge → Limit → Telegram

1. Schedule Trigger — Fire once daily at 8:00 AM.
2. RSS Feed Read nodes — Add one for each feed you want to monitor (e.g., Hacker News, TechCrunch, your industry blog). Each node outputs the latest items.
3. Merge node — Combine all feeds into one list using Append mode.
4. Limit node — Cap at 10 items so the digest stays readable.
5. Telegram node — Use an Expression in the message text to loop through items: format each as a linked headline. Set Parse Mode to HTML so <a href> tags render as clickable links.

Workflow 4: AI-Powered Telegram Chatbot

This is where things get exciting. With n8n's AI Agent node, you can build a Telegram chatbot that answers questions, looks up data, and takes actions — all through natural conversation.

Nodes used: Telegram Trigger → AI Agent → Telegram

1. Telegram Trigger node — Set to trigger on message events. This captures every incoming text message.
2. AI Agent node — Connect an OpenAI or Anthropic chat model. Define your system prompt to set the bot's personality and scope. Add tools: an HTTP Request tool for API lookups, a Postgres or MySQL tool for database queries, or custom function tools for business logic.
3. Telegram node — Send the AI Agent's response back to the user, using {{ $json.chatId }} from the trigger to reply to the correct chat.

For a customer support bot, connect the AI Agent to your knowledge base via the Vector Store Tool node — it will retrieve relevant documentation chunks and ground its answers in your actual content. Add a Window Buffer Memory sub-node to give the agent conversation context across multiple messages.

With n8n's new human-in-the-loop capabilities, you can also require manual approval before the AI executes high-impact tools like updating database records or processing refunds. The Chat node's approval buttons make this seamless — a team member simply clicks "Approve" or "Reject" right in Telegram.

Workflow 5: Daily Team Standup Collector

Replace standup meetings with an async Telegram workflow that collects updates and posts a summary.

Nodes used: Schedule Trigger → Telegram (send prompt) → Telegram Trigger (collect replies) → Wait → Code → Telegram (post summary)

1. Schedule Trigger — Fires at 9:00 AM on weekdays.
2. Telegram node — Sends a prompt to your team group: "Good morning! Reply with your standup update: What did you do yesterday? What's planned for today? Any blockers?"
3. Telegram Trigger — A separate workflow that collects replies from team members and appends them to a Google Sheet or n8n's static data.
4. Wait node — Pauses for 2 hours to give everyone time to respond.
5. Code node — Aggregates all replies into a formatted summary.
6. Telegram node — Posts the compiled standup summary back to the group or a dedicated channel.

This gives distributed teams a persistent, searchable record of standups without the time cost of synchronous meetings. If you pipe the results into a Google Sheet, you get a timeline of team activity you can review in seconds.

Tips for Running Telegram Bots in Production

Building the workflow is the fun part. Keeping it reliable is what matters. Here are practical tips for Telegram bots that need to run 24/7:

• Use webhook mode, not polling — n8n's Telegram Trigger uses webhooks by default, which is faster and more reliable. Make sure your n8n instance is accessible via HTTPS, as Telegram requires it for webhook delivery.
• Handle errors gracefully — Add an Error Trigger workflow that sends you a Telegram message when any workflow fails. Meta? Yes. Useful? Absolutely.
• Respect message limits — Telegram messages cap at 4,096 characters. For longer content, split into multiple messages using the Split In Batches node or send a document instead.
• Set bot commands — Use BotFather's /setcommands to register commands like /help, /status, and /report. Then use a Switch node in your workflow to route based on {{ $json.message.text }}.
• Secure your bot — If your bot handles sensitive data, check the chat.id against an allowlist in an IF node before processing any message. This prevents unauthorized users from interacting with your workflows.

The biggest operational concern with Telegram bots is uptime. If your n8n instance goes down, your bot goes silent — and unlike email, users expect instant responses in chat. This is where a managed hosting solution pays for itself. With n8nautomation.cloud, your instance runs on dedicated infrastructure with automatic backups, HTTPS configured by default, and 24/7 uptime monitoring — starting at just $12/month. No Docker configs, no SSL certificates, no 3 AM restarts.

Telegram bots built with n8n sit at a sweet spot: powerful enough to replace custom-coded bots, flexible enough to connect to your entire tool stack, and simple enough to build in an afternoon. Start with the notification workflow to get comfortable with the nodes, then work your way up to the AI chatbot. Each workflow you build compounds — the patterns you learn in one transfer directly to the next.