Telegram + Gmail, send follow ups from one chat

Your follow-ups don’t fall through because you’re careless. They fall through because your day is split across Telegram, Gmail, Calendar, and a dozen tiny “I’ll do that later” moments.

Founders feel it when a warm lead goes cold. Client-facing marketers feel it after back-to-back calls. And ops leads notice it when “quick admin” becomes the whole afternoon. This Telegram Gmail automation pulls the busywork into one chat so you can send the follow-up while the context is still fresh.

This workflow turns Telegram into an AI personal assistant: it can check your schedule, pull contact info from Sheets, draft and send emails via Gmail, and even do quick web research when you ask. You’ll see how it works, what you need, and where teams usually trip up.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Telegram + Gmail, send follow ups from one chat

Click to explore

flowchart LR

    subgraph sg0["Telegram Flow"]
        direction LR
        n0["<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 Trigger"]
        n1@{ icon: "mdi:robot", form: "rounded", label: "AI Agent", pos: "b", h: 48 }
        n2["<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 Response"]
        n3@{ icon: "mdi:wrench", form: "rounded", label: "Wikipedia Tool", pos: "b", h: 48 }
        n4@{ icon: "mdi:wrench", form: "rounded", label: "Web Search (SerpAPI)", pos: "b", h: 48 }
        n5@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
        n6@{ icon: "mdi:memory", form: "rounded", label: "Conversation Memory", pos: "b", h: 48 }
        n7@{ icon: "mdi:location-exit", form: "rounded", label: "Google Calendar", pos: "b", h: 48 }
        n8@{ icon: "mdi:message-outline", form: "rounded", label: "Gmail Tool", pos: "b", h: 48 }
        n9@{ icon: "mdi:database", form: "rounded", label: "Get Contacts", pos: "b", h: 48 }
        n10@{ icon: "mdi:location-exit", form: "rounded", label: "Get Calendar Events", pos: "b", h: 48 }
        n1 --> n2
        n8 -.-> n1
        n9 -.-> n1
        n3 -.-> n1
        n7 -.-> n1
        n0 --> n1
        n5 -.-> n1
        n6 -.-> n1
        n10 -.-> n1
        n4 -.-> n1
    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 n0 trigger
    class n1 ai
    class n5 aiModel
    class n3,n4 ai
    class n6 ai
    class n9 database
    classDef customIcon fill:none,stroke:none
    class n0,n2 customIcon

The Problem: Follow-Ups Get Lost Between Apps

You finish a call, open Telegram to send “great speaking,” then realize you need the person’s email. So you jump to a spreadsheet (if it’s up to date), then to Gmail, then to Calendar to check what you promised, then back to Telegram because another message came in. Somewhere in that shuffle, the follow-up becomes tomorrow’s problem. Multiply that by a few clients, a few internal threads, and a few random “can you send this?” requests, and you end the week with a trail of half-finished tasks and awkward delays.

It adds up fast. Here’s where it breaks down in real life.

After meetings, you spend about 10 minutes hunting context before you write anything useful.
Contact details live in multiple places, so you either guess the email format or ask someone (again).
Calendar and inbox don’t talk, which means follow-ups aren’t tied to what actually happened that day.
When you’re busy, “I’ll send it later” becomes “I forgot,” and that’s a terrible look.

The Solution: A Telegram Assistant That Sends the Email for You

This workflow creates a Telegram bot that behaves like a practical personal assistant. You message it in plain English, and an AI agent decides what to do next: check your Google Calendar, look up a contact in Google Sheets, draft a follow-up, and send it through Gmail. Because it keeps a short conversation memory, you can speak naturally instead of repeating details every time. You can also ask it to look things up on Wikipedia or the web (via SerpAPI) when you need a quick answer mid-conversation. The end result is simple: you run your day from one chat window, while your calendar and inbox stay updated behind the scenes.

The workflow starts when someone (you) messages the Telegram bot. From there, the AI agent routes the request to the right tool: calendar, contacts, email, or research. Finally, it replies in Telegram with confirmation, details, or the content it sent.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

Telegram messages trigger actions instead of opening three separate apps.
The assistant pulls contact details from Google Sheets before writing an email.
Gmail sending happens inside the workflow, including drafting and dispatch.
Google Calendar lookups return your day’s events on demand (or as a daily schedule email).

Most teams get about 2 hours back each week just from fewer context switches.
Follow-ups go out while the meeting is still fresh, which usually means faster replies.
You stop re-checking calendars because the assistant can tell you what’s next.
Fewer “what’s their email again?” moments because contacts live in one source.
A cleaner record of what was sent and when, which helps with accountability.

Example: What This Looks Like

Say you have 8 client calls in a week and you send a follow-up after each one. Manually, it’s easy to burn about 15 minutes per follow-up between finding the contact, checking the calendar notes, writing, and sending, which is around 2 hours weekly. With this workflow, you message the bot right after the call (“Send a recap to Sarah and propose Tuesday at 2”), then wait a minute or two for the assistant to pull the email from Sheets, check Calendar, and send via Gmail. The “work” on your side is basically one message.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Telegram Bot to receive requests and reply in chat.
Gmail to draft and send follow-up emails.
Google Calendar to read events and plan availability.
Google Sheets for your contact list (names, emails).
OpenAI API key (get it from the OpenAI platform dashboard).
SerpAPI key (get it from your SerpAPI account dashboard).

Skill level: Intermediate. You’ll connect accounts, set permissions (OAuth), and tweak a few assistant instructions.

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

How It Works

A Telegram message kicks things off. You send a request like “What’s on my calendar today?” or “Email John about the proposal,” and the workflow receives it instantly through your bot.

