Google Drive to Google Sheets, meeting notes done
Meeting recordings are everywhere, but the notes aren’t. Someone forgets to write them up, action items disappear into chat, and you end up re-listening to a 45-minute call just to find one decision.
Meeting notes automation matters most when you’re moving fast. A project manager trying to keep sprints on track feels it. A sales lead doing back-to-back discovery calls feels it too. Honestly, so does the agency owner who has to prove “what we agreed on” to three different stakeholders.
This n8n workflow takes meeting audio dropped into Google Drive, transcribes it, summarizes it, and appends a clean entry into Google Sheets. You’ll see how the flow 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: Google Drive to Google Sheets, meeting notes done
flowchart LR
subgraph sg0["Looking for uploading file Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Looking for uploading file", pos: "b", h: 48 }
n1@{ icon: "mdi:cog", form: "rounded", label: "Download file", pos: "b", h: 48 }
n2@{ icon: "mdi:robot", form: "rounded", label: "Transcribe the file", pos: "b", h: 48 }
n3@{ icon: "mdi:robot", form: "rounded", label: "Create summary", pos: "b", h: 48 }
n4@{ icon: "mdi:cog", form: "rounded", label: "Get date", pos: "b", h: 48 }
n5@{ icon: "mdi:cog", form: "rounded", label: "Format date", pos: "b", h: 48 }
n6@{ icon: "mdi:database", form: "rounded", label: "Save the summary", pos: "b", h: 48 }
n4 --> n5
n5 --> n6
n1 --> n2
n3 --> n4
n2 --> n3
n0 --> 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 n2,n3 ai
class n6 database
The Problem: Meeting Notes Don’t Survive Real Life
Teams don’t struggle because they “don’t care about documentation.” They struggle because documentation is always the last thing anyone has time for. The meeting ends, everyone jumps to the next call, and the recording sits in a folder with a filename like “Team Sync FINAL v3.” Then comes the follow-up question: “What did we decide?” and suddenly you’re scrubbing audio, guessing context, and trying to reconstruct action items from memory. It’s slow, and it’s risky.
The friction compounds. A missed task here and a misunderstood decision there turns into churn, rework, and awkward “I thought you owned that” messages.
- Someone has to manually take notes, which means the notes vary wildly in quality and detail.
- Action items get buried in chat threads and never become a searchable system of record.
- Listening back to one hour-long recording can easily steal another hour from your day.
- When new teammates join, they can’t catch up because the real decisions live inside old audio files.
The Solution: Google Drive → Sheets Meeting Summaries
This workflow watches a specific Google Drive folder for new audio uploads. The moment a recording lands there, n8n pulls down the file and sends it to OpenAI Whisper for transcription, turning the conversation into usable text. Next, ChatGPT takes that transcript and produces a structured summary focused on what your team actually needs: key points, decisions, and action items (with owners and deadlines when they’re mentioned). Finally, the workflow stamps the entry with today’s date and appends the summary to a Google Sheet, giving you one running archive you can search, filter, and share.
The flow starts with Google Drive detection and secure download. From there, AI handles transcription and summarization. The output lands in Google Sheets as a simple row you can reference later without hunting for the original recording.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you run 5 meetings a week and each one is 45 minutes. Without automation, you spend about 20 minutes writing notes, then another 15 minutes later when someone asks, “What did we decide?” That’s roughly 3 hours a week. With this workflow, you drop the audio into Google Drive (maybe 1 minute), wait for transcription and summarization, and the summary shows up in Google Sheets. The “admin time” drops to a few minutes for the whole week.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Drive for storing and triggering on new audio.
- Google Sheets to store a searchable summary log.
- OpenAI API key (get it from your OpenAI dashboard)
Skill level: Beginner. You’ll connect accounts, paste IDs for your Drive folder and Sheet, and run a quick test upload.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A new audio file appears in Google Drive. The workflow polls a specific folder (about once a minute) and looks for fresh uploads in common formats like MP3, WAV, M4A, or MP4.
The recording is retrieved for processing. n8n downloads the file so it can be sent to transcription, without you manually sharing links or moving files between tools.
AI turns audio into usable notes. OpenAI Whisper generates a transcript, then ChatGPT summarizes it using a prompt designed to pull out decisions, action items, owners, deadlines, and clean formatting.
The summary is logged to Google Sheets with the date. The workflow captures the current date, formats it consistently, and appends a new row so your archive grows automatically over time.
You can easily modify the summary format to match your internal template, or switch the destination from one master sheet to per-team sheets based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Google Drive Trigger
Set up the workflow to start when a new file is uploaded to a specific Google Drive folder.
- Add and open Monitor New Drive Uploads.
- Set Event to
fileCreated. - Set Trigger On to
specificFolderand choose your folder in Folder to Watch (e.g.,Meeting Folder). - Under Poll Times, keep the default
everyMinuteif you want near-real-time monitoring. - Credential Required: Connect your Google Drive credentials (this node has no credentials configured yet).
Step 2: Connect Google Drive and Download the File
Retrieve the uploaded audio file so it can be sent for transcription.
- Add and open Retrieve Drive File.
- Set Operation to
download. - Set File ID to
{{ $json.id }}to use the ID from Monitor New Drive Uploads. - Credential Required: Connect your Google Drive credentials (this node has no credentials configured yet).
Step 3: Set Up AI Transcription and Summary Generation
Use OpenAI to transcribe the audio file and generate a structured meeting summary.
- Add and open Audio Transcription Task.
- Set Resource to
audioand Operation totranscribe. - Credential Required: Connect your OpenAI credentials (this node has no credentials configured yet).
- Add and open Generate Meeting Summary.
- Set Model to
gpt-4.1. - In Messages, keep the system prompt and set the user content to
{{ $json.text }}to pass the transcript. - Credential Required: Connect your OpenAI credentials (this node has no credentials configured yet).
text field; otherwise Generate Meeting Summary will receive empty input.Step 4: Format the Date and Append to Google Sheets
Add a timestamp and store the summary in your meeting log spreadsheet.
- Add and open Capture Current Date, then set Output Field Name to
Date. - Add and open Format Date String.
- Set Operation to
formatDateand Date to{{ $json.Date }}. - Add and open Append Summary to Sheet.
- Set Operation to
append, select your Document (e.g.,Meeting Log) and Sheet Name (e.g.,Sheet1). - Map Date to
{{ $json.formattedDate }}and Meeting Summary to{{ $('Generate Meeting Summary').item.json.message.content }}. - Credential Required: Connect your Google Sheets credentials (this node has no credentials configured yet).
Execution Flow: Monitor New Drive Uploads → Retrieve Drive File → Audio Transcription Task → Generate Meeting Summary → Capture Current Date → Format Date String → Append Summary to Sheet.
Step 5: Test and Activate Your Workflow
Validate the end-to-end flow and enable it for production.
- Click Execute Workflow and upload a test audio file into the watched Drive folder.
- Verify that Audio Transcription Task outputs a transcript and Generate Meeting Summary returns formatted content.
- Check your Google Sheet to confirm a new row is appended with a formatted date and summary.
- If everything looks correct, toggle the workflow to Active to begin monitoring uploads automatically.
Common Gotchas
- Google Drive credentials can expire or need specific permissions. If things break, check the n8n Credentials page and re-auth the Google account 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
About 30 minutes if your Google and OpenAI accounts are ready.
No. You’ll mostly connect accounts and paste a couple of IDs (Drive folder and Sheet). If you can follow a checklist, you can run this.
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 API usage for Whisper + ChatGPT (often a few cents per meeting, depending on length).
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.
Yes, and it’s usually the best part. You’ll edit the prompt in the “Generate Meeting Summary” (OpenAI Chat Model) node to match your style, like adding a “Risks / Blockers” section or forcing bullet points. Many teams also add speaker labels or a “Decisions only” mode for leadership updates. If you want per-client summaries, you can route output into different sheets based on the Google Drive folder or filename.
Usually it’s an expired OAuth session or the Google account lacks access to the folder being watched. Reconnect Google Drive in n8n Credentials, then confirm the folder ID is correct and the Drive trigger can “see” new files. If you recently changed who owns the folder, that can break it too.
Most small teams can run dozens of recordings a day without issues, as long as your OpenAI limits and n8n execution plan can keep up.
Often, yes, because this is not just “move data from A to B.” You’re handling file retrieval, transcription, a structured AI prompt, and then writing clean output to Sheets, which usually needs branching and a bit of logic. n8n makes that easier to maintain, and self-hosting means you’re not paying per tiny step when volume grows. Zapier or Make can still work if you only need something simple and you value a very guided UI. If you’re unsure, Talk to an automation expert and we’ll help you pick the practical option.
Once this is running, your meeting audio stops being a graveyard and starts becoming an archive your team actually uses. The workflow handles the repetitive part, so you can focus on the work that comes next.
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.
