🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

Gmail to Telegram, smarter routing for every email

Gmail to Telegram, smarter routing for every email - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Gmail to Telegram, smarter routing for every email - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Your inbox isn’t “busy.” It’s chaotic. Important emails land next to newsletters, invoices get buried under support threads, and you keep rereading the same message just to decide what to do.

Gmail Telegram routing hits hardest when you’re the person who “owns” the inbox. That’s often a business owner or an ops lead. Support teams and sales reps feel it too, because delays turn into unhappy customers and missed deals.

This n8n workflow categorizes every new Gmail message with GPT‑5, routes it to the right next step, labels it in Gmail, and keeps your team posted in Telegram. You’ll see exactly what it automates, what results you get, and what you’ll need to run it.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Gmail to Telegram, smarter routing for every email

The Problem: Email Triage Eats Your Day

Most inbox pain isn’t typing responses. It’s the constant switching: read the email, decide if it’s support or sales or finance, search for the right “old answer,” forward it to the right person, then remember to follow up. And because it’s manual, the rules are inconsistent. Two similar messages get handled differently depending on who saw them first, or how rushed you were. Meanwhile, urgent stuff hides in plain sight, and the “I’ll reply later” pile turns into a quiet backlog.

It adds up fast. Here’s where it usually breaks down.

  • Reading and sorting 50+ emails can burn about 1–2 hours, and none of it moves work forward.
  • Without consistent labels, you can’t track what’s piling up, so support, sales, and finance issues blur together.
  • Forwarding to the right teammate is easy to forget, which means payments stall or customer issues linger.
  • Drafting replies from scratch leads to uneven tone and repeated rewrites, especially when you’re pulling info from policies or FAQs.

The Solution: GPT‑Routed Gmail That Updates Telegram Automatically

This workflow watches your Gmail inbox for new messages, then uses a GPT‑5 powered classifier to decide what category each email belongs to based on the sender, subject, and content. From there, it routes the email into a dedicated “agent” for that category. Support messages can be answered automatically using your FAQ and policy knowledge base stored in Pinecone, then replied to directly in Gmail and labeled “Customer Support.” Finance emails get labeled “Finance,” analyzed for whether they’re payments or receivables, then forwarded to the correct internal team, with a Telegram alert so nothing disappears. Sales inquiries get labeled “Sales Opportunities,” and the workflow creates a draft response for you to review, with a Telegram nudge if more info is needed. Internal emails get summarized and sent to you in Telegram, so you can react fast without living in Gmail.

The workflow starts when a new Gmail email arrives. GPT classifies it and hands it to the right agent (support, finance, sales, or internal). Finally, Gmail gets the right label and either a reply, a draft, or a forward happens, with Telegram messages keeping you in the loop.

What You Get: Automation vs. Results

Example: What This Looks Like

Say your inbox gets about 40 meaningful emails a day, and manual triage takes maybe 2 minutes each (read, decide, label, forward or start a reply). That’s around 80 minutes daily before you even do real work. With this workflow, the trigger is instant, classification and routing runs in the background, and you mostly spend time only on sales drafts that need approval, maybe 15–20 minutes a day. That’s roughly an hour back on an average day.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Gmail to monitor, label, draft, and reply.
  • Telegram for alerts and internal summaries.
  • OpenRouter API key (get it from your OpenRouter dashboard).
  • OpenAI API key for embeddings (get it from OpenAI API keys page).
  • Pinecone to store and search FAQs, policies, and business info.

Skill level: Intermediate. You’ll connect accounts, paste API keys, and adjust categories and prompts to match your business.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A new email arrives in Gmail. The Gmail trigger watches your inbox and pulls the key fields the AI needs (who it’s from, the subject line, and the body).

The email gets categorized by AI. A GPT‑5 classifier reviews the content and routes it into support, finance, sales/leads, internal mail, or a “do nothing” path for messages you don’t want to act on.

Each category takes the right action. Support can generate a reply using your Pinecone FAQ/policy knowledge. Finance can decide “payment” vs “receivable” and forward to the correct team. Sales can generate a draft and ask you to review if needed, which keeps quality high without slowing you down.

