🔓 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

Telegram to Gmail, follow-ups that stop on reply

Telegram to Gmail, follow-ups that stop on reply - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Telegram to Gmail, follow-ups that stop on reply - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

You had a good call. You took notes. Then the day happens, the follow-up email gets delayed, and the lead quietly goes cold.

This is the kind of mess account executives feel every week, and it hits founders even harder because there’s no one else to pick up the slack. Agencies running outreach for clients deal with it too. With Telegram Gmail follow-ups automated, you can keep a consistent 3-touch sequence going without sounding like a robot.

This workflow captures leads in Telegram, writes personal emails with AI, sends them from Gmail (or SMTP), and stops the moment someone replies. You’ll see what it does, 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 to Gmail, follow-ups that stop on reply

The Problem: Follow-ups slip, and “personal” doesn’t scale

Most teams don’t lose leads because the offer is bad. They lose them because the follow-up process is uneven. One rep sends a thoughtful email right after the call, another waits two days, and someone else copies a template that feels… copy-pasted. Then replies get missed, or worse, a second follow-up goes out after the lead already answered (which is a fast way to look disorganized). It also creates a mental load you carry all day. “Did I email that prospect?” “Did they reply?” “Was I supposed to nudge them again?”

The friction compounds. Not in a dramatic way. In the slow, expensive way.

  • After each call, you end up rewriting the same “great speaking with you” email for the tenth time that week.
  • It’s easy to forget the 24-hour follow-up, especially when your calendar is stacked.
  • Replies are scattered across inboxes, so you can’t quickly see which leads are active versus already handled.
  • Manual tracking in a sheet usually gets updated “later,” which means it’s not reliable when you need it.

The Solution: Telegram lead intake → AI emails → Gmail follow-ups that stop on reply

This n8n workflow turns your post-call notes into a complete, tracked follow-up sequence. A sales agent drops lead details into a Telegram bot (name, company, email, and a few notes from the conversation). AI then extracts and structures the info, saves it to a lead table, and generates a tailored first email that matches the situation and the tone you want. n8n sends that email immediately, updates the lead status, and pings the agent in Telegram so they know it went out. After that, scheduled checks handle the follow-ups automatically: a second message after about 24 hours, then a final touch if there’s still no reply. The important part is reply detection. Each day, the workflow scans Gmail, marks leads as replied when it finds a response, and stops any future follow-ups.

The workflow starts with Telegram lead intake. In the middle, Gemini generates email copy for each step of the sequence while n8n logs content and status to your data table (and optionally Google Sheets). Finally, Gmail monitoring prevents awkward double-taps by shutting down the sequence when the lead responds.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you handle 10 leads a week from calls. Manually, you might spend about 10 minutes drafting the first email, another 5 minutes scheduling or setting reminders, and then 10 minutes across the week checking replies and updating a sheet. That’s roughly 25 minutes per lead, or about 4 hours a week. With this workflow, the “manual” part is dropping the lead into Telegram (maybe 1 minute). The sequence sends itself, and the daily Gmail scan handles reply detection in the background.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Telegram Bot for lead submission and alerts
  • Gmail account to send and detect replies
  • Gemini API Key (get it from Google AI Studio)

Skill level: Intermediate. You’ll connect accounts, set a data table (or sheet), and paste an API key.

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

How It Works

A lead comes in through Telegram. After a call, you message your bot with the lead’s name, email, company, and quick notes. That single message is the trigger that starts everything.

The workflow cleans and structures the info. Gemini extracts key fields from the notes, and n8n writes a new record to your data table (status, sequence number, last sent date, plus storage fields for email subject/body).

AI writes the email for the right moment. The first email is warm and conversational, the second adds value and context, and the third is short and respectful. n8n then sends via the email node and updates the lead record so you can audit what went out.

Reply detection stops the sequence. On a daily schedule, n8n pulls active leads, searches Gmail for responses, flags leads as replied, and sends a Telegram notification to the agent so they can take over the human part.

You can easily modify the follow-up timing or message style to match your sales motion. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Telegram Trigger

Set up the workflow entry point so new leads arrive from Telegram into the automation pipeline.

  1. Add and open Telegram Lead Intake.
  2. Connect the Telegram bot you want to use for lead intake.
  3. Save the node so it registers the webhook.

Credential Required: Connect your Telegram API credentials.

