n8n + Telegram Integration: Build Powerful Bots Without Code

The n8n Telegram integration is one of the most versatile connections in the entire n8n ecosystem. Telegram's Bot API is generous — free, fast, and feature-rich — and n8n's native Telegram nodes give you full access to it without touching a line of Python or Node.js bot framework code. Whether you want server alerts on your phone, a customer support bot in a group chat, or a workflow that forwards leads from a Telegram channel to your CRM, this guide walks you through every step.

Why Telegram + n8n Is a Powerful Combination

Telegram bots have a problem: they need a server running 24/7 to listen for updates and respond. Traditional bot development means setting up a webhook endpoint, writing handler code, deploying to a server, and managing uptime. n8n eliminates all of that.

With n8n, your Telegram bot logic lives in a visual workflow. The Telegram Trigger node handles the webhook automatically. Your bot responses, data lookups, and integrations with other tools are just nodes you drag onto the canvas. Need your bot to check inventory in a Google Sheet before replying? Add a Google Sheets node. Need it to create a Jira ticket? Add a Jira node. No boilerplate, no deployment pipeline.

Here's what makes this pairing stand out:

• Instant webhook setup — n8n registers the webhook with Telegram automatically when you activate the workflow
• Rich message support — send text, photos, documents, videos, locations, and stickers
• Inline keyboards — build interactive menus with callback buttons
• Group chat support — your bot can operate in groups, not just 1-on-1
• No rate limit worries — Telegram's Bot API allows 30 messages per second, far more than most automation needs

Setting Up Your Telegram Bot for n8n

Before connecting n8n, you need a Telegram bot token. This takes about two minutes:

1. Open Telegram and search for @BotFather — this is Telegram's official bot for creating bots
2. Send /newbot and follow the prompts to choose a name and username
3. BotFather will reply with your HTTP API token — copy this, you'll need it in n8n
4. Optionally, send /setdescription and /setabouttext to configure your bot's profile

Now add the credentials in n8n:

1. Go to Settings → Credentials → Add Credential
2. Search for Telegram API
3. Paste your bot token into the Access Token field
4. Click Save — n8n will verify the token is valid

The Telegram Trigger Node: Listening for Messages

The Telegram Trigger node is your bot's ears. It listens for incoming events and kicks off your workflow whenever something happens. When you add it to a workflow, you can configure which updates to listen for:

• message — any text, photo, or document sent to the bot
• callback_query — when a user clicks an inline keyboard button
• edited_message — when a user edits a previously sent message
• channel_post — messages posted to a channel where the bot is an admin
• pre_checkout_query — for bots that handle Telegram Payments

A typical setup looks like this: add the Telegram Trigger node, select your credentials, check the update types you want, and connect it to your processing nodes. When you activate the workflow, n8n sends a setWebhook request to Telegram's API, pointing to your n8n instance's webhook URL.

The trigger output includes the full message object — sender info, chat details, message text, any attached media, and metadata. You can use an If node or Switch node right after the trigger to route messages based on content. For example, check if message.text starts with / to handle bot commands differently from regular messages.

Sending Messages, Photos, and Documents

The Telegram node (not the Trigger) handles outbound communication. It supports multiple operations:

Send Message — the most common operation. Set the Chat ID (you can reference it dynamically from the trigger output) and your Text. Enable Parse Mode as HTML or MarkdownV2 to format your messages with bold, italic, links, and code blocks.

Send Photo — pass a URL or binary data. Great for sending charts, screenshots, or generated images. You can include a caption below the photo.

Send Document — attach files like PDFs, CSVs, or exports from other nodes. The Move Binary Data node is useful here for converting data from other tools into a file attachment.

Send Chat Action — show typing indicators ("typing...", "uploading photo...") while your workflow processes data. This gives users visual feedback that the bot is working.

Other available operations include sending locations, editing messages that were already sent, pinning messages in group chats, and managing chat members.

5 Telegram Workflows You Can Build Today