You get Telegram visibility without living in your inbox. When a finance email is forwarded, you get a Telegram alert. When a sales draft is created (or more info is required), Telegram tells you what to do next. Internal emails can be summarized into a quick message so you can respond faster.

You can easily modify the categories to match your teams (for example, “Partnerships” or “Hiring”) based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Gmail Trigger

Start by setting up the workflow trigger so new emails are captured and passed into the routing logic.

  1. Add and open Incoming Gmail Watcher.
  2. Credential Required: Connect your gmailOAuth2 credentials.
  3. Set Simple to false to retain full email metadata (headers, body, and IDs).

Step 2: Connect Email Routing and Classification

Route incoming emails into support, finance, sales, internal, or other branches using the classifier and model.

  1. Open Email Category Router and set Input Text to =From: {{ $json.headers.from }} Subject: {{ $json.headers.subject }} Email body: {{ $json.text }}.
  2. Confirm the categories in Email Category Router are configured for Customer Support, Finance, Others, Sales Opportunities, and Internal.
  3. Open OpenRouter GPT5 Mini and set Model to openai/gpt-5-mini.
  4. Credential Required: Connect your openRouterApi credentials on OpenRouter GPT5 Mini.
  5. Verify Email Category Router routes to Support Response Agent, Finance Review Agent, Sales Lead Agent, Internal Mail Agent, and Do Nothing Placeholder based on classification (not in parallel).

Step 3: Set Up Support Response AI

Generate customer support replies from the FAQ knowledge base and send a reply automatically.

  1. Open Support Response Agent and set Text to ={{ $json.text }}.
  2. Confirm OpenRouter Chat Mini is connected as the language model for Support Response Agent and set Model to openai/gpt-4o-mini.
  3. Credential Required: Connect your openRouterApi credentials on OpenRouter Chat Mini.
  4. Ensure FAQ Policy Vector Store is connected as a tool with Mode retrieve-as-tool and Tool Description Call this tool to access Policy and FAQ information.
  5. Credential Required: Connect your pineconeApi credentials on FAQ Policy Vector Store, and your openAiApi credentials on OpenAI Embedding Vector.
  6. Open Send Email Reply and set Operation to reply, Message to ={{ $json.output }}, and Message ID to ={{ $('Incoming Gmail Watcher').item.json.id }}.
  7. Credential Required: Connect your gmailOAuth2 credentials on Send Email Reply.
  8. Open Tag as Support and set Operation to addLabels and Message ID to ={{ $('Incoming Gmail Watcher').item.json.id }}.
  9. Credential Required: Connect your gmailOAuth2 credentials on Tag as Support.

Step 4: Configure Finance Review and Routing

Classify finance emails as receipts or vendor invoices, then alert the right team and Telegram channel.

  1. Open Finance Review Agent and confirm Text is set to =Here's a new email that came in: {{ $('Incoming Gmail Watcher').item.json.id }} Subject : {{ $('Incoming Gmail Watcher').item.json.headers.subject }} From : {{ $('Incoming Gmail Watcher').item.json.headers.from }} Email body : {{ $('Incoming Gmail Watcher').item.json.text }} .
  2. Ensure OpenRouter Chat Mini 2 is connected as the language model for Finance Review Agent and set Model to openai/gpt-4o-mini. Credential Required: Connect your openRouterApi credentials.
  3. Verify Finance Output Schema is attached as the output parser to Finance Review Agent (configure this on the parent agent).
  4. Confirm Tag as Finance is attached as an AI tool to Finance Review Agent and set Message ID to ={{ $('Incoming Gmail Watcher').item.json.id }} and Operation to addLabels. Credential Required: Connect your gmailOAuth2 credentials on the parent agent’s tool configuration.
  5. Open Route by Finance Type and confirm the two outputs evaluate Left Value as ={{ $json.output.emailType }} with boolean true for Customer Receipts and boolean false for Vendor Invoice.
  6. Configure Email Receivables Team with Send To [YOUR_EMAIL], Subject =Received {{ $json.output.Amount }} from {{ $json.output.From }}, and Message =Note receipt {{ $json.output.Amount }} from {{ $json.output.From }}. Credential Required: Connect your gmailOAuth2 credentials.
  7. Configure Email Payments Team with Send To [YOUR_EMAIL], Subject =Make Payment to {{ $json.output.From }} by {{ $json.output.DueDate }}, and Message =Invoice received from {{ $json.output.From }}. |Make payment by {{ $json.output.DueDate }}. Credential Required: Connect your gmailOAuth2 credentials.
  8. Set Telegram Receipt Alert Text to =📥 Income-ing! ${{ $json.output.Amount }} from {{ $json.output.From.split('<')[0].trim() }} and Telegram Payment Alert Text to =💲Pay ${{ $json.output.Amount }} to {{ $json.output.From.split('<')[0].trim() }}. Credential Required: Connect your telegramApi credentials.