The AI agent figures out what you meant. Using an OpenAI chat model plus a small memory buffer, it keeps enough context to handle follow-ups like “Actually, make it shorter” without you re-explaining everything.

The workflow uses the right tools for the job. Calendar questions go to Google Calendar, email requests go to Gmail, and contact lookups pull from your Google Sheets database. If you ask a knowledge question, it can query Wikipedia or run a web search through SerpAPI.

You get a clear response in Telegram. Sometimes that’s a confirmation (“Sent”), sometimes it’s a formatted agenda, and sometimes it’s the drafted message you can approve before sending, depending on how you configure the agent.

You can easily modify the assistant instructions to require approval before sending emails based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Telegram Trigger

Set up the incoming Telegram trigger so your assistant reacts to new messages.

Add and open Telegram Incoming Trigger.
Confirm Updates includes message.
Credential Required: Connect your Telegram credentials (bot token) in Telegram Incoming Trigger.

⚠️ Common Pitfall: The workflow will not trigger unless the Telegram bot token is valid and the bot has been started in the target chat.

Step 2: Connect Google and Email Services

These tools are used by the assistant to read contacts, manage calendar events, and send emails.

Open Retrieve Contact List and set Document ID to [YOUR_ID] and Sheet Name to gid=0.
Open Calendar Event Manager and set Calendar to [YOUR_EMAIL].
Open Fetch Calendar Events and set Operation to getAll, and Calendar to [YOUR_EMAIL].
Credential Required: Connect your Google Sheets credentials to Retrieve Contact List.
Credential Required: Connect your Google Calendar credentials to Calendar Event Manager and Fetch Calendar Events.
Credential Required: Connect your Gmail credentials to Gmail Dispatch Tool.

Tip: The AI tools Calendar Event Manager, Fetch Calendar Events, Retrieve Contact List, and Gmail Dispatch Tool are connected to Assistant Reasoning Hub as AI tools—ensure credentials are added on each tool node, not on the agent.

Step 3: Set Up the AI Reasoning and Memory

Configure the AI agent, language model, and memory so it can interpret messages and maintain context.

Open Assistant Reasoning Hub and set Text to {{ $json.message.text }}.
In Assistant Reasoning Hub, confirm Prompt Type is define and keep the System Message instructions as provided.
Open OpenAI Chat Engine and set Model to gpt-4o-mini.
Open Dialogue Memory Buffer and set Session Key to {{ $('Telegram Incoming Trigger').item.json.message.from.id }} and Context Window Length to 10.
Credential Required: Connect your OpenAI credentials in OpenAI Chat Engine (language model for Assistant Reasoning Hub).
Credential Required: Connect your SerpAPI credentials in Web Search Utility (used as an AI tool by Assistant Reasoning Hub).

⚠️ Common Pitfall: AI tool nodes like Wikipedia Lookup Tool and Web Search Utility should be connected to Assistant Reasoning Hub as tools; do not wire them into the main execution flow.

Step 4: Configure Telegram Output

Send the AI-generated response back to the user in Telegram.

Open Telegram Reply Sender and set Text to {{ $json.output }}.
Set Chat ID to {{ $('Telegram Incoming Trigger').item.json.message.chat.id }}.
Credential Required: Connect your Telegram credentials in Telegram Reply Sender.

Step 5: Test and Activate Your Workflow

Verify the full flow from message input to AI response and enable it for live use.

Click Test Workflow and send a message to your Telegram bot.
Confirm the execution flow runs Telegram Incoming Trigger → Assistant Reasoning Hub → Telegram Reply Sender.
Check that the reply arrives in Telegram and includes the AI-generated response.
Once verified, toggle the workflow to Active to enable live automation.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

Google (Gmail/Calendar/Sheets) credentials can expire or need specific scopes. If things break, check your credential status in n8n and your Google Cloud OAuth consent/scopes 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.

Frequently Asked Questions

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

About an hour if you already have your Google and Telegram accounts ready.

Do I need coding skills to automate Telegram Gmail automation?

No. You’ll mostly be connecting accounts and pasting API keys. The “hardest” part is usually getting Google OAuth permissions set correctly.

Is n8n free to use for this Telegram Gmail automation 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 and SerpAPI usage costs (usually a few dollars a month for light use).

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 Telegram Gmail automation workflow for “approve before sending”?

Yes, and honestly you probably should at first. Update the AI agent’s system message to require confirmation, then have it draft the email and send the draft back to Telegram for an “OK to send?” reply. Many teams also customize the Google Sheets contact lookup (so it matches by name, company, or both), and they tighten Gmail permissions so only specific actions are allowed.

Why is my Telegram connection failing in this workflow?

Usually it’s the bot token or webhook setup. Regenerate the token in BotFather if you suspect it was exposed, then update the Telegram credentials inside n8n. Also double-check that your workflow is active and that the trigger is listening, because inactive workflows look like “the bot is broken.”

How many messages can this Telegram Gmail automation automation handle?

A lot.

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

Often, yes, because the “assistant” part needs branching logic, memory, and multiple tools working together. n8n makes that easier to control, and self-hosting means you’re not paying per tiny step when conversations get chatty. Zapier or Make can still work if you only need something simple, like “Telegram message → send a templated email.” If you want research, contact lookup, and calendar-aware follow-ups in the same flow, n8n is usually the cleaner fit. Talk to an automation expert if you want a quick recommendation for your exact setup.

You don’t need a new productivity system. You need fewer handoffs. Set this up once, and your follow-ups stop living in your head.

Telegram + Gmail, send follow ups from one chat

How This Automation Works

n8n Workflow Template: Telegram + Gmail, send follow ups from one chat

The Problem: Follow-Ups Get Lost Between Apps