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

The n8n Telegram integration turns one of the world's most popular messaging apps into a control center for your automations. With over 950 million active users, Telegram isn't just a chat app — its Bot API makes it one of the most automation-friendly platforms available. Pair that with n8n's visual workflow builder and 400+ integrations, and you can build everything from simple notification bots to full AI-powered assistants.

Whether you're monitoring servers, routing customer inquiries, or building an internal tool your team interacts with through chat, this guide covers five real workflows you can build and deploy today.

Why Telegram + n8n Is a Powerful Combo

Telegram's Bot API is one of the most developer-friendly messaging APIs available. Unlike WhatsApp or SMS, there are no per-message fees, no approval processes for templates, and no rate limits that'll block you during normal use. Creating a bot takes 30 seconds via @BotFather.

n8n's Telegram node supports both triggers (receiving messages, commands, and callback queries) and actions (sending messages, photos, documents, stickers, and editing existing messages). This two-way capability means your workflows can both listen and respond — making interactive bots possible without any custom code.

Key capabilities of the n8n Telegram node:

• Telegram Trigger node — fires on new messages, commands, callback queries, channel posts, or edited messages
• Send Message — supports Markdown and HTML formatting, inline keyboards, and reply markup
• Send Photo / Document / Video — attach files from other nodes or URLs
• Edit Message — update previously sent messages (great for status updates)
• Answer Callback Query — respond to inline button presses
• Get Chat Member — check user roles and permissions

Setting Up the Telegram Node in n8n

Before building any workflow, you need a Telegram bot token and your n8n instance configured to receive webhooks.

Step 1: Create Your Bot

1. Open Telegram and search for @BotFather
2. Send /newbot and follow the prompts to name your bot
3. Copy the API token — it looks like 123456789:ABCdefGHIjklMNOpqrsTUVwxyz

Step 2: Add Credentials in n8n

1. In your n8n instance, go to Settings → Credentials → Add Credential
2. Search for Telegram and select the Telegram API credential type
3. Paste your bot token and save

Step 3: Set Up the Trigger

Drag a Telegram Trigger node onto your canvas and select which updates to listen for — typically message for general messages or callback_query for inline button responses. Once activated, n8n automatically registers a webhook with Telegram's servers.

Workflow 1: Real-Time Server and App Alerts

The simplest and most common Telegram automation: send yourself (or your team) instant alerts when something happens.

How It Works

1. Trigger: Webhook node receives a POST request from your monitoring tool (Uptime Kuma, Grafana, Healthchecks.io, or a custom endpoint)
2. IF node: Check the severity level — only send Telegram messages for critical or warning
3. Telegram node (Send Message): Format and send a message to your ops channel

Example Message Format

🔴 *Server Alert: Critical*

Service: `{{ $json.service_name }}`
Status: {{ $json.status }}
Downtime: {{ $json.duration }}s
Timestamp: {{ $now.format('yyyy-MM-dd HH:mm:ss') }}

[View Dashboard]({{ $json.dashboard_url }})

Set the Parse Mode to Markdown in the Telegram node to render the formatting. You can also chain this with the Edit Message action to update the alert message when the service recovers, keeping your channel clean.

Workflow 2: AI-Powered Telegram Chatbot

This is where n8n's Telegram integration gets exciting. By combining the Telegram Trigger with n8n's AI nodes, you can build a conversational chatbot that answers questions, looks up data, or performs actions — all through Telegram chat.

Workflow Structure

1. Telegram Trigger — listens for incoming messages
2. AI Agent node — processes the message using an LLM (OpenAI, Anthropic, or any supported provider)
3. Window Buffer Memory node — maintains conversation context per chat ID using {{ $('Telegram Trigger').item.json.message.chat.id }} as the session key
4. Telegram node (Send Message) — returns the AI response to the user

Making It Useful

A basic chatbot that just forwards to an LLM isn't very interesting. The real power comes from giving the AI Agent tools:

• Connect a Google Sheets tool so users can ask "What's the status of order #1234?"
• Add an HTTP Request tool to query your internal APIs
• Wire up a Postgres or MySQL tool to let the bot look up customer records
• Attach a Vector Store tool for RAG-powered Q&A against your documentation

