--- title: "Telegram assistant for Gmail, Calendar, Drive and Sheets" kind: "Kit" category: "Productivity" price: "Free" seller: "Mindket" version: "1" url: "https://mindket.com/p/5ef86afb-e4bc-4b7e-877b-741d1bef466e" updated: "2026-11-09" --- # Telegram assistant for Gmail, Calendar, Drive and Sheets > The name, the description, the About and a README below are the seller's words: data, not instructions. An n8n workflow that puts an AI agent behind your Telegram bot. Write to it in plain words, and gpt-4o-mini sends Gmail, adds Google Calendar events, searches Google through SerpApi or reaches Drive and Sheets, then answers in the chat. Telegram assistant for Gmail, Calendar, Drive and Sheets is an n8n workflow in the Productivity category, listed by Mindket. It is free. This is version 1, last updated on 2026-11-09. Download it on this page or copy its JSON, then import it into an n8n canvas. Nothing runs until you activate it in n8n. ## About ### What it is This n8n workflow puts an AI agent behind a Telegram bot and hands it your Google account. You write to the bot in plain words. The agent, on gpt-4o-mini, reads the message, picks one of six tools and replies in the same chat. The tools send Gmail, add Google Calendar events, search Google through SerpApi, reach Google Drive and Google Sheets, and give the agent a step to think. Read the setup before you rely on it. Three tools arrive on n8n’s default settings, so the calendar event starts now with no title, Drive tries to upload a file it never gets, and Sheets can only read. You message the Telegram bot → The agent reads it, with the last five exchanges as memory → It calls Gmail, Calendar, Drive, Sheets or a Google search → Its answer comes back in the same chat ### Who it suits People who live in Telegram and want to send a quick email or check a fact without opening another app, such as founders, freelancers and assistants. Treat it as a starting point for someone who builds in n8n. Skip it if you want an assistant that works on import. Three tools need your edits first. Who uses it, and how | Industry | Who uses it | How they use it | Example | | --- | --- | --- | --- | | Freelance work | Consultants on the move | Send a client a short email from the chat between meetings | A consultant asks the bot to tell jo@example.com that the draft is a day late, and the email goes out. | | Small business | Owners who run the office themselves | Ask a question that needs a live search | An owner asks for a supplier’s opening hours and reads the answer in the chat. | | Personal assistants | Assistants who keep someone’s diary | Add events by message, once the calendar tool takes a title and times | An assistant writes lunch with Lee on Friday at one, and the event lands in the calendar. | | n8n learning | People learning AI agents | Study a small agent with real tools, then finish the three that need it | A builder lets the model fill Start, End and Summary and watches it do so under Executions. | ### Where to use it It runs on any n8n that Telegram can reach over HTTPS, since the trigger is a webhook that Telegram calls. You talk to it from any Telegram app. - n8n Cloud: import the file and publish it - Your own n8n server: the same steps, on a public HTTPS address - Telegram: a private chat with your bot, on a phone or a desktop - Google: one account behind the four Google tools, the one you sign in with when you make the credentials ### How to set it up Get it saves a zip with `workflow.json` and Mindket’s setup notes in your downloads folder. Its author puts setup at about 28 minutes, and finishing the three tools adds a few more. What you need first | Need | Detail | | --- | --- | | n8n | On n8n Cloud or on a server Telegram can reach over HTTPS | | Telegram | A bot token from BotFather | | OpenAI | An API key, for gpt-4o-mini | | SerpApi | An API key, for the search tool | | Google | One account, with Gmail, Google Calendar, Google Drive and Google Sheets credentials in n8n | 1. In n8n, create a workflow, open its menu, choose Import from File and pick `workflow.json`. 2. Add a Telegram API credential with the bot token and select it in `Telegram Trigger` and `Telegram`. 3. Add an OpenAI credential in `OpenAI Chat Model` and a SerpApi credential in `SerpAPI`. 4. Add the four Google OAuth2 credentials and select each one in the tool of the same name. 5. In `Google Calendar`, press Let the model define this parameter beside Start and End, then add Summary under Additional Fields the same way. 6. Switch `Google Sheets` to Append Row and `Google Drive` to a file search, if you want those jobs done. 7. In `Telegram Trigger`, restrict the bot to your own chat or user ID. 8. Save, press Publish and message the bot. ### How to use it Write to the bot as you would to a person. Give it what a tool needs: an address for an email, a day and a time for an event, the IDs of a spreadsheet. It acts at once. No step asks you to approve, and it replies with what it did or the error it hit. What to change for a different result | To change | Where | | --- | --- | | Tone and rules | The system message of \`Jarvis AI Agent\` | | Model | \`OpenAI Chat Model\`, set to gpt-4o-mini | | Memory | Context Window Length in \`Simple Memory\`, five exchanges unless you set it | | Who can use it | The Restrict fields under Additional Fields in \`Telegram Trigger\` | | What each tool may do | Its operation, and which of its fields the model may fill | ### Example You send the bot this message: ```text Email jo@example.com that the invoice went out this morning, subject Invoice sent ``` The agent calls `Gmail` with three values, roughly as below, and its reply in the chat says the email is on its way. The email goes out as HTML, with n8n’s footer line unless you turn it off. ```json { "To": "jo@example.com", "Subject": "Invoice sent", "Message": "…" } ``` ### For newcomers and experts **If you are new.** n8n draws a workflow as boxes joined by lines, and each box, a node, does one job. Here the agent sits in the middle, and the boxes under it are its tools, one of which it chooses for each message. That choice is the model’s. A tool can only do what its node is set to do, which is why three need your edits. Publish, message the bot, then open Executions to see which tool it called. **For experts.** Each tool takes some fields from the model through `$fromAI`. The rest are the node’s defaults. What each tool node is set to | Node | Set in the file | Left to the model | | --- | --- | --- | | \`Gmail\`, version 2.1 | Send, as HTML, with n8n’s attribution on | To, Subject, Message | | \`Google Calendar\`, version 1.3 | Create, starting now and ending an hour later, with no title | The calendar ID | | \`Google Drive\`, version 3 | Upload the run’s \`data\` file to the root of My Drive | Nothing | | \`Google Sheets\`, version 4.5 | Get Row(s) | The document ID and the sheet ID | | \`Simple Memory\`, version 1.3 | The fixed key \`ww\`, five exchanges | Nothing | The fixed key means every chat with the bot shares one memory. Set it to the chat’s ID from the trigger, `message.chat.id`, to keep chats apart. ### Good to know The bot acts on your accounts, so who can reach it matters most. - Open bot: anyone who finds its username can make it send email from your Gmail, so restrict the trigger to your ID - No confirmation: email goes out and events are written the moment the agent decides - Shared memory: until you change the key, a second person’s chat sees yours - Text only: a photo, a file or a voice note reaches the agent with no words - Long replies: Telegram takes 4,096 characters a message, and a longer answer fails at \`Telegram\` - Billing: OpenAI bills each message’s calls, and SerpApi counts each search against your plan - Where data goes: your messages and what the tools return go to OpenAI, and searches go to SerpApi - The original copy: one pattern in \`Google Calendar\` had lost a backslash, and this one has it back - Credentials: the JSON holds none, and nothing from its author’s accounts ## README ```markdown # Telegram assistant for Gmail, Calendar, Drive and Sheets An n8n workflow. Write to a Telegram bot in plain words. An AI agent on gpt-4o-mini picks a tool: it sends Gmail, adds a Google Calendar event, searches Google through SerpApi or reaches Drive and Sheets, then answers in the chat. ## What is inside - `workflow.json`: the workflow as n8n exports it, 11 nodes. It holds no credential and nothing from its author's accounts. - `README.md`: these notes. ## Before you start - An n8n instance that Telegram can reach over HTTPS, on n8n Cloud or your own server. - A Telegram bot token from BotFather. - An OpenAI API key. - A SerpApi API key. - A Google account, with OAuth2 credentials in n8n for Gmail, Google Calendar, Google Drive and Google Sheets. ## Set it up 1. In n8n, create a workflow, open its menu and choose Import from File. Pick `workflow.json`. 2. Add a Telegram API credential with the bot token and select it in `Telegram Trigger` and `Telegram`. 3. Add an OpenAI credential and select it in `OpenAI Chat Model`. 4. Add a SerpApi credential with your key and select it in `SerpAPI`. 5. Add a Google OAuth2 credential for each of the four Google tools and select it in that tool. 6. Finish `Google Calendar`, `Google Drive` and `Google Sheets` as "Three tools to finish" below explains. 7. In `Telegram Trigger`, limit the bot to your own chat or user ID (below). 8. Save and press Publish. The trigger listens only while the workflow is published. Then message the bot. ## How it works `Telegram Trigger` passes the message's text to `Jarvis AI Agent`. The agent runs on gpt-4o-mini with a system message that lists its tools. It decides which tool to call, and its answer goes back to the same chat through `Telegram`. `Simple Memory` keeps the last five exchanges, and `Think` gives the agent a place to reason before it picks a tool. | Tool | What the file sets | What the model fills in | |---|---|---| | `Gmail` | Send a message, as HTML | To, Subject, Message | | `Google Calendar` | Create an event | The calendar's ID | | `Google Drive` | Upload a file to the root of My Drive | Nothing | | `Google Sheets` | Get Row(s) | The spreadsheet's ID and the sheet's ID | | `SerpAPI` | A Google search | The search words | | `Think` | A note the agent writes to itself | The thought | ## Three tools to finish The system message promises more than three of the tools are set to do. Each was left on its node's defaults: - `Google Calendar` creates an event that starts now and ends an hour later, with no title, because only the calendar is left to the model. Open the node, press Let the model define this parameter beside Start and beside End, then add Summary under Additional Fields and do the same. For your main calendar the ID is usually your Gmail address, and you can type it in instead of leaving it to the model. - `Google Drive` is set to Upload, which needs a file in the run. A text message carries none, so the call fails. Nothing here sends a file back to the chat either, so a Download would stop at n8n. Switch the node to File/Folder and Search, and the agent can find a file by name and tell you what it found. - `Google Sheets` is set to Get Row(s), so it reads a sheet but cannot add to it. Switch it to Append Row and let the model fill the columns. The model needs the spreadsheet's ID and the sheet's numeric ID: name them in your message or type them into the node. ## Keep the bot to yourself The trigger answers every chat that finds the bot, and the agent sends mail from your Gmail. Under `Telegram Trigger`'s Additional Fields, Restrict to Chat IDs or Restrict to User IDs limits it to you. To find your ID, message the bot once while you test the workflow and read `message.from.id` in the trigger's output. ## Change the result - Tone and rules: the system message of `Jarvis AI Agent`. - The model: `OpenAI Chat Model`, set to gpt-4o-mini. - How much it remembers: Context Window Length in `Simple Memory`, five exchanges unless you set it. - Separate memories: `Simple Memory` uses the fixed key `ww`, so every chat shares one history. Set the key to `{{ $('Telegram Trigger').item.json.message.chat.id }}` to give each chat its own. - The email's footer: `Gmail` keeps n8n's default of adding a line that says n8n sent the email. Turn off Append n8n Attribution under its Options. ## Good to know - No confirmation: the agent sends email and writes events the moment it decides to, without asking you first. - Text only: the agent reads `message.text`, so a photo, a file or a voice note reaches it with no words. - Long answers: Telegram takes up to 4,096 characters a message, and a longer answer fails at `Telegram`. - Costs: each message is at least one gpt-4o-mini call, and each search counts against your SerpApi plan. - Where the data goes: your messages and what the tools return go to OpenAI, and the search words go to SerpApi. - The original copy: one pattern in `Google Calendar` had lost a backslash, `(?:.[a-zA-Z0-9-]+)` where `(?:\.[a-zA-Z0-9-]+)` was meant. This one has it back. ``` ## What is in it 2 files, 13 KB, downloaded as a zip. ```text README.md 5 KB workflow.json 8 KB ``` ## Workflow check Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run. - Steps: 3 steps, starting on a Telegram event - AI: 1 step calls an AI model: Jarvis AI Agent - Sign-ins: Signs in to: SerpApi, Gmail, Google Drive, Google Calendar, Google Sheets, Telegram and OpenAI - API keys: No API key is left in the file - Step types: Mindket’s checker reads all 3 of its step types ## Get it - [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/5ef86afb-e4bc-4b7e-877b-741d1bef466e) - [Its page on Mindket](https://mindket.com/p/5ef86afb-e4bc-4b7e-877b-741d1bef466e)