RSS + Gmail: a clean weekly tech brief in your inbox

Your “keep up with tech” system probably looks like this: 14 open tabs, three half-read newsletters, and a promise you’ll catch up on Friday. Then Friday arrives and you skip it anyway. RSS Gmail automation fixes that mess by turning scattered reading into one clean weekly brief.

This hits marketers who need trend awareness without doomscrolling. Founders feel it when they’re trying to spot product moves while juggling everything else. And if you run a small agency, you already know the pain of “staying current” quietly stealing billable hours.

This workflow collects articles daily from your favorite tech feeds, stores them for smart retrieval, and emails you a curated summary once a week. You’ll see what it does, why it works, and how to tailor it to your topics.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: RSS + Gmail: a clean weekly tech brief in your inbox

Click to explore

flowchart LR

    subgraph sg0["Get Articles Daily Flow"]
        direction LR
        n0@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split Out", pos: "b", h: 48 }
        n1@{ icon: "mdi:vector-polygon", form: "rounded", label: "Embeddings OpenAI", pos: "b", h: 48 }
        n2@{ icon: "mdi:robot", form: "rounded", label: "Default Data Loader", pos: "b", h: 48 }
        n3@{ icon: "mdi:robot", form: "rounded", label: "Recursive Character Text Spl..", pos: "b", h: 48 }
        n5@{ icon: "mdi:play-circle", form: "rounded", label: "Get Articles Daily", pos: "b", h: 48 }
        n11@{ icon: "mdi:memory", form: "rounded", label: "Store News Articles", pos: "b", h: 48 }
        n12@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Tech News RSS Feeds", pos: "b", h: 48 }
        n13@{ icon: "mdi:cog", form: "rounded", label: "Read RSS News Feeds", pos: "b", h: 48 }
        n16@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set and Normalize Fields", pos: "b", h: 48 }
        n0 --> n13
        n1 -.-> n11
        n5 --> n12
        n2 -.-> n11
        n13 --> n16
        n12 --> n0
        n16 --> n11
        n3 -.-> n2
    end

    subgraph sg1["Send Weekly Summary Flow"]
        direction LR
        n4@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
        n6@{ icon: "mdi:play-circle", form: "rounded", label: "Send Weekly Summary", pos: "b", h: 48 }
        n7@{ icon: "mdi:robot", form: "rounded", label: "News reader AI", pos: "b", h: 48 }
        n8@{ icon: "mdi:message-outline", form: "rounded", label: "Send Newsletter", 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/markdown.dark.svg' width='40' height='40' /></div><br/>Convert Response to an Email.."]
        n10@{ icon: "mdi:swap-vertical", form: "rounded", label: "Your topics of interest", pos: "b", h: 48 }
        n14@{ icon: "mdi:memory", form: "rounded", label: "Get News Articles", pos: "b", h: 48 }
        n15@{ icon: "mdi:vector-polygon", form: "rounded", label: "Embeddings OpenAI2", pos: "b", h: 48 }
        n7 --> n9
        n14 -.-> n7
        n4 -.-> n7
        n15 -.-> n14
        n6 --> n10
        n10 --> n7
        n9 --> n8
    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 n5,n6 trigger
    class n2,n3,n7 ai
    class n4 aiModel
    class n11,n14 ai
    class n1,n15 ai
    classDef customIcon fill:none,stroke:none
    class n9 customIcon

Why This Matters: Weekly tech catch-up turns into tab chaos

Trying to keep up with tech news manually sounds simple until you live it. You start with “I’ll just skim a few headlines,” then you’re deep in threads, bouncing between sources, and saving articles you never return to. The real cost isn’t only time. It’s the constant context-switching, plus the nagging feeling you’re missing something important. And when you finally do sit down to catch up, you’re staring at a pile of links with no prioritization, no personalization, and no clear “what matters this week.”

It adds up fast. Here’s where it usually breaks down.

You reread the same story in five places because each source phrases it differently.
Saved articles turn into an unread archive, which means you still feel behind.
Newsletters help, but they rarely match your interests, so you skim a lot of filler.
Important shifts get buried because nothing is ranking stories by relevance to you.

What You’ll Build: A personalized weekly tech newsletter from RSS

This automation runs in the background and does the unglamorous parts of “staying informed” for you. Each day, it pulls new items from multiple tech RSS feeds (think Wired, TechCrunch, The Verge, plus whatever you add). It cleans up the article fields so titles, summaries, and dates are consistent. Then it creates semantic embeddings with OpenAI and stores them in an in-memory vector store, which lets the workflow “remember” what it has seen in a way that’s searchable by meaning, not just keywords. Once a week, the workflow asks an AI agent to curate a short list based on your topics (for example: AI, games, gadgets) and a target number of stories (like 15). Finally, it formats the result into an email-friendly digest and sends it via Gmail.

Daily collection builds a library of what happened. Weekly curation turns that library into a single brief you’ll actually read. The output lands in your inbox as one clean email, ready to forward to a teammate or drop into Slack.

What You’re Building

What Gets Automated

What You’ll Achieve

Pulling fresh stories every day from multiple RSS feeds you choose.
Normalizing titles, summaries, and dates so the content is consistent.
Embedding and storing articles for semantic “memory” and relevance matching.
Generating a weekly curated summary and sending it through Gmail automatically.

Replace a weekly “catch-up session” (about 2 hours) with a 5-minute read.
See fewer repeats because the workflow curates across sources.
Get relevance to your interests instead of generic newsletter blurbs.
Share one digest with a team without forwarding five different emails.
Stay current without keeping tabs open all week.

Expected Results

Say you track 10 tech RSS feeds and you normally skim 20 stories a day. If you spend even 2 minutes per story, that’s about 40 minutes daily, plus another hour on the weekend trying to remember what mattered. With this workflow, daily collection is automatic, and weekly reading becomes one email with roughly 15 curated items. You’ll spend about 5 to 10 minutes reading the brief, not a whole evening “catching up.”

Before You Start

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
OpenAI for embeddings and weekly summarization.
Gmail to send the weekly brief to your inbox.
OpenAI API key (get it from the OpenAI API dashboard)

Skill level: Beginner. You’ll connect accounts, paste an API key, and edit a few “Set” fields for feeds and interests.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

A daily schedule fetches new stories. On a daily trigger, the workflow loads your list of RSS feeds and pulls the latest items from each source. If you want more or fewer sources, you’ll change that feed list.

Articles get cleaned up and stored for retrieval. Titles, summaries, and publish dates are normalized so downstream steps don’t break on inconsistent fields. Then OpenAI generates embeddings and the workflow stores them in memory, so the weekly curator can retrieve stories by meaning (for example, “AI chips” matches even if the headline uses different wording).

A weekly trigger runs the curation. Once a week, you define your interest topics and how many items you want. The AI agent queries the stored article library and compiles the most relevant, newsworthy picks, rather than dumping everything into one long list.

The summary is formatted and sent via Gmail. The curated brief is converted into a clean, email-friendly layout and dispatched to your inbox. You read it like any other newsletter, except you control the sources and the angle.

You can easily modify the RSS sources to match your industry, or change the weekly item count if you want a shorter read. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Schedule Triggers

Set up the daily and weekly schedules that drive article ingestion and newsletter curation.

Select Daily Article Trigger and confirm the schedule rule is enabled for daily execution.
Select Weekly Summary Trigger and set the rule to run weekly at hour 5 (already defined in the node).
Verify the execution flow: Daily Article Trigger → Define Tech RSS Feeds and Weekly Summary Trigger → Set Interest Topics.

Tip: If you want a specific timezone, set the workflow timezone in n8n settings so both triggers align with your locale.

Step 2: Connect the RSS Feed Inputs

Define the list of tech RSS sources and split them into individual feed URLs for retrieval.

Open Define Tech RSS Feeds and set the rss array to the provided list of URLs, e.g., https://www.engadget.com/rss.xml, https://feeds.arstechnica.com/arstechnica/index, https://www.theverge.com/rss/index.xml, https://www.wired.com/feed/rss, https://www.technologyreview.com/topnews.rss, https://techcrunch.com/feed/.
In Distribute Items, set Field To Split Out to rss to create one item per feed URL.
In Retrieve RSS Items, set URL to the expression {{ $json.rss }} so each split item is fetched.

⚠️ Common Pitfall: If any feed URL is invalid or blocked by SSL, Retrieve RSS Items may fail. Validate each feed URL in a browser before running.

Step 3: Normalize and Prepare Articles for Vector Storage

Standardize RSS fields, chunk content, and create documents for embedding and storage.

In Normalize Article Fields, map fields as expressions: title → {{ $json.title }}, content → {{ $json['content:encodedSnippet'] ?? $json.contentSnippet}}, date → {{ $json.isoDate}}, link → {{ $json.link }}.
Configure Recursive Text Chunker with Chunk Size set to 3000.
In Standard Data Loader, set JSON Data to # {{ $json.title }} {{ $json.content }} and JSON Mode to expressionData.
In Standard Data Loader metadata, set title to {{ $json.title }}, createDate to {{ $now.toISO() }}, publishDate to {{ $json.date }}, and link to {{ $json.link }}.

Tip: Consistent field mapping in Normalize Article Fields prevents missing summaries later when the AI curates results.

Step 4: Set Up Embeddings and Vector Storage

Encode articles into embeddings and store them for weekly retrieval.

In OpenAI Vector Encoder, connect credentials. Credential Required: Connect your openAiApi credentials.
In Persist News Vectors, set Mode to insert and Memory Key to news_store_key.
Confirm the data flow: Normalize Article Fields → Persist News Vectors with embeddings from OpenAI Vector Encoder via the AI embedding connection.

⚠️ Common Pitfall: If you skip the embedding connection from OpenAI Vector Encoder to Persist News Vectors, vectors won’t be stored and weekly summaries will be empty.

Step 5: Configure the AI Newsletter Curation

Define interests and connect the AI agent to the stored vector data for weekly summarization.

In Set Interest Topics, set Interests to eink/epaper devices, AI, Linux, open source, automation, no-code, low-code, productivity, quantum computing, quantum resistant crypto, groundbreaking innovation and Number of news items to include to 5.
In AI News Curator, keep Text as Summarize the most relevant tech news published in the past 7 days. Today is {{ $now }} and confirm Prompt Type is define.
In OpenAI Chat Engine, select model gpt-4o. Credential Required: Connect your openAiApi credentials.
Ensure Fetch Stored Articles is set to Mode retrieve-as-tool with Top K 20, Tool Name get_news, Memory Key news_store_key, and Tool Description Call this tool to get the latest news articles..
In Secondary Embedding Encoder, connect credentials. Credential Required: Connect your openAiApi credentials.

Tip: OpenAI Chat Engine is connected as the language model for AI News Curator—ensure credentials are added to OpenAI Chat Engine, not the agent node.

Step 6: Format and Send the Newsletter Email

Convert the AI output to HTML and dispatch the newsletter to your inbox.

In Format Summary for Email, set Mode to markdownToHtml and Markdown to {{ $json.output }}.
In Dispatch Newsletter Email, set Send To to [YOUR_EMAIL], Subject to Weekly tech newsletter, and Message to {{ $json.data }}.
Connect Gmail credentials. Credential Required: Connect your gmailOAuth2 credentials.

⚠️ Common Pitfall: If Dispatch Newsletter Email is missing valid Gmail OAuth permissions, the send action will fail even if the summary is generated.

Step 7: Test and Activate Your Workflow

Run a manual test to ensure articles are stored and a weekly summary is emailed correctly.

Click Execute Workflow and confirm Daily Article Trigger retrieves items through Retrieve RSS Items and stores vectors in Persist News Vectors.
Manually execute Weekly Summary Trigger and verify AI News Curator produces output that flows to Format Summary for Email and then Dispatch Newsletter Email.
Successful execution should result in an email with HTML-formatted summaries and links.
When satisfied, toggle the workflow to Active for production scheduling.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

OpenAI credentials can expire or be restricted by billing limits. If the workflow suddenly stops embedding or summarizing, check your OpenAI API key and usage limits first.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Gmail sending can fail if your Google account permissions change. Reconnect the Gmail credential in n8n and confirm the correct “From” account is selected.

Quick Answers

What’s the setup time for this RSS Gmail automation?

About 30 minutes if your feeds and accounts are ready.

Is coding required for this weekly tech brief automation?

No coding required. You’ll mostly connect accounts and edit your feed list, topics, and schedule.

Is n8n free to use for this RSS Gmail automation workflow?

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 OpenAI API costs, which are usually a few cents per run depending on how many articles you embed and summarize.

Where can I host n8n to run this automation?

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.

Can I modify this RSS Gmail automation workflow for different use cases?

Yes, and you should. Swap sources by editing the “Define Tech RSS Feeds” node, then adjust “Set Interest Topics” to match your niche (security, fintech, gaming, whatever). You can also change the weekly item count so the email is shorter, or rewrite the AI agent instructions to produce an exec summary instead of a newsletter-style digest. If you prefer chat delivery, replace the Gmail sending step with a Telegram message node.

Why is my Gmail connection failing in this workflow?

Usually it’s a revoked Google permission or an outdated credential inside n8n. Reconnect the Gmail account, then confirm the workflow is using the correct Gmail credential on the send step. If you recently changed your Google security settings, that can break previously working connections. Also check that you’re not hitting a sending limit if you’re testing repeatedly.

What volume can this RSS Gmail automation workflow process?

Plenty for a personal or small-team digest: dozens of feeds and hundreds of articles per week is typical.

Is this RSS Gmail automation better than using Zapier or Make?

For this kind of workflow, n8n is usually the better fit because you’re doing more than simple “A to B” syncing. You’re collecting daily, transforming text, storing embeddings, then querying that store weekly, which is real logic with multiple phases. Zapier and Make can do parts of it, but it often gets expensive or awkward when you add AI memory and branching. n8n also gives you a self-hosted option, which many teams prefer for higher volumes. If you want help choosing, Talk to an automation expert and get a quick recommendation.

Once this is running, your “staying current” habit stops fighting your calendar. One weekly email. The rest of the week is yours.

RSS + Gmail: a clean weekly tech brief in your inbox

How This Automation Works

n8n Workflow Template: RSS + Gmail: a clean weekly tech brief in your inbox

Why This Matters: Weekly tech catch-up turns into tab chaos