Gmail + Telegram: smarter triage and draft replies

Your inbox doesn’t get “busy.” It gets chaotic. Important threads slip under promos, people follow up because you didn’t see their last message, and by the time you reply you’re already behind.

This Gmail Telegram triage automation hits customer support leads first, honestly, but founders and sales reps feel the same pain. You get a labeled inbox, AI-assisted draft replies, and Telegram alerts when something needs attention now.

Below you’ll see what the workflow does, the results to expect, and how the moving parts fit together so you can adapt it to your process.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: Gmail + Telegram: smarter triage and draft replies

Click to explore

flowchart LR

    subgraph sg0["Gmail Flow"]
        direction LR
        n0@{ icon: "mdi:robot", form: "rounded", label: "Sentiment Analysis", pos: "b", h: 48 }
        n1@{ icon: "mdi:brain", form: "rounded", label: "Azure OpenAI Chat Model", pos: "b", h: 48 }
        n2@{ icon: "mdi:message-outline", form: "rounded", label: "Spam", pos: "b", h: 48 }
        n3@{ icon: "mdi:message-outline", form: "rounded", label: "Gmail", pos: "b", h: 48 }
        n4@{ icon: "mdi:message-outline", form: "rounded", label: "Important", pos: "b", h: 48 }
        n5@{ icon: "mdi:message-outline", form: "rounded", label: "Promotion", pos: "b", h: 48 }
        n6@{ icon: "mdi:message-outline", form: "rounded", label: "Notification", pos: "b", h: 48 }
        n7@{ icon: "mdi:message-outline", form: "rounded", label: "Personal", pos: "b", h: 48 }
        n8@{ icon: "mdi:message-outline", form: "rounded", label: "Call request", pos: "b", h: 48 }
        n9@{ icon: "mdi:message-outline", form: "rounded", label: "Needs Reply", pos: "b", h: 48 }
        n10@{ icon: "mdi:robot", form: "rounded", label: "important?", pos: "b", h: 48 }
        n11@{ icon: "mdi:robot", form: "rounded", label: "Draft Reply", pos: "b", h: 48 }
        n12@{ icon: "mdi:swap-vertical", form: "rounded", label: "$INPUTS$", pos: "b", h: 48 }
        n13@{ icon: "mdi:message-outline", form: "rounded", label: "Draft", pos: "b", h: 48 }
        n14@{ icon: "mdi:message-outline", form: "rounded", label: "Get emails", pos: "b", h: 48 }
        n15@{ icon: "mdi:robot", form: "rounded", label: "needs reply?", pos: "b", h: 48 }
        n16@{ icon: "mdi:cog", form: "rounded", label: "No Operation, do nothing", pos: "b", h: 48 }
        n17["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Telegram"]
        n18@{ icon: "mdi:location-exit", form: "rounded", label: "Google Calendar", pos: "b", h: 48 }
        n19@{ icon: "mdi:play-circle", form: "rounded", label: "Gmail Trigger", pos: "b", h: 48 }
        n20@{ icon: "mdi:robot", form: "rounded", label: "json schema", pos: "b", h: 48 }
        n21@{ icon: "mdi:message-outline", form: "rounded", label: "Write draft", pos: "b", h: 48 }
        n2 --> n3
        n13 -.-> n11
        n12 --> n0
        n7 --> n11
        n4 --> n15
        n5 --> n10
        n14 -.-> n11
        n10 --> n3
        n10 --> n4
        n11 --> n21
        n9 --> n11
        n21 --> n17
        n20 -.-> n11
        n8 --> n11
        n6 --> n10
        n15 --> n11
        n15 --> n16
        n19 --> n12
        n18 -.-> n11
        n0 --> n2
        n0 --> n4
        n0 --> n5
        n0 --> n6
        n0 --> n7
        n0 --> n8
        n0 --> n9
        n1 -.-> n0
        n1 -.-> n10
        n1 -.-> n11
        n1 -.-> n15
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n19 trigger
    class n0,n10,n11,n15,n20 ai
    class n1 aiModel
    classDef customIcon fill:none,stroke:none
    class n17 customIcon

Why This Matters: Inbox triage is stealing your best hours

Most inbox stress isn’t “too many emails.” It’s decision fatigue. Every new message forces a mini-triage: Is this spam? Is it urgent? Do I need to reply, or can it wait? You do that dozens of times a day, then you do it again when you come back after meetings. And when you’re rushed, you miss the subtle stuff: a client hinting they’re unhappy, a lead asking for a call, or a teammate waiting on a yes/no to move a project forward.

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

You spend about 1–2 hours a day just scanning and sorting messages that never needed your brain in the first place.
Urgent threads get buried, so you end up reacting late instead of responding on your terms.
“Quick replies” aren’t quick when you have to reread the whole thread and reconstruct context every time.
Manual labeling is inconsistent, which means search, delegation, and follow-up workflows never quite stick.

