Verify email content against Google Sheets and Gmail logs
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 7 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Gmail and Google Sheets.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Get many messages (Gmail): get many
- Extracting Preheader From HTML (HTML): parses or builds HTML
- Combine HTML, Expected Content and Preheader (Merge): merges the data from its input branches
- Load Expected Content (Google Sheets): uses Google Sheets
- Extract Actual Content and Results (Code): runs custom JavaScript code
- Log Content Checks to Excel (Google Sheets): append or update
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (6)
- Manual Trigger
n8n-nodes-base.manualTrigger - Gmail
n8n-nodes-base.gmail - HTML
n8n-nodes-base.html - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - Google Sheets
n8n-nodes-base.googleSheets
From the author
How it works - Input: Google Sheets provides “Expected Content” rows (one per block/section). - HTML Parse: A JS/HTML step extracts Actual Content from the email’s HTML (from Gmail or any provided HTML source). - Merge: Expected and Actual items are merged…