🔓 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 + Gmail: turn messages into done tasks

Telegram + Gmail: turn messages into done tasks - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Telegram + Gmail: turn messages into done tasks - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Your inbox shouldn’t be a crime scene. But when requests arrive as Telegram messages, voice notes, screenshots, and random files, you end up hunting for context and forgetting follow-ups.

This Telegram Gmail automation hits founders and marketing managers hard, honestly. Client-facing consultants feel it too. The payoff is simple: messages become Gmail drafts and tracked tasks, so you stop losing “I’ll get back to you” moments.

Below, you’ll see how the workflow routes each message type, uses AI to interpret it, and turns the result into an email draft, a task, or a calendar action you can trust.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Telegram + Gmail: turn messages into done tasks

The Problem: Telegram “To-Dos” Don’t Turn Into Action

Telegram is fast, which is why work ends up there. A client sends a screenshot with “can you update this,” a teammate drops a voice note with three action items, and you tell yourself you’ll handle it after the next call. Then it’s gone. Not deleted, just buried under newer chats. You might forward it to email, or paste it into a task tool, or take a messy note. That context-switching is the real cost, and it’s where mistakes slip in.

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

  • You reread the same thread multiple times because the “real ask” is scattered across text, media, and replies.
  • Voice notes get postponed because transcribing them feels like extra work, so urgent items sit for a day.
  • Screenshots and photos contain important details, but they don’t translate cleanly into a task title or an email reply.
  • You create drafts and tasks inconsistently, which means nothing is searchable when you need it next week.

The Solution: Turn Telegram Inputs Into Gmail Drafts + Tracked Tasks

This workflow treats Telegram like your front door for work, not a second inbox. It starts the moment your Telegram bot receives a message, voice note, photo, or document. n8n routes that input by type, then processes it so it becomes “plain English” a system can act on. Voice gets transcribed. Images get analyzed and summarized. Text is kept intact. Everything is merged into a single, clean prompt for an AI manager agent that decides what should happen next: draft an email in Gmail, create or update a task in your task system, look up context from your memory base (Airtable), or even prepare a calendar action when scheduling is involved. Finally, the workflow replies in Telegram with a clear summary so you know what was created and where.

The workflow begins in Telegram, then normalizes each message into one consistent format. The AI manager agent uses that unified input to draft the right Gmail response and log the work as a task (Todoist or Google Sheets), using your saved context so it sounds like you. Then it reports back in chat, so you don’t wonder if anything happened.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you get 15 actionable Telegram messages in a typical day, and each one takes about 5 minutes to turn into “something real” (a draft, a task, a calendar note). That’s roughly 75 minutes of admin, plus the extra time spent searching later. With this workflow, you forward or send the message once, then wait for the reply in chat while it drafts the email and logs the task. Your hands-on time drops to about 10 minutes total for the day, mostly just quick review and send.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Telegram for collecting messages via a bot
  • Gmail to create drafts or send replies
  • Google Gemini credentials (create in Google AI Studio / Google Cloud)

Skill level: Intermediate. You’ll connect accounts, add API keys, and paste a few IDs (Airtable base, Sheets IDs, chatId) in the right places.

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

How It Works

A Telegram message kicks everything off. The Telegram Trigger listens for incoming text, voice notes, photos, and documents sent to your bot (including captions). You can also use the scheduled triggers for daily or weekly prompts if you want proactive follow-up routines.

Content gets normalized into one “clean” input. A Switch routes by message type, then n8n fetches files when needed. Voice messages are transcribed through Gemini. Photos are downloaded, converted, and analyzed so the workflow can extract what matters (like a list of edits, a name, an address, or a “please fix this section”).

The AI manager decides what to do next. After Merge combines the streams, the Manager Agent orchestrates specialized tools: it can pull and update memory in Airtable, create tasks in Todoist or Google Sheets, draft or reply in Gmail, and check or create calendar events in Google Calendar. This is where raw inputs become actual outputs.