⚠️ Common Pitfall: Replace [YOUR_EMAIL] in Email Receivables Team and Email Payments Team with real team inboxes, and set a valid Chat ID in Telegram Receipt Alert (currently =).

Step 5: Configure Sales Lead Processing

Use your knowledge base to draft sales replies, or notify you when manual review is needed.

  1. Open Sales Lead Agent and set Text to =Subject : {{ $json.headers.subject }} From : {{ $json.headers.from }} Email : {{ $json.text }}.
  2. Ensure OpenRouter Chat Mini 3 is connected as the language model and set Model to openai/gpt-4o-mini. Credential Required: Connect your openRouterApi credentials.
  3. Verify Business Services Vector is connected as a tool with Mode retrieve-as-tool and Tool Description Knowledge of the business and services it provides. Credential Required: Connect your pineconeApi credentials, and your openAiApi credentials on OpenAI Embedding Vector 2.
  4. Confirm Sales Output Schema is attached as the output parser to Sales Lead Agent (configure this on the parent agent).
  5. Ensure Tag Sales Opportunities is attached as an AI tool to Sales Lead Agent with Message ID ={{ $('Incoming Gmail Watcher').item.json.id }} and Operation addLabels. Credential Required: Connect your gmailOAuth2 credentials on the parent agent’s tool configuration.
  6. Open Requires Review? and confirm the condition uses Left Value ={{ $json.output.escalate }} with boolean true to trigger manual review.
  7. Configure Notify Manual Review Text to =📥 New lead: {{ $('Incoming Gmail Watcher').item.json.from.value[0].name }} I searched the knowledge database but I wasn't sure how to respond. Please see your email!. Credential Required: Connect your telegramApi credentials.
  8. Configure Create Email Draft with Resource draft, Email Type html, Message ={{ $json.output.emailBody }}, and Subject =Re: {{ $('Incoming Gmail Watcher').item.json.subject }}. Credential Required: Connect your gmailOAuth2 credentials.
  9. Set Notify Draft Review Text to =📥 New lead: {{ $('Incoming Gmail Watcher').item.json.from.value[0].name }} I searched the knowledge database and drafted a reply for you. Please check your email! Facts used: {{ $json.output.knowledgeDatabase }} Rationale in email reply: {{ $json.output.reason }}. Credential Required: Connect your telegramApi credentials.

Step 6: Configure Internal Email Summaries and Placeholders

Summarize internal emails and label them, while keeping a placeholder for non-matching categories.

  1. Open Internal Mail Agent and set Text to =Subject : {{ $json.headers.subject }} From : {{ $json.headers.from }} Email : {{ $json.text }}.
  2. Ensure OpenRouter Chat Mini 4 is connected as the language model and set Model to openai/gpt-4o-mini. Credential Required: Connect your openRouterApi credentials.
  3. Confirm Internal Output Schema is attached as the output parser to Internal Mail Agent (configure this on the parent agent).
  4. Attach Tag as Internal as an AI tool to Internal Mail Agent with Message ID ={{ $('Incoming Gmail Watcher').item.json.id }} and Operation addLabels. Credential Required: Connect your gmailOAuth2 credentials on the parent agent’s tool configuration.
  5. Set Telegram Internal Summary Text to ={{ $json.output.From }} sent you an email about {{ $json.output.emailBody }}. Credential Required: Connect your telegramApi credentials.
  6. Leave Do Nothing Placeholder in place to catch uncategorized emails for future expansion or debugging.

Step 7: Test and Activate Your Workflow

