n8n + Telegram Integration: 5 Powerful Automations You Can Build Today

The n8n Telegram integration is consistently one of the most popular nodes in the entire n8n ecosystem — and for good reason. Telegram's Bot API is fast, free, and incredibly flexible, and when you pair it with n8n's visual workflow builder, you get a notification and chatbot engine that rivals custom-coded solutions. Whether you need instant alerts for your team, an AI assistant your customers can message, or automated group management, Telegram plus n8n handles it all.

Why Telegram + n8n Is a Killer Combo

Telegram stands apart from other messaging platforms for automation. The Bot API is completely free with generous rate limits (around 30 messages per second), bots can send rich media including photos, documents, and formatted text with Markdown or HTML, and there's no approval process — you create a bot and it's live immediately.

n8n gives you two core Telegram nodes:

• Telegram node — sends messages, photos, documents, stickers, chat actions, and more. Supports editing and deleting messages too.
• Telegram Trigger node — listens for incoming messages, callback queries (inline button clicks), and other updates via webhook.

Together, these let you build bidirectional workflows: your bot can both react to what users send and proactively push information out. Combine that with n8n's 400+ other integrations and you've got a messaging hub that connects to virtually any tool in your stack.

Setting Up Your Telegram Bot Credentials

Every automation below starts the same way — you need a Telegram bot token. Here's the quick version:

1. Open Telegram and search for @BotFather.
2. Send /newbot and follow the prompts to name your bot.
3. BotFather gives you an API token that looks like 123456789:ABCdefGHIjklMNOpqrsTUVwxyz.
4. In n8n, go to Credentials → New → Telegram API and paste that token.

You'll also need the Chat ID of the user or group you want to message. The easiest method: add your bot to a group, send a message, then use the n8n HTTP Request node to call https://api.telegram.org/bot<TOKEN>/getUpdates. The chat ID appears in the response. For personal messages, you can use the Telegram Trigger node — it includes the sender's chat ID in every incoming message payload.

Automation 1: Server Monitoring Alerts

This is the most common Telegram automation, and it takes about five minutes to set up. The goal: get an instant Telegram message when something goes wrong with your infrastructure.

Workflow structure:

1. Schedule Trigger node — runs every 5 minutes (or whatever interval you want).
2. HTTP Request node — hits your health check endpoint, e.g., https://yourapp.com/api/health. Set "On Error" to "Continue" so the workflow doesn't stop on a failure.
3. IF node — checks if the response status code is anything other than 200, or if the response time exceeded a threshold.
4. Telegram node — sends an alert message to your ops channel.

For the Telegram node, configure it with:

• Operation: Send Message
• Chat ID: your group chat ID
• Text: use an expression like 🚨 *Alert:* yourapp.com returned status {{ $json.statusCode }} at {{ $now.toISO() }}
• Parse Mode: Markdown

You can extend this with multiple HTTP Request nodes to monitor several services in parallel, then use a Merge node to collect results before sending a single consolidated alert.

Automation 2: AI-Powered Customer Chatbot

This is where things get interesting. With n8n's AI Agent node and the Telegram Trigger, you can build a customer support chatbot that actually understands context — not just keyword matching.

Workflow structure:

1. Telegram Trigger node — set to trigger on "message" updates. This fires every time someone messages your bot.
2. AI Agent node — configure with your preferred LLM (OpenAI, Anthropic, Google Gemini, or any provider n8n supports). Set a system prompt that defines your bot's personality and knowledge base.
3. Telegram node — sends the AI response back to the user. Use {{ $('Telegram Trigger').item.json.message.chat.id }} as the Chat ID so it replies to the right person.

The AI Agent node in n8n now supports improved token management and can chain multiple tool calls together. You can give it tools like a Vector Store lookup (to search your documentation) or an HTTP Request tool (to check order status from your API), turning your Telegram bot into a genuinely useful assistant.

For maintaining conversation context, use n8n's Window Buffer Memory sub-node connected to the AI Agent. This stores recent messages per chat ID so the bot remembers what was said earlier in the conversation.

Automation 3: Form Submission Notifications

Get instant Telegram notifications whenever someone fills out a form — whether it's a contact form, lead magnet signup, or support request. This workflow bridges your web forms directly to your team's Telegram group.

Workflow structure:

1. Webhook node — creates a URL your form can POST to. Set the HTTP method to POST and the response mode to "Last Node."
2. Set node — formats the incoming data into a clean message. Map fields like name, email, and message into a formatted string.
3. Telegram node — sends the formatted submission to your team chat.

