Convert handwritten meeting notes to Google Docs with Gmail and easybits
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 6 nodes and runs on Gmail events. Along the way it connects Gmail, Google Docs and Extractor (community).
How it runs
Trigger: On Gmail events.
- easybits: Extract Meeting Notes (Easybits Extractor): uses Easybits Extractor
- Set: Build Doc Body (Edit Fields (Set)): sets or maps fields
- Google Docs: uses Google Docs
- Google Docs: update
- Gmail: reply
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @easybits/n8n-nodes-extractor is verified or supports 3.0 (used in easybits: Extract Meeting Notes).
- Also check Gmail Trigger below v1.4 runs as v1.4 (drafts skipped, max emails per poll).
Nodes used (5)
- Gmail Trigger
n8n-nodes-base.gmailTrigger - Easybits Extractor
@easybits/n8n-nodes-extractor.easybitsExtractor - Edit Fields (Set)
n8n-nodes-base.set - Google Docs
n8n-nodes-base.googleDocs - Gmail
n8n-nodes-base.gmail
From the author
Quick overview This workflow monitors a Gmail inbox for unread emails with image attachments, uses easybits Extractor to turn handwritten meeting notes into structured data, creates a Google Doc in a chosen Drive folder, inserts the formatted notes, and…