Automate Telegram with n8n: 7 Bot Workflows You Can Build Today

Automating Telegram with n8n opens up a world of possibilities for teams that rely on the messaging platform for communication, alerts, and customer support. With over 900 million monthly active users, Telegram has become a go-to channel for businesses, communities, and developer teams — and n8n's native Telegram node makes it straightforward to build bots that actually do useful work.

Unlike basic bot frameworks that require you to write and host code, n8n lets you visually wire up Telegram triggers and actions alongside hundreds of other services. You get the flexibility of a custom bot with the simplicity of drag-and-drop workflow building.

Why Telegram + n8n Is a Powerful Combination

Telegram's Bot API is one of the most developer-friendly messaging APIs available. It supports rich messages with buttons, inline keyboards, media attachments, and group management — all accessible through n8n without writing a single line of code.

Here's what makes this pairing stand out:

• Trigger-based automation — n8n's Telegram Trigger node listens for incoming messages, commands, callback queries, and channel posts in real time
• Two-way communication — send messages, photos, documents, stickers, and even locations back to users or groups
• 400+ integrations — connect Telegram to your CRM, databases, project management tools, monitoring systems, and AI services
• Conditional logic — use IF nodes, Switch nodes, and expressions to route messages based on content, sender, or chat type
• No server management — when you run n8n on n8nautomation.cloud, your Telegram bots run 24/7 with automatic backups and zero infrastructure headaches

Setting Up the Telegram Node 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. Copy the API token BotFather gives you
4. In n8n, go to Credentials → Add Credential → Telegram API
5. Paste your bot token and save

n8n provides two Telegram-related nodes:

• Telegram Trigger — starts a workflow when your bot receives a message, command, callback query, or other update
• Telegram — sends messages, edits messages, sends media, manages chats, and performs other bot actions

Workflows 1-2: Smart Notification Bots

1. Server Monitoring Alerts

This is the most common Telegram automation and one of the most valuable. Set up a workflow that monitors your infrastructure and sends alerts to a Telegram group when something goes wrong.

Workflow structure:

• Trigger: Schedule Trigger node (every 5 minutes) or a Webhook node receiving alerts from your monitoring tool
• Check: HTTP Request node pinging your service endpoints
• Condition: IF node checking response status codes or response times
• Alert: Telegram node sending a formatted message to your ops channel

Use Telegram's Markdown or HTML parse mode to format alerts with bold service names, status indicators, and direct links to your dashboard. A message template might look like:

🔴 *Service Down*
Endpoint: {{ $json.url }}
Status: {{ $json.statusCode }}
Time: {{ $now.format('HH:mm:ss') }}