The AI Agent node handles the routing — users just type natural language questions in Telegram, and the agent decides which tool to call.

Workflow 3: Interactive Approval Workflows

Telegram's inline keyboards let you build approval flows where someone taps "Approve" or "Reject" right in the chat — no login to a dashboard required.

Workflow Structure

1. Webhook node — receives an approval request (e.g., a new expense report, deployment request, or content submission)
2. Telegram node (Send Message) — sends the request details with inline keyboard buttons:

   Reply Markup → Inline Keyboard:
   [
     [{"text": "✅ Approve", "callback_data": "approve_{{id}}"}],
     [{"text": "❌ Reject", "callback_data": "reject_{{id}}"}]
   ]

3. Telegram Trigger (separate workflow) — listens for callback_query updates
4. Switch node — routes based on whether callback data starts with approve_ or reject_
5. HTTP Request node — calls your API to process the approval/rejection
6. Telegram node (Edit Message) — updates the original message to show the decision

This pattern works for expense approvals, PR merge requests, content review, access requests, or any process where a human needs to make a quick yes/no decision.

Workflow 4: Content Monitoring and Digest Bot

Build a bot that monitors sources and sends you curated digests — like a personal RSS reader with intelligence.

Workflow Structure

1. Schedule Trigger — runs every morning at 8 AM (or whatever cadence you prefer)
2. RSS Feed Read node — pulls new items from multiple feeds (industry blogs, competitor news, product updates)
3. HTTP Request node — optionally pull from APIs like Reddit, Hacker News, or Twitter/X
4. AI Agent or Summarize node — filters for relevance and generates a brief summary of each item
5. Telegram node (Send Message) — delivers a formatted daily digest to your channel

You can make this interactive by adding inline buttons like "Read More" (links to the article) or "Save" (sends it to Notion or Pocket via additional nodes).

Workflow 5: CRM Updates via Telegram Commands

Let your sales team update your CRM without leaving Telegram. This workflow listens for specific commands and pushes data to your CRM.

Supported Commands

• /deal Acme Corp 50000 negotiation — creates or updates a deal
• /note Acme Corp Had a great call, they want a demo next week — adds a note to a contact
• /lookup Acme Corp — returns deal info and recent activity

Workflow Structure

1. Telegram Trigger — listens for messages starting with /
2. Switch node — routes by command (/deal, /note, /lookup)
3. Function node — parses the command arguments into structured fields
4. HubSpot / Pipedrive / Salesforce node — creates the deal, adds the note, or retrieves the record
5. Telegram node (Send Message) — confirms the action back to the user

This is especially useful for field sales reps who need to log activity quickly between meetings. No app switching, no mobile CRM frustration — just type a command.

Tips for Running Telegram Bots in Production

Building the workflow is the easy part. Keeping it reliable is what matters. Here are practical considerations:

• Always set an error workflow. If your bot crashes mid-conversation, users get silence — which is worse than an error message. Use n8n's Error Trigger to send yourself a Telegram alert (meta, but effective) when any workflow fails.
• Use chat IDs, not usernames. Telegram usernames can change. Always store and reference the numeric chat.id for targeting messages.
• Rate limits exist. Telegram allows roughly 30 messages per second to different chats, but only 1 message per second to the same chat. If you're sending bulk notifications, add a Wait node with a 1-second delay between messages to the same group.
• Secure your bot. If your bot handles sensitive data, check the incoming chat.id against an allowlist before processing commands. You can store the allowlist in a Google Sheet or database and check it with an IF node at the start of your workflow.
• Keep your instance running 24/7. Telegram webhooks need a live endpoint. If your n8n instance goes down, you'll miss messages — Telegram retries for a while, but not forever. Running on n8nautomation.cloud gives you a dedicated instance with guaranteed uptime, automatic backups, and no server babysitting.

The Telegram and n8n combination works because both tools share the same philosophy: powerful, open, and no unnecessary gatekeeping. You get a messaging platform with zero per-message costs and a workflow engine with no artificial node limits. Whether you're building a quick alert bot or a full conversational AI assistant, the setup takes minutes — especially when your n8n instance is already running and publicly accessible on n8nautomation.cloud.