What You’ll Build: AI triage, Gmail labels, drafts, and Telegram alerts

This workflow watches your Gmail inbox for new messages, then immediately runs them through AI-based classification. It routes each email into a clear category like Spam, Promotion, Notification, Personal, Call Request, or Needs Reply, and applies the right Gmail handling so your inbox stays readable. Next, it evaluates tone and urgency (sentiment and priority checks) to decide what deserves a faster path. If a message looks like it requires a response, the workflow generates a context-aware draft reply that fits the thread, creates that draft in Gmail, and pings you in Telegram so you can review and send. For call requests or follow-ups, it can also use a calendar helper to schedule the next step without you juggling tabs.

The workflow starts with a Gmail trigger. AI analyzes the message and assigns it to the right “lane,” then it makes a judgment call about whether a reply is needed. Finally, it creates a Gmail draft and sends a Telegram alert for the threads you don’t want to miss.

What You’re Building

What Gets Automated

What You’ll Achieve

New Gmail messages are categorized into practical buckets like Promo, Personal, and Needs Reply.
Sentiment and priority checks decide what deserves immediate attention.
Draft replies are generated with thread context and saved directly in Gmail.
Telegram notifications fire for urgent or reply-worthy messages so you can act quickly.

Cut daily inbox triage from about 90 minutes to roughly 10 minutes of review.
Fewer missed “quietly urgent” emails, because they surface in Telegram.
Faster response times without sending raw AI replies, since you edit drafts first.
A more consistent labeling system, which makes search and delegation easier.
Cleaner follow-ups for call requests and time-sensitive conversations.

Expected Results

Say you get about 40 emails a day. Manually triaging and opening threads “just to check” can easily take 2 minutes each, so you’re burning about 80 minutes before you’ve even replied to anyone. With this workflow running: messages get labeled automatically, you only open the ones flagged as Priority or Needs Reply, and you start from a ready-to-edit draft. Realistically, that turns into about 10 minutes of review plus a few quick edits. That’s roughly an hour back most days.

Before You Start

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Gmail for reading, labeling, and creating drafts.
Telegram to receive urgent thread alerts.
OpenAI or Azure OpenAI API key (get it from your OpenAI or Azure portal) to classify emails and draft replies.

Skill level: Intermediate. You’ll connect accounts, map a few fields, and adjust prompts to match your tone.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

A new email arrives in Gmail. The Gmail Trigger fires as soon as a message hits your inbox (or a specific label/folder, depending on how you configure it). The workflow maps the useful fields like sender, subject, body, and thread identifiers so the rest of the steps have clean inputs.

AI classifies the message. Sentiment insights and a chat model analyze the content and decide which category it belongs to: spam, promo, notification, personal, call request, or needs reply. That decision controls where the email is routed next.

Priority and reply checks kick in. For categories like promotions or alerts, an extra priority check can bump something into “Priority” if it’s more urgent than it looks. A reply check determines if the email truly needs a response, so you’re not drafting replies to FYIs.

Drafts and notifications get created. If a response is needed, the AI Agent composes a reply using thread context, then Gmail creates a draft you can edit and send. Telegram gets a concise notification so you notice urgent threads without living in your inbox.

You can easily modify the categories and alert rules to match your workflow, like only notifying on “Call Request” or escalating negative sentiment. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Gmail Trigger

Set up the trigger that listens for incoming Gmail events and starts the triage flow.

Add and open Gmail Event Trigger.
Select the Gmail trigger options appropriate for your mailbox (use your existing workflow defaults if already configured).
Credential Required: Connect your Gmail credentials.
Connect Gmail Event Trigger to Input Mapper to match the execution flow.

⚠️ Common Pitfall: If the Gmail trigger is not authorized, the workflow will never start. Make sure the Gmail account has API access enabled.

Step 2: Connect Gmail for Routing and Draft Actions

This workflow uses multiple Gmail nodes to route messages into different inbox labels and to create drafts.

Open each Gmail routing node and confirm it points to the correct label or mailbox: Junk Mailbox, General Inbox, Priority Inbox, Promo Inbox, Alert Inbox, Personal Inbox, Call Request Inbox, and Reply Needed.
Open Create Draft Email and confirm it is set to create a draft in the same Gmail account.
Credential Required: Connect your Gmail credentials to all Gmail nodes (9 total, including Create Draft Email).
Ensure the execution flow matches the workflow: Junk Mailbox → General Inbox.

Use consistent Gmail credentials across all Gmail nodes to avoid cross-account label conflicts.

Step 3: Set Up Sentiment and Priority Routing

Sentiment checks drive how messages are routed across the various inboxes.