You get the result back in Telegram. The final response is sent to chat, typically with a short summary of what was drafted, what was logged as a task, and any follow-up questions the agent needs answered before it can finish the job.

You can easily modify where tasks land (Todoist vs. a Google Sheet) 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 and scheduled triggers that kick off the assistant’s workflows.

  1. Open Telegram Update Trigger and ensure it listens for Updates set to message.
  2. Open Daily Schedule Trigger and set the cron Expression to 0 8 * * * for daily 8 AM runs.
  3. Open Weekly Schedule Trigger and set the cron Expression to 0 08 * * MON for weekly Monday 8 AM runs.
  4. Confirm that Daily Schedule Trigger connects to Compose Morning Prompt and Weekly Schedule Trigger connects to Compose Team Followup.
Tip: Check your n8n timezone settings to ensure the cron schedules for Daily Schedule Trigger and Weekly Schedule Trigger fire at the correct local time.

Step 2: Connect Telegram

Configure Telegram nodes for incoming content and outbound replies.

  1. In Telegram Update Trigger, add your Telegram bot credentials. Credential Required: Connect your Telegram credentials.
  2. In Telegram Message Sender, set Text to ={{ $json.output }} and Chat ID to =[YOUR_ID]. Credential Required: Connect your Telegram credentials.
  3. In Telegram File Fetch, set Resource to file and File ID to ={{ $json.message.voice.file_id }}. Credential Required: Connect your Telegram credentials.
  4. In Telegram Photo Fetch, set Resource to file and File ID to ={{ $json.message.photo[0].file_id }}. Credential Required: Connect your Telegram credentials.
⚠️ Common Pitfall: Replace all [YOUR_ID] placeholders with your actual Telegram Chat ID, otherwise Telegram Message Sender will fail to deliver responses.

Step 3: Set Up Content Routing and Input Mapping

Route incoming Telegram content and normalize it into a single combined stream.

  1. In Route by Content, configure rules to detect content types using these expressions: ={{ $json.message.document }}, ={{ $json.message.voice }}, ={{ $json.message.text }}, and ={{ $json.message.photo[0] }}.
  2. In Map Caption Text, set the text field to ={{ $('Telegram Update Trigger').item.json.message.caption }}.
  3. In Map Message Text, set the text field to ={{ $('Telegram Update Trigger').item.json.message.text }}.
  4. In Map Image Summary, set the text field to ={{ $json.content }}.
  5. In Combine Streams, set Number Inputs to 6 so all possible inputs can merge into the agent.

Execution flow note: Route by Content routes to Map Caption Text, Telegram File Fetch, Map Message Text, or Telegram Photo Fetch based on content type, then each mapping node feeds into Combine Streams.

Step 4: Set Up Media Processing and Transcription