Verify each branch works correctly before enabling production automation.

  1. Click Execute Workflow and send a test email that matches each category (Support, Finance, Sales Opportunities, Internal, and Others).
  2. Confirm that Support Response Agent leads to Send Email Reply and then Tag as Support.
  3. Confirm Finance Review Agent routes through Route by Finance Type and triggers Email Receivables Team or Email Payments Team followed by the matching Telegram alert.
  4. Confirm Sales Lead Agent sends to Requires Review? and either Notify Manual Review or Create Email Draft → Notify Draft Review.
  5. Confirm Internal Mail Agent sends a message to Telegram Internal Summary and labels the email with Tag as Internal.
  6. When results look correct, toggle the workflow Active to enable continuous email triage.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Gmail permissions are picky. If labeling or drafting fails, check the connected Google account in n8n credentials and confirm it has Gmail access to read, label, and send.
  • If you’re relying on external AI calls (OpenRouter, embeddings, Pinecone), occasional slow responses happen. Increase any wait time you use and watch the n8n execution log to confirm downstream nodes aren’t running with empty data.
  • The default agent prompts are usually too generic for real businesses. Add your brand voice, your refund policy, and “when to escalate to a human” early, or you’ll spend your time cleaning up drafts.

Related Workflows

If your team also lives in Slack, not Telegram, the same idea works there too. Gmail + Slack: smarter triage, faster replies is a solid pairing when you want alerts to land where the team already collaborates.

Need a lighter-weight support setup that focuses mostly on pulling answers from a knowledge base? Gmail + Pinecone: instant FAQ replies, less inbox noise goes deeper on the “knowledge-first” part of the system.

For teams that want AI-written replies but don’t need multi-agent routing yet, Gmail + OpenAI: faster support replies, less inbox load is a simpler on-ramp that still saves a lot of time.

When email is split across providers, it helps to standardize urgency handling. Outlook to Slack, urgent emails flagged fast is useful if part of your org is on Outlook but you still want consistent alerting.

Finally, if you want to improve output quality (less “AI-sounding,” fewer rewrites), OpenAI + Gmail: better system prompts, less rewrites pairs well with this workflow because prompt discipline is what makes routing and drafting actually dependable.


Quick reference:

Frequently Asked Questions

How long does it take to set up this Gmail Telegram routing automation?

About an hour if you already have your API keys and bot ready.

Do I need coding skills to automate Gmail Telegram routing?

No. You’ll connect accounts, paste API keys, and adjust a few category rules and prompts.

Is n8n free to use for this Gmail Telegram routing workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenRouter/OpenAI usage plus Pinecone costs for vector search.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this Gmail Telegram routing workflow for Outlook instead of Gmail?

Yes, but you’ll need to swap the Gmail trigger and Gmail send/draft/label actions for Outlook equivalents. The classification and routing logic stays the same, so most edits are at the “inbox” and “send message” parts of the workflow. Many teams also customize categories like “Partnerships,” “Hiring,” or “VIP clients,” then tune the prompts so each agent knows what to do.

Why is my Gmail connection failing in this workflow?

Usually it’s expired or revoked Google permissions in n8n credentials, so reconnect the Gmail account and try again. If drafts or labels fail but reading works, double-check that the account has the right Gmail access scopes enabled. Rate limits can also show up when you process big batches, especially if you rerun old executions.

How many emails can this Gmail Telegram routing automation handle?

A typical small business inbox volume is fine, and scaling mostly depends on your n8n plan and your AI API limits.

Is this Gmail Telegram routing automation better than using Zapier or Make?

It depends on how far you want to take it. Zapier and Make are great for simple “if subject contains X, send message to Y” style automations, and they’re easy to maintain. This workflow leans on multi-step AI agents, structured outputs, and a knowledge base (Pinecone), which is the kind of logic that gets awkward or expensive in simpler tools. n8n also gives you a self-hosted option, which matters if you want more control and fewer execution limits. If you’re unsure, Talk to an automation expert and we’ll help you pick the cleanest approach.

Once this is running, your inbox stops being a guessing game. The workflow handles the repetitive sorting and nudging, and you focus on the few messages that truly need your judgment.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.