Open Input Mapper and ensure it formats the incoming email fields required by downstream nodes.
Configure Sentiment Insights to analyze the email content coming from Input Mapper.
Confirm the routing branches from Sentiment Insights to Junk Mailbox, Priority Inbox, Promo Inbox, Alert Inbox, Personal Inbox, Call Request Inbox, and Reply Needed.
Verify Priority Check routes to both General Inbox and Priority Inbox, and Reply Check routes to Compose Draft or Idle Step.
Credential Required: Connect your Azure OpenAI credentials to Azure Chat Model and ensure it is linked to Sentiment Insights, Priority Check, and Reply Check.

Step 4: Set Up AI Drafting with Tools and Schema

The AI agent generates reply drafts and uses tools for Gmail and Calendar context.

Open Compose Draft and confirm it is connected to Azure Chat Model as the language model.
Attach the AI tool nodes to Compose Draft: Draft Utility, Retrieve Messages, and Calendar Helper.
Attach Structured Schema as the output parser for Compose Draft.
Credential Required: Add Gmail credentials and Google Calendar credentials to Compose Draft (not the tool sub-nodes). These tools inherit credentials from the parent agent.
Credential Required: Connect your Azure OpenAI credentials to Azure Chat Model for draft generation.

⚠️ Common Pitfall: Do not add credentials directly to Draft Utility, Retrieve Messages, Calendar Helper, or Structured Schema. These are AI sub-nodes and must inherit credentials from Compose Draft and Azure Chat Model.

Step 5: Configure Output Notifications

Finalize the output actions that create drafts and send alerts.

Verify the main draft flow: Compose Draft → Create Draft Email → Telegram Notify.
Open Telegram Notify and set the chat destination for triage alerts.
Credential Required: Connect your Telegram credentials in Telegram Notify.
Keep Idle Step as a no-operation branch for messages that should not be drafted.

Final Step: Test and Activate Your Workflow

Run end-to-end tests to validate routing, drafting, and notifications before going live.

Use Execute Workflow to run a manual test with a recent Gmail message.
Confirm that messages are routed from Sentiment Insights to the correct Gmail label nodes and that drafts are created by Create Draft Email.
Check that Telegram Notify posts a message when a draft is created.
Activate the workflow using the Active toggle when results match expectations.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

Gmail credentials can expire or need specific permissions. If things break, check your Gmail OAuth connection in n8n’s Credentials section first.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Quick Answers

What’s the setup time for this Gmail Telegram triage automation?

About 30 minutes if your Gmail, Telegram, and AI credentials are ready.

Is coding required for this inbox triage automation?

No. You’ll mostly connect accounts and adjust a few text prompts and categories.

Is n8n free to use for this Gmail Telegram triage 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 OpenAI or Azure OpenAI usage (for many teams, it’s a few dollars a month unless you’re drafting at very high volume).

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 modify this Gmail Telegram triage workflow for different use cases?

Yes, and you should. Most teams start by editing the categories produced by the Structured Schema step, then adjusting what counts as “urgent” in the Priority Check and Reply Check steps. You can also swap the Telegram Notify step for Discord or Slack, and keep the rest of the logic the same. If you want calendar automation to do more, the Calendar Helper can be extended to create events with attendees and meeting links.

Why is my Gmail connection failing in this workflow?

Usually it’s expired OAuth permissions or the wrong Gmail scope. Reconnect your Gmail credential in n8n, then confirm the workflow is pointing at the right Gmail account and label/mailbox. If drafts are failing, also check that your Google account allows draft creation for that mailbox (workspace policies can block it). And if it breaks only during busy periods, you may be hitting Gmail API rate limits.

What volume can this Gmail Telegram triage workflow process?

On a typical n8n Cloud plan you can handle thousands of executions per month, and self-hosting removes execution limits (your server becomes the ceiling). Practically, the AI call is the slow part, so expect high-volume inboxes to queue. If you’re processing hundreds of emails a day, consider batching and only drafting for “Needs Reply” to keep costs and noise under control.

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

It depends. n8n is better when you want branching logic (multiple categories, priority checks, reply checks) and you don’t want to pay extra for every path and filter. It’s also easier to self-host, which matters if you process a lot of emails. Zapier or Make can feel simpler for a basic “Gmail to Telegram notification,” but they get messy once you add AI classification and threaded drafting. If you want help deciding, Talk to an automation expert and describe your volume and reply style.

Once this is running, your inbox turns into a queue you can trust. The workflow handles the sorting and the first draft, and you stay in control of what actually gets sent.

Gmail + Telegram: smarter triage and draft replies

How This Automation Works

n8n Workflow Template: Gmail + Telegram: smarter triage and draft replies

Why This Matters: Inbox triage is stealing your best hours