⚠️ Common Pitfall: If the webhook is not registered, Telegram will not deliver messages to Telegram Lead Intake. Save the node after connecting credentials.

Step 2: Set Up Lead Extraction with AI

Configure the AI pipeline that parses incoming lead messages into structured data.

  1. Open AI Lead Data Extract and define the prompt or system instructions for lead parsing.
  2. Ensure Gemini Parsing Model is connected as the language model for AI Lead Data Extract.
  3. Ensure Structured JSON Parser is connected as the output parser for AI Lead Data Extract.

Credential Required: Connect your Google Gemini credentials in Gemini Parsing Model.

Note: Structured JSON Parser is an AI tool sub-node; credentials should be added to the parent node Gemini Parsing Model used by AI Lead Data Extract.

Step 3: Persist Lead Data and Compose the First Email

Store extracted lead data, initialize tracking, and generate the first email with AI.

  1. Open Add Table Record and map the extracted lead fields into your data table.
  2. Configure Init Lead Tracking to set status fields and timestamps for the lead.
  3. Open AI Email Composer and define the email generation instructions.
  4. Ensure Gemini Email Model is connected as the language model for AI Email Composer.
  5. Ensure Email JSON Extractor is connected as the output parser for AI Email Composer.
  6. Map the output in Prepare Email Fields for subject, body, and recipient.

Credential Required: Connect your Google Gemini credentials in Gemini Email Model.

Note: Email JSON Extractor is an AI tool sub-node; credentials should be added to the parent node Gemini Email Model used by AI Email Composer.

Step 4: Configure Initial Email Dispatch and Agent Notifications

Send the first email and update records, then notify your agent in Telegram.

  1. Open Dispatch Email and configure the sender account and email fields.
  2. Verify Modify Table Records updates the lead status after the email is sent.
  3. Open Notify Agent Email Sent and set the message format and target chat.

Credential Required: Connect your SMTP credentials in Dispatch Email.

Credential Required: Connect your Telegram API credentials in Notify Agent Email Sent.

Step 5: Configure Daily Reply Monitoring

Scan for replies daily, check each lead, and alert agents when a reply is detected.

  1. Set the schedule in Daily Reply Scan to control when reply checks run.
  2. Configure Retrieve Table Rows to pull active leads for reply checking.
  3. Set batch size in Iterate Items to manage volume.
  4. Open Fetch Gmail Messages and configure the mailbox and query for reply detection.
  5. Define the logic in Check Lead Reply to evaluate if a reply exists.
  6. Customize the alert in Alert Agent Reply, then map updates in Flag Lead Replied and Update Reply Status.

Iterate Items outputs to both Check Lead Reply and Fetch Gmail Messages in parallel.

Credential Required: Connect your Google credentials in Fetch Gmail Messages.

Credential Required: Connect your Telegram API credentials in Alert Agent Reply.

If Gmail results are empty, confirm the search query and that the mailbox has access to the thread IDs used in your lead table.

Step 6: Configure Second Follow-Up Email

Generate and send the second follow-up for leads who have not replied.

  1. Set the timing in Daily Followup Scan for follow-up processing.
  2. Configure Retrieve Followup Rows and Init Followup Data to prepare input for AI.
  3. Open AI Second Followup Email and define the follow-up prompt.
  4. Ensure Gemini Followup Model is connected as the language model and Followup JSON Parser as the output parser for AI Second Followup Email.
  5. Map outputs in Prepare Second Followup, then send with Dispatch Second Email.
  6. Update records in Modify Followup Records and notify in Notify Agent Followup Sent.

Credential Required: Connect your Google Gemini credentials in Gemini Followup Model.

Credential Required: Connect your SMTP credentials in Dispatch Second Email.

Credential Required: Connect your Telegram API credentials in Notify Agent Followup Sent.

Note: Followup JSON Parser is an AI tool sub-node; credentials should be added to the parent node Gemini Followup Model used by AI Second Followup Email.

Step 7: Configure Third Follow-Up and Completion Notifications

