Gmail to Google Sheets, AI news tracked for you
Your AI newsletter inbox is probably lying to you. Not on purpose, but because important links get buried, “I’ll read it later” becomes “never,” and the same stories keep resurfacing without any tracking.
This Gmail Sheets automation hits marketing leads hardest when they need quick trend angles. Agency owners want clean inputs for client recaps. And operators who run internal updates just need a system that doesn’t collapse after day three.
This workflow turns AlphaSignal emails into a structured Google Sheets log with Italian summaries and consistent categories. You will see how it works, what you need, and what to tweak so it matches your reporting style.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Gmail to Google Sheets, AI news tracked for you
flowchart LR
subgraph sg0["Newsletter Parse Age Flow"]
direction LR
n0@{ icon: "mdi:brain", form: "rounded", label: "Gemini Chat Engine", pos: "b", h: 48 }
n1@{ icon: "mdi:cog", form: "rounded", label: "Web Page Extractor", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Iterate Articles", pos: "b", h: 48 }
n3@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Dialogue Model", pos: "b", h: 48 }
n4@{ icon: "mdi:message-outline", form: "rounded", label: "Fetch Email Message", pos: "b", h: 48 }
n5["<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/>HTML to Markdown"]
n6@{ icon: "mdi:robot", form: "rounded", label: "Newsletter Parse Agent", 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/code.svg' width='40' height='40' /></div><br/>Validate JSON Output"]
n8@{ icon: "mdi:robot", form: "rounded", label: "Article Category Chain", pos: "b", h: 48 }
n9["<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/httprequest.dark.svg' width='40' height='40' /></div><br/>URL Shortener Call"]
n10@{ icon: "mdi:database", form: "rounded", label: "Append Sheet Record", pos: "b", h: 48 }
n1 -.-> n6
n4 --> n5
n9 --> n10
n6 --> n7
n7 --> n2
n2 --> n8
n3 -.-> n8
n5 --> n6
n10 --> n2
n8 --> n9
n0 -.-> n6
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 n6,n8 ai
class n0,n3 aiModel
class n10 database
class n9 api
class n7 code
classDef customIcon fill:none,stroke:none
class n5,n7,n9 customIcon
The Problem: AI News You Can’t Actually Use
AlphaSignal (and similar newsletters) are packed with useful links, but they show up as a wall of text at the exact wrong time: between calls, during deep work, or at the end of the day when your brain is done. So you skim, star it, maybe forward it… then it disappears into the same black hole as the rest. Next week you’re trying to remember, “Was that the LLM agent thing or the scraping thing?” and you end up re-Googling it anyway. Meanwhile, you’re missing patterns because nothing is stored in a way you can filter or summarize.
It adds up fast. Here’s where it breaks down in real life.
- Each newsletter forces you to manually split articles, copy links, and write notes, which quietly burns about 30 minutes a day.
- Summaries end up inconsistent because they depend on your mood and time, so weekly recaps become harder than they should be.
- Categorization is usually missing, which means you cannot quickly answer “What changed in AI automation this month?”
- When someone asks for sources, you scramble through email threads instead of sending one clean sheet.
The Solution: Turn Newsletters Into a Daily Intelligence Sheet
This workflow watches for a new AlphaSignal email in Gmail, then converts the newsletter into a format AI can reliably parse. A Gemini-powered agent reads the cleaned content, splits it into individual articles, and uses a scraping tool to visit each URL so the summary is based on the actual page, not just the snippet inside the email. After that, each article is handled one-by-one: OpenAI categorizes it into a predefined topic, the link is shortened via CleanURI, and the final record is appended into Google Sheets with the date, title, short link, Italian summary, and category. You end up with a growing dataset you can filter, chart, or turn into recaps without digging through your inbox.
The workflow starts when a newsletter arrives from [email protected]. From there, AI extracts articles and enriches them by scraping the source pages. Finally, Google Sheets becomes your searchable “AI news database” that keeps updating on its own.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say AlphaSignal includes about 10 articles in a daily email. Manually, you’d open the email, split the items, open links, write a quick summary, pick a category, then paste it into a sheet. Even at “only” 5 minutes per article, that’s about 50 minutes a day. With this workflow, you spend maybe 2 minutes checking the sheet (or zero, if you don’t need to). The processing runs in the background, then the log is ready when you are.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Gmail to receive and read AlphaSignal emails
- Google Sheets to store a clean daily log
- Google Gemini API key (get it from Google AI Studio)
- OpenAI API key (get it from the OpenAI API dashboard)
- ScrapeGraphAI API key (get it from your ScrapeGraphAI account)
Skill level: Intermediate. You’ll connect OAuth accounts, paste API keys, and test a run end-to-end.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A Gmail email arrives from AlphaSignal. n8n pulls the message content from your inbox using your Gmail connection, so it can work from the full body of the newsletter.
The email is cleaned for reliable parsing. The HTML body is converted into Markdown, which is easier for the AI agent to read without picking up layout noise, tracking pixels, and random formatting.
An AI agent splits the newsletter into articles and enriches them. Gemini identifies each individual item, then uses the ScrapeGraphAI tool to visit the linked page and produce a stronger Italian summary based on the source content.
Each article gets categorized, shortened, and logged. OpenAI assigns the best-fit category, CleanURI creates a short link, and Google Sheets gets a new row with date, title, URL, summary, and category.
You can easily modify the category list or the output language to match your team’s reporting style. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Trigger Type
This workflow starts with an email item ID that feeds Fetch Email Message. You need to add a trigger node to supply $json.id.
- Add a trigger node of your choice (for example, an email watch, manual trigger, or schedule) that outputs a message id field for Gmail.
- Ensure the trigger’s output JSON includes
id, because Fetch Email Message uses{{ $json.id }}for messageId. - Connect the trigger’s output to Fetch Email Message to match the execution flow.
⚠️ Common Pitfall: This workflow has no trigger node. Without adding one, Fetch Email Message will not receive a message ID and the workflow will fail.
Step 2: Connect Gmail and Convert HTML Content
This stage retrieves the email and converts its HTML body to Markdown for parsing.
- Open Fetch Email Message and set Operation to
get. - Set Message ID to
{{ $json.id }}. - Credential Required: Connect your gmailOAuth2 credentials in Fetch Email Message.
- In HTML to Markdown, set HTML to
{{ $json.textAsHtml }}and Destination Key tomd. - Confirm the connection Fetch Email Message → HTML to Markdown is in place.
Step 3: Set Up the Newsletter Parsing AI
The newsletter content is split into individual articles and summarized using AI tools.
- In Newsletter Parse Agent, set Text to
{{ $json.md }}and keep Prompt Type asdefine. - Verify the system instructions in Newsletter Parse Agent require JSON output with
title,link, andsummaryfields. - Gemini Chat Engine is connected as the language model for Newsletter Parse Agent — Credential Required: Connect your googlePalmApi credentials in Gemini Chat Engine.
- Web Page Extractor is connected as a tool for Newsletter Parse Agent — ensure ScrapeGraph AI credentials are added to Newsletter Parse Agent as the parent tool configuration.
- In Web Page Extractor, keep User Prompt set to
Entra nell'url di ogni articolo e fai il summary con i concetti principali in italiano dell'articolo setessoand Website URL set to{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Website_URL', `Inserisci l'url dell'articolo`, 'string') }}.
Tip: The parsing step expects valid JSON output. If the model adds extra text, the next node will fail.
Step 4: Validate JSON and Iterate Articles
The workflow cleans the AI output, parses JSON, and processes each article one by one.
- Keep the JavaScript in Validate JSON Output as provided to strip
```jsonwrappers and parse the output. - Confirm the connection Newsletter Parse Agent → Validate JSON Output → Iterate Articles.
- In Iterate Articles, leave default batch settings unless you want to throttle article processing.
Step 5: Categorize, Shorten URLs, and Write to Google Sheets
Each article is categorized, shortened, and appended to a spreadsheet.
- In Article Category Chain, keep Text set to
=Which category does it belong to? Title: {{ $json.title }} Summary: {{ $json.summary }}. - OpenAI Dialogue Model is connected as the language model for Article Category Chain — Credential Required: Connect your openAiApi credentials in OpenAI Dialogue Model.
- In URL Shortener Call, set URL to
https://cleanuri.com/api/v1/shorten, Method toPOST, and Content Type toform-urlencoded. - Set the body parameter url to
{{ $('Iterate Articles').item.json.link }}in URL Shortener Call. - In Append Sheet Record, set Operation to
append, and configure Document ID to[YOUR_ID]and Sheet Name togid=0(or your target sheet). - Map the columns in Append Sheet Record as follows: DATE
{{ $now.format('dd/LL/yyyy') }}, LINK{{ $json.result_url }}, TITLE{{ $('Iterate Articles').item.json.title }}, SUMMARY{{ $('Iterate Articles').item.json.summary }}, CATEGORY{{ $('Article Category Chain').item.json.text }}. - Credential Required: Connect your googleSheetsOAuth2Api credentials in Append Sheet Record.
Step 6: Test and Activate Your Workflow
Run a controlled test to validate the email parsing, AI output, and sheet append actions before going live.
- Manually run the trigger and verify Fetch Email Message returns a valid email with
textAsHtml. - Check HTML to Markdown outputs
mdand that Newsletter Parse Agent returns valid JSON. - Confirm Validate JSON Output emits one item per article and URL Shortener Call returns
result_url. - Verify Append Sheet Record appends a new row with the mapped fields and category text.
- When successful, toggle the workflow to Active for production use.
Common Gotchas
- Gmail OAuth credentials can expire or need specific permissions. If things break, check the n8n Credentials screen and confirm the Gmail scope still allows reading mailbox content.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About an hour if your accounts and API keys are ready.
No. You’ll mainly connect credentials and paste API keys. The only “code-like” piece is usually just checking the JSON validation node works with your newsletter format.
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 API usage for Gemini, OpenAI, and ScrapeGraphAI (usually a few dollars a month unless you process a lot).
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, but you’ll want to change it in the agent prompt where the summary language is defined, not only at the final “write to sheet” step. You can also swap the category labels to English while keeping summaries Italian, if that’s better for your team. Common customizations include adjusting the category list, changing the summary length, and adding a “priority” field for must-read items.
Usually it’s expired OAuth consent or the wrong Gmail account connected in n8n. Reconnect Gmail in the n8n Credentials area, then re-test the “Fetch Email Message” node. Also check that the workflow is filtering the correct sender ([email protected]), because a mismatch can look like a connection issue when it’s really “no email found.”
A typical daily newsletter volume (around 5–20 articles) is fine, and scaling mostly depends on your n8n plan and API rate limits. On n8n Cloud, higher tiers handle more monthly executions; self-hosting removes execution caps but your server still has limits. Practically, the slowest part is scraping and summarizing, so if you start processing several newsletters per day, you may want longer timeouts and a slightly bigger VPS.
Often, yes. This workflow uses an agent, web scraping, JSON validation, and looping per article, which is where no-code “simple zaps” tend to get brittle or expensive. n8n also lets you self-host, so you can run high volume without paying per step in the same way. Zapier or Make can still be fine if you only need a basic “email to sheet” log with no scraping and no categorization. If you’re unsure, Talk to an automation expert and get a quick recommendation.
Once this is running, your inbox stops being the archive. The sheet becomes the system, and you can finally spot trends without re-reading yesterday’s email.
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.