Enable image understanding and audio transcription before the agent handles the message.

  1. In Binary Image Converter, set JavaScript Code to for (const item of $input.all()) { // Manually set the correct MIME type item.binary.data.mimeType = "image/jpeg"; // Convert binary to Base64 item.json.base64Image = `data:image/jpeg;base64,${item.binary.data.data.toString('base64')}`; } return $input.all(); .
  2. In Gemini Image Analysis, set Text to Analyse and Explain this image., Resource to image, Input Type to binary, and Operation to analyze. Credential Required: Connect your googlePalmApi credentials.
  3. In Audio Transcription, set Resource to audio and Input Type to binary. Credential Required: Connect your googlePalmApi credentials.

Step 5: Set Up the Primary Manager Agent

Configure the main AI agent that generates the final response back to Telegram.

  1. In Primary Manager Agent, set Text to ={{ $json.text }}, set Prompt Type to define, and enable Has Output Parser.
  2. Attach Session Window Memory as AI memory and set Session Key to =[YOUR_ID], Session ID Type to customKey, and Context Window Length to 10.
  3. Confirm Gemini Chat Model A is connected as the language model for Primary Manager Agent. Credential Required: Connect your googlePalmApi credentials.
⚠️ Common Pitfall: Gemini Chat Model B, Gemini Chat Model C, Gemini Chat Model D, Gemini Chat Model E, Gemini Chat Model F, and Gemini Chat Model G have no credentials configured—add googlePalmApi credentials to each of these model nodes before running the workflow.

Step 6: Connect Assistant Tools and Data Services

Wire up the supporting assistants (memory, email, tasks, research, projects, and calendar) and their integrations.

  1. For memory operations, connect Memory Base Tool with the Airtable tools (Airtable List Records, Airtable Create Personal, Airtable Search Personal, Airtable Upsert Personal, Airtable Remove Personal, Airtable Get Personal, Airtable Update Personal, Airtable Search Alerts, Airtable Get Alerts, Airtable Get Contacts, Airtable Search Contacts). These tools are AI sub-nodes—add Airtable credentials to Memory Base Tool, not the individual Airtable nodes. Credential Required: Connect your Airtable credentials.
  2. For task management, connect Task Manager Tool with Todoist tools (Todoist Close Task, Todoist Delete Task, Todoist Fetch Task, Todoist List Tasks, Todoist Move Task, Todoist Reopen Task, Todoist Update Task, Todoist Create Task). These are AI sub-nodes—add Todoist credentials to Task Manager Tool. Credential Required: Connect your Todoist credentials.
  3. For research, connect Research Assistant Tool with SERP Search Tool, Wikipedia Lookup, and Wolfram Query Tool. These are AI sub-nodes—add SerpAPI and Wolfram Alpha credentials to Research Assistant Tool as needed. Credential Required: Connect your SerpAPI and Wolfram Alpha credentials.
  4. For email automation, connect Email Assistant Tool with Gmail tools (Gmail Send Message, Gmail Create Draft, Gmail Reply Message, Gmail List Labels, Gmail Apply Labels, Gmail Mark Unread, Gmail Fetch Messages) and Google Sheets Lookup. These are AI sub-nodes—add Gmail and Google Sheets credentials to Email Assistant Tool. Credential Required: Connect your Gmail and Google Sheets credentials.
  5. For project management, connect Project Manager Tool with Google Sheets tools (Client Tasks Sheet, Company Tasks Sheet, Update Company Notes, Update Client Notes, Append Company Task, Append Client Task, Delete Company Task, Delete Client Task) and attach Project Memory Window with Session Key set to dasds. These are AI sub-nodes—add Google Sheets credentials to Project Manager Tool. Credential Required: Connect your Google Sheets credentials.
  6. For calendar actions, connect Calendar Assistant Tool with Calendar List Events, Calendar Remove Event, Calendar Get Event, Calendar Update Event, Calendar Availability Check, Calendar Create With Guests, and Calendar Create No Guests. These are AI sub-nodes—add Google Calendar credentials to Calendar Assistant Tool. Credential Required: Connect your Google Calendar credentials.
⚠️ Common Pitfall: The integration nodes listed above are AI tool sub-nodes. Credentials must be configured on their parent agents (Memory Base Tool, Task Manager Tool, Research Assistant Tool, Email Assistant Tool, Project Manager Tool, Calendar Assistant Tool), not on the individual tools.

Step 7: Configure Output and Scheduled Prompts

Finalize the assistant’s outputs and scheduled prompt content.

  1. In Compose Morning Prompt, set the text field to =Hey Main, Give me the schedules that I have today which includes, my todo, my calendar, my notifications in your memory that I need to take care today. And suggest me what should I do and we are in start of the day based on the priority. Also research for the latest tech and business news that happened yesterday that have a greatest potential to get an oppurtunity, should be specific and should be helpful and give me a comment about that too. Also with an oppurtunity that we can take use of because of this news. Also send me with the important emails that I have. Just the important ones. .
  2. In Compose Team Followup, set the text field to =Send a followup to the team individually with the tasks that are incomplete, the task they need to do or completed with a notes and a summary about this week. Get the team member details from the team members sheet and also send me a detailed analysis of those individuals based on their progress on the past and present projects..
  3. Verify that Combine Streams connects to Primary Manager Agent, and Primary Manager Agent connects to Telegram Message Sender.

Step 8: Test & Activate Your Workflow

Validate all triggers, AI responses, and integrations before turning on the workflow.

  1. Click Execute Workflow and send a test message, voice note, or photo to your Telegram bot to trigger Telegram Update Trigger.
  2. Confirm successful runs when Telegram Message Sender replies with an AI-generated response from Primary Manager Agent.
  3. Manually run Daily Schedule Trigger and Weekly Schedule Trigger to confirm scheduled prompt creation and merging into Combine Streams.
  4. Once confirmed, switch the workflow to Active to enable production execution.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Telegram bot settings are easy to half-finish. If replies stop, check the bot token and webhook setup, then confirm your chatId placeholders match the chat you’re testing in.
  • If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Gmail and Google Calendar permissions can be surprisingly strict. If drafts aren’t created, check the connected Google account in n8n credentials and confirm it has access to the right mailbox and calendars.

Related Workflows

If you want a broader “command center” version of this, Telegram + Google Gemini for tasks, email, calendar is a strong companion because it leans even harder into multi-tool orchestration from a single chat thread.

When the real bottleneck is booking calls (not writing emails), Telegram to Google Calendar, meetings handled in chat keeps scheduling out of your inbox entirely and turns “can you do Tuesday?” into an actual event.

If follow-ups are missing because you forget the time-sensitive stuff, Telegram + Google Calendar, reminders you wont miss pairs nicely with this workflow so tasks don’t just get created, they get remembered.

Need quick answers back to Telegram without the whole task-and-email layer? Telegram + Google Gemini: instant bot replies is useful for lighter-weight chat support and internal Q&A.

Finally, if your team prefers conversational scheduling for routine blocks, Telegram to Google Calendar, schedule by chat can sit alongside this setup so “schedule it” becomes as easy as sending a message.


Quick reference:

Frequently Asked Questions

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

About 30–60 minutes if your credentials and IDs are ready.

Do I need coding skills to automate Telegram Gmail tasks?

No. You’ll mostly connect accounts and paste a few IDs into the right nodes.

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 Google Gemini usage and any optional tools like SerpAPI or WolframAlpha if you enable research features.

Where can I host n8n to run this Telegram Gmail 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 “draft only, no sending”?

Yes, and it’s a common tweak. Keep the Gmail Create Draft tool enabled and disable (or remove) Gmail Send Message so the workflow never sends automatically. You can also have the Telegram reply include the draft link or subject line so you can review faster before hitting send.

Why is my Telegram connection failing in this workflow?

Most of the time it’s the basics: the bot token is wrong, the webhook isn’t set, or the chatId placeholder doesn’t match the conversation you’re testing. If you can receive messages but can’t send replies, check the Telegram Message Sender node credentials and confirm the bot is allowed to message that chat. Also make sure n8n can reach the internet if you’re self-hosting behind a firewall.

How many messages can this Telegram Gmail automation handle?

On n8n Cloud Starter, you can handle up to a few thousand executions per month, which is plenty for most small teams. If you self-host, there’s no execution cap; it mainly depends on your server and how heavy your AI steps are. In practice, the limiter is usually voice and image processing time, not n8n itself.

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

Often, yes, because this is not a simple “if message then email” recipe. You’re routing by message type, downloading files, transcribing audio, analyzing images, merging context, and then letting an agent choose between Gmail, tasks, calendar, and memory. n8n handles that kind of branching and tool-calling without turning into a giant, expensive chain of premium steps. Zapier or Make can still work if you only need a basic forward-to-email flow and don’t care about voice notes or screenshots. If you’re unsure, Talk to an automation expert and get a recommendation based on your volume and needs.

Once this is running, Telegram stops being a place where work disappears. You’ll get cleaner drafts, tracked tasks, and fewer “sorry, I missed that” follow-ups.

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.