[Open Dashboard](https://your-dashboard.com)

2. Daily Business Digest

Pull data from multiple sources and compile a morning summary sent to your Telegram chat every day at 8 AM.

Workflow structure:

• Trigger: Schedule Trigger node (cron: 0 8 * * *)
• Fetch data: Multiple branches — one hitting your Stripe API for revenue, another querying Google Analytics for traffic, another pulling open tickets from your helpdesk
• Merge: Merge node combining the data streams
• Format: Code node or template expressions to build a readable summary
• Send: Telegram node delivering the digest

Workflows 3-4: Auto-Responders and Command Bots

3. FAQ Command Bot

Build a bot that responds to slash commands with pre-defined answers — perfect for community groups or internal teams.

Workflow structure:

• Trigger: Telegram Trigger node (listening for messages)
• Route: Switch node checking {{ $json.message.text }} against patterns like /help, /pricing, /hours, /status
• Respond: Separate Telegram nodes for each command, each sending the appropriate response with inline keyboards for follow-up actions

For the inline keyboard, use the Telegram node's "Reply Markup" option with an Inline Keyboard. Each button can carry a callback data payload that triggers another workflow or a different branch in the same workflow.

4. AI-Powered Auto-Responder

Take it a step further by connecting your Telegram bot to an AI model. When a user sends a question, the workflow passes it through an OpenAI or Anthropic node and returns the AI-generated answer.

Workflow structure:

• Trigger: Telegram Trigger node
• Context: Optionally fetch relevant data from a Notion database, Google Sheet, or vector store using the message as a search query
• AI: OpenAI node (or AI Agent node for more complex chains) with a system prompt tailored to your use case
• Reply: Telegram node sending the AI response back to the user

n8n's AI Agent node supports memory, so you can maintain conversation context across multiple messages by storing chat history in a Postgres or Redis node keyed to the Telegram chat ID.

Workflows 5-6: Data Sync and CRM Workflows

5. Lead Capture to CRM

When someone messages your Telegram bot for the first time, automatically create a contact in your CRM and notify your sales team.

Workflow structure:

• Trigger: Telegram Trigger node
• Check: IF node — is this a new user? Check against a Google Sheet or database lookup using the Telegram user ID
• Create: HubSpot, Salesforce, or Pipedrive node creating a new contact with the Telegram username and first message as notes
• Notify: Telegram node sending a message to your sales channel: "New lead from Telegram: @username"
• Reply: Telegram node sending a welcome message to the user

6. Form Submission Notifications

Connect a Typeform, Google Forms, or Webhook trigger to Telegram so your team instantly sees new submissions.

Workflow structure:

• Trigger: Webhook node or Typeform Trigger node
• Format: Set node extracting and formatting the relevant fields
• Send: Telegram node posting a structured summary to your team channel
• Optional: Add an inline keyboard with "Approve" / "Reject" buttons that trigger a callback query workflow to update the submission status in your database

Workflow 7: Group Management Automation

If you manage a Telegram community, automating moderation tasks saves significant time. Here's a workflow for automated welcome messages and basic moderation.

Workflow structure:

• Trigger: Telegram Trigger node listening for new_chat_members updates
• Welcome: Telegram node sending a personalized welcome message that tags the new member and includes group rules
• Log: Google Sheets or Airtable node logging the new member's username, join date, and referral source (if using invite links)
• Moderation branch: A separate Telegram Trigger listening for all messages, routing through a Switch node that checks for spam patterns (URLs from new members, repeated messages, banned keywords)
• Action: Telegram node using the Delete Message or Ban Chat Member operation when spam is detected

For communities with heavy traffic, you can add a Code node that implements rate limiting — tracking message frequency per user in a Set node or external database and flagging accounts that exceed a threshold.

Tips for Running Telegram Bots in Production

Building the workflow is half the job. Keeping it reliable is the other half. Here are practical considerations for production Telegram bots:

Use webhook mode, not polling. n8n's Telegram Trigger uses webhooks by default, which means Telegram pushes updates to your n8n instance immediately. This requires your n8n instance to be publicly accessible with a valid SSL certificate — something you get automatically with n8nautomation.cloud but need to configure manually on self-hosted setups.

Handle errors gracefully. Add an Error Trigger workflow that catches failures in your Telegram workflows and sends you a notification (ironically, via Telegram) when something breaks. Use n8n's built-in retry-on-fail setting for nodes that call external APIs.

Respect Telegram's rate limits. The Bot API limits sending to about 30 messages per second across all chats, and 1 message per second to the same chat. If your workflow sends bulk messages, add a Wait node with a 1-second delay between sends or use the SplitInBatches node to throttle throughput.

Store state externally. Telegram bots often need to remember things — user preferences, conversation state, pending approvals. Use a Postgres, MySQL, or Redis node to persist state rather than relying on static data or workflow variables that reset between executions.

Test with a private group first. Before deploying any bot to a production channel, create a private test group. Add your bot and verify every workflow path — including error cases and edge conditions like empty messages, forwarded messages, and media-only messages that contain no text.

Running your Telegram bot on a managed n8n instance at n8nautomation.cloud means your webhooks have a stable HTTPS endpoint, your workflows execute around the clock, and you don't need to worry about server restarts killing your bot's connection. Starting at $15/month, it's the simplest way to keep your Telegram automations running without babysitting infrastructure.

The combination of Telegram's rich bot API and n8n's visual workflow builder makes it possible to create sophisticated automations that would otherwise require a custom application. Whether you're building an internal alerting system, a customer-facing support bot, or a community management tool, these seven workflow patterns give you a solid foundation to build on.