Gmail to Google Docs, Zoom meeting notes done for you
You leave a Zoom call with good momentum, then lose it in the recap. Someone has to dig up the email, skim the transcript, pull action items, write a summary, format it, and send it. It is tedious. And it happens after every single meeting.
This Zoom notes automation hits project managers hardest, but team leads and meeting coordinators feel it too. The outcome is simple: consistent meeting notes in Google Docs plus a clean email summary, without copying and pasting for about an hour.
Below you’ll see exactly what the workflow does, what you need to connect, and how to think about customizing the output so it matches your team’s style.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Gmail to Google Docs, Zoom meeting notes done for you
flowchart LR
subgraph sg0["Gmail 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/markdown.dark.svg' width='40' height='40' /></div><br/>Markdown"]
n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Edit Fields1", pos: "b", h: 48 }
n2@{ icon: "mdi:robot", form: "rounded", label: "Generate Summary", pos: "b", h: 48 }
n3@{ icon: "mdi:cog", form: "rounded", label: "Update a document", pos: "b", h: 48 }
n4@{ icon: "mdi:cog", form: "rounded", label: "Create a document", pos: "b", h: 48 }
n5@{ icon: "mdi:robot", form: "rounded", label: "DocFormat", pos: "b", h: 48 }
n6@{ icon: "mdi:cog", form: "rounded", label: "No Operation, do nothing", pos: "b", h: 48 }
n7["<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/markdown.dark.svg' width='40' height='40' /></div><br/>Apply Formatting"]
n8@{ icon: "mdi:play-circle", form: "rounded", label: "Gmail Trigger", pos: "b", h: 48 }
n9@{ icon: "mdi:message-outline", form: "rounded", label: "Mark a message as read", pos: "b", h: 48 }
n10@{ icon: "mdi:cog", form: "rounded", label: "No Operation, do nothing1", pos: "b", h: 48 }
n11@{ icon: "mdi:brain", form: "rounded", label: "gpt-4O", pos: "b", h: 48 }
n12@{ icon: "mdi:message-outline", form: "rounded", label: "Send Email", pos: "b", h: 48 }
n11 -.-> n2
n0 --> n1
n5 --> n4
n12 -.-> n2
n1 --> n2
n8 --> n0
n8 --> n9
n7 --> n5
n2 --> n7
n4 --> n3
n3 --> n6
n9 --> n10
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 n8 trigger
class n2,n5 ai
class n11 aiModel
classDef customIcon fill:none,stroke:none
class n0,n7 customIcon
Why This Matters: Zoom recaps are a hidden time sink
Most meetings don’t fail because the conversation was bad. They fail because the follow-up is inconsistent. One person writes a wall of text, another forgets decisions, and action items get buried in someone’s inbox. If you’re running multiple calls a week, the admin work becomes its own job: hunting the Zoom email in Gmail, pulling out the transcript, rewriting it into something readable, then reformatting it again so it works in Google Docs and in email.
It adds up fast. And the worst part is the context switching.
- Meeting summaries often take about 30–60 minutes per call when you include formatting and sending.
- Important decisions get paraphrased differently, which leads to “that’s not what we agreed” conversations later.
- Action items come out incomplete because nobody wants to comb through a long transcript twice.
- Google Docs becomes an afterthought, so searching past decisions turns into an inbox archaeology project.
What You’ll Build: Gmail-triggered Zoom summaries that land in Google Docs
This workflow watches your Gmail inbox for Zoom meeting notification emails and turns them into structured notes automatically. When a matching email arrives, n8n pulls the relevant fields, converts the content into a format the AI can reliably analyze, and then asks an AI Agent (using an OpenAI chat model) to extract what you actually care about: attendees, key discussion points, decisions, action items, and next steps. From there, the workflow generates two outputs in one run. You get Google Docs-friendly text saved as a document for your archive, and you get an email-safe HTML summary ready to send to participants, with consistent formatting every time.
The workflow starts with a Gmail trigger. It cleans and maps the email content, generates a meeting summary with the AI Agent, then renders it into two versions: one for Google Docs and one for email. Finally, it creates the Google Doc and dispatches the recap through Gmail so nobody waits on “I’ll send notes later.”
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you run 5 Zoom meetings a week. Manually, a recap often takes about 45 minutes: find the Zoom email, skim the transcript, write the summary, format it for email, then create a Google Doc. That’s roughly 4 hours a week. With this workflow, your time is closer to 5 minutes to review the generated summary (or just spot-check action items) while n8n does the rest in the background, so you get most of that time back and the notes don’t “mysteriously” slip to tomorrow.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Gmail for detecting Zoom emails and sending recaps.
- Google Docs (via Google Drive) to create and store meeting notes.
- OpenAI API key (get it from your OpenAI dashboard under API keys).
Skill level: Beginner. You will connect accounts, set one Gmail filter, and paste an API key.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
A Zoom email lands in Gmail. The workflow uses a Gmail trigger that’s filtered to Zoom meeting notification emails, so normal inbox traffic doesn’t start unnecessary runs.
The email content gets cleaned and mapped. n8n converts the raw email into a more consistent markdown-like format, then uses a “map fields” step to organize the useful parts (subject, date, transcript text, participants, and anything Zoom includes).
AI generates the meeting summary. An AI Agent powered by an OpenAI chat model reads the prepared content and produces a structured recap. This is where attendees, key points, decisions, action items, and next steps are pulled out in a predictable format.
Two outputs get produced and delivered. The workflow renders email-safe HTML for the recap email, and it also formats a Google Docs-compatible version, creates a new Google Doc, inserts the content, then sends the recap through Gmail. It also flags the triggering email as read so you don’t reprocess it later.
You can easily modify the Gmail search filter to match your Zoom setup, and adjust the summary format to match your internal template. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Email Inbox Trigger
Set up the workflow to watch your inbox for new meeting-related emails.
- Add the Email Inbox Trigger node.
- Credential Required: Connect your gmailOAuth2 credentials.
- Set Filters → Query to
subject: 'Meeting assets', 'Zoom', 'Meeting Assets'. - Set Filters → Read Status to
unread. - Set Poll Times to
everyMinute. - Confirm Simple is
falseto receive full message data.
Step 2: Connect Email Parsing and Field Mapping
Convert email content to Markdown and normalize fields for downstream AI processing.
- Add the Convert to Markdown node and set HTML to
={{ $json.html || $json.textAsHtml}}. - Connect Convert to Markdown to Map Email Fields.
- In Map Email Fields, add assignments with these values:
- Set subject to
={{ $json.subject }}and from to={{ $json.headers.from }}. - Set date to
={{ $json.date }}. - Set metadata['received-spf'] to
={{ $json.headers['received-spf'] }}. - Set metadata['delivered-to'] to
={{ $json.headers['delivered-to'] }}. - Set metadata['authentication-results'] to
={{ $json.headers['arc-authentication-results'] }}. - Set data to
={{ $json.data || $json.textPlain}}.
Step 3: Set Up AI Meeting Summarization
Use the AI agent to generate the meeting summary and trigger the email tool.
- Add the Create Meeting Summary node and set Text to
={{ $json.data }}. - Set Prompt Type to
defineto use the built-in system prompt. - Add the LLM Chat Engine node and connect it as the language model for Create Meeting Summary.
- Credential Required: Connect your openAiApi credentials to LLM Chat Engine.
- Configure LLM Chat Engine with Model
gpt-4oand Temperature0.3. - Ensure Dispatch Summary Email is connected as the AI tool for Create Meeting Summary.
- In Dispatch Summary Email, set Send To to
={{ $('Email Inbox Trigger').item.json.headers.to }}. - Set Subject to
={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Subject', ``, 'string') }}and Message to={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Message', ``, 'string') }}. - Credential Required: Connect your gmailOAuth2 credentials for the Dispatch Summary Email tool inside Create Meeting Summary (configure on the parent tool setup, not the sub-node).
Step 4: Format Output and Build the Google Doc
Transform the AI output into clean markup and store it in a Google Doc.
- Connect Create Meeting Summary to Render Output Markup and set HTML to
={{ $json.output }}. - Connect Render Output Markup to Docs Text Formatter.
- In Docs Text Formatter, keep JSON Output enabled (
true). - Credential Required: Connect your openAiApi credentials to Docs Text Formatter.
- Set the Model to
gpt-4.1and Temperature to0.3. - Connect Docs Text Formatter to Generate Doc File and set Title to
={{ $json.message.content.title }}. - Set Folder ID to
defaultin Generate Doc File. - Credential Required: Connect your googleDocsOAuth2Api credentials to Generate Doc File.
- Connect Generate Doc File to Insert Doc Content and set Document URL to
={{ $json.id }}. - In Insert Doc Content, set the insert Text to
={{ $('Docs Text Formatter').item.json.message.content.content }}. - Credential Required: Connect your googleDocsOAuth2Api credentials to Insert Doc Content.
Step 5: Configure Email Status Updates and Idle Nodes
Mark processed emails as read and keep the workflow paths aligned with idle steps.
- Note that Email Inbox Trigger outputs to both Convert to Markdown and Flag Email Read in parallel.
- In Flag Email Read, set Operation to
markAsReadand Message ID to={{ $json.id }}. - Credential Required: Connect your gmailOAuth2 credentials to Flag Email Read.
- Connect Flag Email Read to Idle Step 2 to complete the parallel branch.
- Keep Idle Step after Insert Doc Content as a placeholder for future extensions.
Step 6: Test and Activate Your Workflow
Validate the end-to-end flow before enabling it for production.
- Click Execute Workflow and send a test email that matches the Email Inbox Trigger query.
- Confirm the email is marked as read by Flag Email Read and that both parallel branches complete.
- Verify Create Meeting Summary produces content and triggers Dispatch Summary Email with a valid subject and message.
- Check that Generate Doc File creates a new Google Doc and Insert Doc Content populates it.
- When successful, toggle Active to enable the workflow for continuous operation.
Troubleshooting Tips
- Gmail credentials can expire or need specific permissions. If things break, check the Gmail node’s connected account and scopes in n8n’s Credentials first.
- If your Zoom email includes links or attachments (like transcript PDFs), extraction can vary by meeting. If summaries look thin, verify the workflow is pulling the transcript text you expect before it reaches the AI Agent.
- Default prompts in AI nodes are generic. Add your brand voice and your required headings (Decisions, Action Items, Next Steps) early or you will be tweaking every recap by hand.
Quick Answers
About 30 minutes if your Gmail, Google, and OpenAI accounts are ready.
No. You’ll connect accounts, set a Gmail filter, and adjust the summary template if you want.
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 costs (usually a few cents per meeting, depending on transcript 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 you should. Most teams tweak the Gmail trigger filter, then adjust the “Create Meeting Summary” AI Agent prompt to match their headings (like Risks, Blockers, or Customer Requests). You can also change the Google Docs steps (“Generate Doc File” and “Insert Doc Content”) to save into a specific folder, add a naming convention, or append to an existing running doc instead of creating a new one each time.
Usually it’s expired OAuth access or the wrong Google account connected. Reconnect the Gmail credential inside n8n, then confirm the trigger account and the “Dispatch Summary Email” account are the ones you actually use for meeting invites. If it still fails, check your Google security settings and make sure the workflow has permission to read inbox messages and send email.
Plenty for normal team meeting volume. On self-hosted n8n there’s no hard execution limit (it depends on your server), and on n8n Cloud the cap depends on your plan. Practically, this workflow handles one meeting email per run, so even a busy calendar of a few dozen meetings a week is fine as long as you’re comfortable with the OpenAI usage.
Often, yes. n8n is nicer for multi-step formatting (email-safe HTML plus Google Docs text), and it’s easier to keep the “logic” in one place when you start adding conditions like “only send recaps for client meetings” or “route to a different folder by project.” Self-hosting is a big deal too if you don’t want to think about task limits. Zapier or Make can still work if you only need a lightweight version, but complex summarization chains tend to get expensive or awkward. If you’re torn, Talk to an automation expert and we’ll map the simplest option.
Once this is live, your meeting notes stop depending on someone’s memory and free time. The workflow handles the repetitive cleanup and documentation, and you keep the momentum from the call.
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.
