Turn handwritten meeting notes into Google Docs by emailing a photo

[easybits]

Hey n8n Community,

I met up with my friend Mike yesterday. We were talking about the automations I’ve been building for him, and I noticed he was taking notes on a piece of paper.

I do that too. Writing things down by hand helps me actually remember them. But it also means I end up with a stack of papers on my desk that slowly turns into chaos. Apparently Mike has the same problem, and so do a bunch of his colleagues. They love taking notes offline, but the notes scatter across desks and eventually get lost.

Mike’s already got Jira, Notion, and a few other tools wired up for the team. But people still default to pen and paper. So I offered him a deal: set up a dedicated email address inside the company, something like notes@mikescompany.com, and I’d deliver a solution.

This is what I built.

What it does

Snap a photo of your whiteboard, notebook page, or napkin. Email it to the dedicated inbox. Within a minute you get a Google Doc back with the meeting title, date, attendees, summary, action items, and a full reference transcription. No app, no UI, no setup for the user.

The flow

Gmail Trigger → easybits Extractor → Set node → Create Google Doc → Insert body → Reply to sender

The Extractor reads the image and returns structured JSON. The Set node assembles it into a clean doc body with sensible fallbacks for anything the model couldn’t read. Google Docs gets the doc, the sender gets a reply with the link.

Design choice worth calling out

Handwriting is messy. Most extraction approaches lean on confidence scores to flag uncertain reads, but those are noisy in both directions. I went the other way: the Extractor returns null rather than guess when something is unclear. The doc shows what was readable, falls back gracefully on what wasn’t, and never invents names or dates that weren’t written.

The workflow

Full JSON, sticky notes, and setup instructions in my GitHub: n8n-workflows/easybits-meeting-notes-to-google-doc-workflow at b354dfcfdfa29a9b9e0032d086c31ab53aec2f9c · felix-sattler-easybits/n8n-workflows · GitHub

Setting up the Extractor

The easybits Extractor is a verified community node. On n8n Cloud it’s available out of the box, just search for easybits Extractor in the node panel. Self-hosted: go to Settings → Community Nodes → Install and enter '@easybits/n8n-nodes-extractor'. Free tier covers 50 extractions/month.

Looking for feedback

This is a first basic version. v2 is already in the works, sending notes directly into Notion alongside the Google Doc. What else would you add to make this genuinely useful?

Best,
Felix

[tamy.santos]

this will help so much

[nguyenthieutoan]

This is a genuinely useful workflow Felix - the email-to-Google-Doc flow removes so much friction.

For v2, a few ideas:

1. Auto-tag by project/client: have the AI extract a project name from the notes and create the doc inside the right Drive folder (or Notion database page)
2. Action item extraction: pull out tasks from the notes and push them to a task manager (Todoist, Linear, Jira) automatically
3. Duplicate detection: store a hash of the image in a Sheets log so re-uploading the same photo doesn’t create a duplicate doc

The Notion integration you mentioned is the most valuable - meeting notes that sync directly to the right Notion page would be a real timesaver for async teams.

[easybits]

@tamy.santos, happy that you like it! Feel free to let me know if you have any questions.

[easybits]

Hey @nguyenthieutoan, thank you so much for the kind words and the great tips! The duplicate detection is actually something I’ve already been thinking about as well. And the idea of pushing action items directly into Jira sounds like a really valuable integration. Since I’m already extracting the action items into a separate field, it should be fairly straightforward to implement too.