Run the third follow-up sequence and mark leads as complete.

  1. Set the schedule in Daily Second Followup Scan and load data with Retrieve Second Rows.
  2. Configure the timing logic in Check 24h Delay, then map fields in Init Third Followup.
  3. Open AI Third Followup Email and define the third follow-up prompt.
  4. Ensure Gemini Third Model is connected as the language model and Third JSON Parser as the output parser for AI Third Followup Email.
  5. Map outputs in Prepare Third Followup, then send with Dispatch Third Email.
  6. Update completion status in Update Records Status and notify in Notify Sequence Complete.

Credential Required: Connect your Google Gemini credentials in Gemini Third Model.

Credential Required: Connect your SMTP credentials in Dispatch Third Email.

Credential Required: Connect your Telegram API credentials in Notify Sequence Complete.

Note: Third JSON Parser is an AI tool sub-node; credentials should be added to the parent node Gemini Third Model used by AI Third Followup Email.

Step 8: Test and Activate Your Workflow

Validate the full sequence before enabling it for production.

  1. Manually execute Telegram Lead Intake by sending a test message from Telegram.
  2. Confirm that a new record is created in Add Table Record and that Dispatch Email sends an email.
  3. Trigger Daily Reply Scan and verify the workflow cycles through Retrieve Table Rows and Fetch Gmail Messages.
  4. Check that follow-up sequences run through Daily Followup Scan and Daily Second Followup Scan without errors.
  5. When everything is correct, switch the workflow to Active.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Gmail credentials can expire or require the right OAuth scopes. If replies aren’t detected, check the Gmail node authentication status in n8n and reconnect the account.
  • If you’re using Wait nodes or external timing logic, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Gemini prompts start generic unless you tighten them. Add your brand voice and a “do not sound salesy” instruction early, or you will be editing outputs forever.

Related Workflows

If you already store leads in a spreadsheet and want email creation to happen from there, Google Sheets to Gmail, personalized lead drafts ready pairs nicely with this workflow as a “prep step” before the sequence logic takes over.

For teams that need cleaner lead capture before follow-ups even start, JotForm + Telegram: get hot leads, ditch spam helps filter and route form submissions so your Telegram intake stays high-signal.

When you want a simpler version of the same outcome (send and track follow-ups in one place), Gmail + Google Sheets: follow ups sent, tracked is a good option, especially if AI personalization isn’t a requirement yet.

Need internal visibility while leads are moving? Google Sheets + Slack: leads routed and followed up is useful when sales and ops both want notifications and ownership without living in the same inbox.

Finally, if your biggest pain is drowning in inbound replies and you want them logged cleanly, Gmail + Google Sheets: inbox triage, logged clean can sit alongside this sequence workflow to keep response handling organized.


Quick reference:

Frequently Asked Questions

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

About an hour if your Telegram bot and Gmail login are ready.

Do I need coding skills to automate Telegram Gmail follow-ups?

No. You’ll mostly connect accounts and paste a Gemini API key. The “hard” part is deciding what you want the emails to sound like.

Is n8n free to use for this Telegram Gmail follow-ups 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 Gemini API usage costs, which are typically small for email-sized prompts.

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 follow-ups workflow for a different number of touches?

Yes, but keep it simple. You can add or remove follow-up steps by adjusting the scheduled follow-up checks and the “sequence number/status” fields stored in the data table. Most teams customize the timing (24 hours vs. 48), the tone per step (friendly vs. direct), and the notification channel (Telegram vs. Discord). The AI email composer and follow-up email nodes are the main places to tweak copy behavior.

Why is my Gmail connection failing in this workflow?

Usually it’s expired OAuth credentials or missing permissions. Reconnect the Gmail node in n8n, then confirm the account has access to the inbox you’re scanning. If you’re processing lots of leads, you can also hit Gmail rate limits, so narrowing the search query and scanning less frequently helps.

How many leads can this Telegram Gmail follow-ups automation handle?

Hundreds a week for most small teams, assuming your email account and n8n instance aren’t heavily loaded.

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

Often, yes. This workflow has multiple scheduled paths (reply scan, first follow-up scan, second follow-up scan) plus status logic, which is the kind of thing that gets pricey and fragile in simpler automation tools. n8n also gives you a self-hosted option, which means you aren’t paying per tiny step once volume grows. That said, Zapier or Make can be quicker for a basic “lead form → single email” setup. If you’re unsure, Talk to an automation expert and describe your lead volume and follow-up rules.

Set this up once, and your follow-up process stops living in your head. The workflow handles the repetitive nudges so you can focus on real conversations.

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.