A practical message template:

📬 *New Contact Form Submission*

*Name:* {{ $json.name }}
*Email:* {{ $json.email }}
*Message:* {{ $json.message }}
*Submitted:* {{ $now.format('yyyy-MM-dd HH:mm') }}

You can add an inline keyboard to the Telegram message with buttons like "Reply" or "Mark as Handled" using the Telegram node's Reply Markup option. When someone clicks a button, the Telegram Trigger (set to listen for "callback_query") fires a separate workflow to update your CRM or send a reply email.

This pattern works for any event source — swap the Webhook node for a Typeform Trigger, Google Forms integration, or any SaaS that sends webhooks. The Telegram output stays the same. If you're running your n8n instance on n8nautomation.cloud, webhooks work out of the box with your dedicated subdomain — no need to configure tunnels or reverse proxies.

Automation 4: Scheduled Daily Reports

Instead of logging into five different dashboards every morning, have n8n compile the data and send a summary to Telegram at 8 AM.

Workflow structure:

1. Schedule Trigger node — set to fire daily at your preferred time using a cron expression like 0 8 * * *.
2. Multiple data source nodes (in parallel) — use HTTP Request nodes, database query nodes (Postgres, MySQL), or direct integrations (Google Analytics, Stripe, etc.) to pull metrics.
3. Merge node — combines all data streams into a single item.
4. Code node — formats everything into a readable Telegram message. Use JavaScript to calculate deltas, percentages, or highlights.
5. Telegram node — sends the report.

Example daily report message:

📊 *Daily Report — {{ $now.format('MMM dd, yyyy') }}*

*Revenue:* ${{ $json.revenue }} ({{ $json.revenueDelta }}%)
*New Users:* {{ $json.newUsers }}
*Support Tickets:* {{ $json.openTickets }} open
*Deploys:* {{ $json.deployCount }} successful

Telegram supports messages up to 4,096 characters. For longer reports, either split into multiple messages using the SplitInBatches node or send a document (PDF/CSV) using the Telegram node's "Send Document" operation.

Automation 5: Group Moderation and Welcome Messages

If you manage a Telegram community — whether it's a customer group, team channel, or open-source project — n8n can handle the repetitive moderation tasks.

Welcome message workflow:

1. Telegram Trigger node — set to trigger on "message" and filter for new chat members using an IF node that checks {{ $json.message.new_chat_members }} exists.
2. Telegram node — sends a welcome message to the group tagging the new member. Use {{ $json.message.new_chat_members[0].first_name }} to personalize it.

Spam filtering workflow:

1. Telegram Trigger node — fires on every message.
2. IF node — checks for common spam patterns: messages containing certain URLs, messages from users with no profile photo, or messages sent within seconds of joining.
3. Telegram node — uses the "Delete Message" operation to remove spam, then optionally uses "Ban Chat Member" to remove the offender.
4. Telegram node (second) — sends a log to your admin channel noting what was deleted and why.

For more sophisticated moderation, route suspicious messages through the AI Agent node to classify intent before taking action. This reduces false positives compared to simple keyword matching.

Tips for Running Telegram Bots in Production

Building the workflow is half the battle. Keeping it running reliably is the other half.

• Use webhook mode, not polling. The Telegram Trigger node uses webhooks by default in n8n, which is more efficient and faster than polling. Just make sure your n8n instance is publicly accessible — hosting on n8nautomation.cloud handles this automatically with your dedicated HTTPS subdomain.
• Handle errors gracefully. Add an Error Trigger workflow that sends Telegram alerts when any of your other workflows fail. Meta? Yes. Useful? Extremely.
• Respect rate limits. Telegram allows ~30 messages per second to different chats, but only 1 message per second to the same chat. If you're sending bulk notifications, use the SplitInBatches node with a 1-second wait between batches.
• Use reply markup for interactivity. Inline keyboards turn passive notifications into actionable messages. A deploy alert with "Rollback" and "Acknowledge" buttons is far more useful than plain text.
• Secure your webhooks. The Telegram Trigger node automatically validates that incoming requests are from Telegram, but if you're using a generic Webhook node, add a header check or secret token.

Telegram's combination of speed, rich formatting, free API access, and massive user base makes it one of the best notification and chatbot channels you can wire into n8n. Every workflow above can be built in under 30 minutes on a managed n8n instance at n8nautomation.cloud — no server setup, no webhook configuration headaches, just build and activate.