Mindvalley Stories
Case Study · AI Mastery

Daily email admin cut from two hours to 15 minutes with three linked automations

Three connected n8n workflows now sort email, extract tasks and file invoices at the press of a single button.

This builder was losing one to two hours a day to email admin. During the program they designed three connected n8n workflows, writing every custom code node together with AI. Now one button does the sorting, the filing and the follow-ups, and their notes show how much patient debugging a working system takes.

Yara van Leeuwen
A builder automating their own email, invoices and client records with n8n, Notion and AI.
The Automation Architect: Gmail, Drive, Notion and OpenAI workflow system

Before

Every day began with one to two hours of email admin. Three to five follow-ups slipped through each week. Each invoice took about 15 minutes to handle by hand, and client information lived in three separate places: Gmail, Drive and a spreadsheet.

“Daily email admin dropped from 1-2 hours to 10-15 minutes.”

In their own words

The turning point

They began working AI-first, using Claude and ChatGPT as architecture partners, code generators and debugging tools. They kept to a strict debugging routine: paste the full workflow JSON into Claude, describe what went wrong, make the smallest fix, test, repeat. Connecting Claude to Notion let it read their databases and prompts directly while they built.

“Debugging followed a strict protocol: paste full workflow JSON into Claude, describe unexpected behavior, implement the smallest fix, test, repeat.”

In their own words

After

They now run three production workflows and six connected Notion databases. One flow takes in email, saves attachments to Drive and links each message to their CRM. A second sorts email into ten categories and pulls out tasks with due dates. A third reads invoice PDFs, records them in the right database and files them by year and type.

What it lets people do

Email admin now takes 10 to 15 minutes a day, and missed follow-ups have dropped to zero. Invoices are handled in one click, and every client's information sits in a single Notion dashboard.

What they learned

Most of the bugs came from n8n losing track of which item belonged to which, so they learned to match data by key and stop trusting item order. They also learned to keep AI prompts in Notion, where they can be changed without touching the workflow, and to check data before it reaches an AI step.

“Build validation gates before AI nodes, not after.”

In their own words

See the work

The three n8n workflows: email intake, task extraction and invoice processing

The Automation Architect: Gmail, Drive, Notion and OpenAI workflow system was built during AI Mastery.

Read the full submission
CATEGORY 1: The Automation Architect Description: A multi-platform automation system spanning 3 interconnected n8n workflows across Gmail, Google Drive, Notion, and OpenAI. Flow 1 ingests emails, normalizes metadata, uploads attachments to Drive, creates structured Notion pages, links every email to the CRM, and labels processed messages. Flow 2 uses Notion AI to classify emails into 10 categories and extract tasks with due dates into a Notion task database. Flow 3 picks up invoice attachments, extracts text from PDFs, sends them to GPT-4.1-mini for structured data extraction, detects credit vs. debit by IBAN matching, creates invoice records in the correct database, and files PDFs in year/type folders on Drive. Custom JavaScript handles email parsing, address normalization, attachment filtering, duplicate detection, and dictionary-based CRM linking — all triggered by a single button press. Key Learnings: Item pairing in n8n is the #1 source of bugs — after any IF, Switch, or lookup node, assume indices are broken and always use dictionary-based matching by key. HTTP PATCH requests unlock what native Notion nodes can't, specifically updating relation properties after page creation. Binary data (attachments) must be uploaded to Drive immediately after parsing, before any code transformations, or the data is lost. Store AI prompts in a Notion database for runtime retrieval so you can iterate without touching the workflow. Build validation gates before AI nodes, not after. Methodology: AI-first development using Claude and ChatGPT as architecture partners, code generators, and debugging tools. All custom JavaScript nodes were written collaboratively with AI. Debugging followed a strict protocol: paste full workflow JSON into Claude, describe unexpected behavior, implement the smallest fix, test, repeat. Notion MCP integration allowed Claude to read databases and prompts directly during development. The system uses webhooks over scheduled triggers, batch processing (up to 25 emails per execution), and Notion AI properties instead of paid AI nodes for classification and task extraction. Results: Daily email admin dropped from 1-2 hours to 10-15 minutes. Missed follow-ups went from 3-5 per week to zero. Invoice processing went from 15 minutes manual per invoice to one-click automatic. Client data consolidated from three separate sources (Gmail, Drive, spreadsheet) into one Notion dashboard. 3 production workflows, 6 interconnected Notion databases, automatic Drive filing, Gmail label management, and full CRM auto-population — all running at near-zero marginal cost per email.

Written 15 February 2026 Submitted by the storyteller

Every story is written by a Mindvalley student or by someone our teachers have worked with. How we collect and check stories

More from AI Mastery

The Automation Architect: Gmail, Drive, Notion and OpenAI workflow system: a AI Mastery case study | Mindvalley Stories