These are real, practical workflows — not hypotheticals. Each one uses nodes that exist in n8n right now.

1. Server Monitoring Alerts

Trigger: Schedule Trigger (every 5 minutes) → HTTP Request node to ping your endpoints → If node to check for non-200 responses → Telegram node to send an alert with the failing URL and status code. Add a second branch that checks response time and alerts if it exceeds your threshold.

2. Daily Digest Bot

Trigger: Schedule Trigger (every morning at 8 AM) → Google Sheets or Notion node to pull today's tasks → Function node to format the list → Telegram node to send a clean, formatted summary to your personal chat or a team group.

3. Lead Capture from Telegram Groups

Trigger: Telegram Trigger (listening to group messages) → If node to filter messages containing keywords like "interested" or "pricing" → Google Sheets node to log the lead with their username, message, and timestamp → Telegram node to send a private reply with more information.

4. Interactive FAQ Bot with Inline Keyboards

Trigger: Telegram Trigger (message) → Switch node to check if it's /start or /help → Telegram node to send a message with an inline keyboard showing FAQ categories → when the user taps a button, a second Telegram Trigger (callback_query) workflow sends the relevant answer and offers a "Back to menu" button.

5. AI-Powered Chat Bot

Trigger: Telegram Trigger → OpenAI node (or any LLM node) to generate a response using the incoming message as the prompt → Telegram node to send the AI's reply back. Add a Send Chat Action ("typing...") before the AI node so users know the bot is thinking. You can store conversation history in a database node to maintain context across messages.

Advanced Patterns: Inline Keyboards and Callbacks

Inline keyboards transform your bot from a simple notification sender into an interactive application. Here's how they work in n8n:

When sending a message with the Telegram node, you can add Reply Markup of type Inline Keyboard. Each button has a label (what the user sees) and a callback data string (what your workflow receives when they tap it).

For example, a support bot could send:

Reply Markup → Inline Keyboard:
Row 1: ["Billing Question" → callback: "support_billing"] ["Technical Issue" → callback: "support_tech"]
Row 2: ["Talk to a Human" → callback: "support_human"]

When a user taps "Billing Question", your callback_query workflow receives support_billing as the callback data. Use a Switch node to route each callback value to the appropriate response.

You can chain multiple keyboards together to build multi-step forms, confirmation dialogs, or navigation menus. The Edit Message Text operation is particularly useful here — instead of sending new messages, you update the existing message in place, keeping the chat clean.

Another powerful pattern: use the Answer Callback Query operation to show a brief toast notification at the top of the user's screen, confirming their selection without sending a visible message.

Hosting Your Telegram Bot 24/7

A Telegram bot is only useful if it's always online. If your n8n instance goes down, Telegram will retry webhook deliveries for a while, but eventually gives up — and your users get silence.

This is the biggest challenge with self-hosting n8n for Telegram bots. You need to ensure:

• Your server has a valid SSL certificate (Telegram rejects plain HTTP webhooks)
• Your n8n instance is accessible from the public internet
• The process stays running through reboots, updates, and crashes
• You're monitoring uptime and restarting automatically on failure

A managed hosting solution removes these concerns entirely. On n8nautomation.cloud, your n8n instance runs on a dedicated server with SSL configured out of the box, automatic backups, and 24/7 uptime monitoring. Your Telegram bot's webhook URL uses your custom subdomain (yourname.n8nautomation.cloud), which Telegram's API accepts immediately — no certificate configuration, no reverse proxy setup, no Docker troubleshooting.

At $15/month, it costs less than most VPS setups once you factor in the time you'd spend maintaining SSL certs, updating n8n versions, and debugging downtime at 2 AM when your bot stops responding.

Telegram bots built with n8n hit a sweet spot: you get the full power of Telegram's Bot API with the flexibility to connect it to hundreds of other services, all through a visual interface. Start with a simple notification workflow, get comfortable with the nodes, and then build up to interactive bots with inline keyboards and AI-powered responses. The learning curve is gentle, and the ceiling is remarkably high.