RSS + Gmail: newsletter drafts ready to send

Writing a newsletter from “interesting articles” sounds simple until you’re stuck copying links, skimming long posts, and trying to make it all sound like you. Then you lose an hour. Again.

This is the kind of mess that hits marketers and content leads first, but founders sending updates and agency owners running client newsletters feel it too. With this RSS Gmail automation, new posts turn into ready-to-review Gmail drafts, so you publish consistently without living in tabs.

Below you’ll see exactly what the workflow does, what it replaces, and how much time it typically gives back once it’s running.

How This Automation Works

See how this solves the problem:

n8n Workflow Template: RSS + Gmail: newsletter drafts ready to send

Click to explore

flowchart LR

    subgraph sg0["RSS Feed Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "RSS Feed Trigger", pos: "b", h: 48 }
        n1@{ icon: "mdi:robot", form: "rounded", label: "Information Extractor", pos: "b", h: 48 }
        n2@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
        n3@{ icon: "mdi:robot", form: "rounded", label: "Message a model", pos: "b", h: 48 }
        n4@{ icon: "mdi:message-outline", form: "rounded", label: "Create a draft", pos: "b", h: 48 }
        n3 --> n4
        n0 --> n1
        n2 -.-> n1
        n1 --> n3
    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 n0 trigger
    class n1,n3 ai
    class n2 aiModel

The Challenge: Turning RSS reads into a finished newsletter

You find great articles in an RSS feed, but turning them into a newsletter draft is where things fall apart. First you open the post, then you hunt for the “real” takeaway, then you paste a quote, then you rewrite it because it sounds like a robot (or worse, like the author). Do that a few times and you’ve burned a chunk of your day without sending anything. The mental load is the sneaky part: you’re constantly re-deciding tone, structure, and what “good enough” means, which is why newsletters slip a day, then a week.

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

You keep re-reading the same long post just to extract a clean summary.
Copy-paste introduces mistakes, from broken links to missing context in the intro.
The writing sounds inconsistent because each draft starts from scratch.
By the time you finish formatting, you’re too tired to do the part that matters: the final edit and send.

The Fix: RSS-to-Gmail newsletter drafts generated automatically

This workflow watches an RSS feed on a schedule and turns new articles into newsletter-ready copy inside Gmail drafts. Every hour, it checks the feed (by default: Artificial Intelligence News). When it finds new items, it pulls out the headline, snippet, and full content, then sends that text to an AI “information extractor” to produce a clean summary (and it can translate, if you want a different language). Next, a second AI step rewrites that summary into newsletter-style prose using a consistent assistant voice (the workflow ships with a “Patrik” tone you can tweak). Finally, n8n creates a Gmail draft, so you review it like any email, make small edits, and send when ready.

The workflow starts with an hourly RSS check. Then OpenAI turns raw articles into structured, readable newsletter text. Gmail receives the finished draft so the last step is simply review-and-send.

What Changes: Before vs. After

What This Eliminates

Impact You’ll See

Manually opening each RSS item to figure out what it says.
Rewriting summaries by hand just to make them “newsletter-friendly”.
Re-deciding tone, formatting, and structure for every edition.
Pasting text into Gmail and cleaning up formatting line-by-line.

Most teams cut 1–2 hours of weekly newsletter prep down to about 20 minutes.
Your drafts sound consistent because the same prompt drives the voice.
Fewer link and copy mistakes since the workflow assembles content automatically.
You get a repeatable “draft pipeline” that scales beyond one person.
Editing becomes the main work, which is the good kind of work.

Real-World Impact

Say you publish a weekly newsletter with 5 articles. Manually, you might spend about 10 minutes per article to read, summarize, and rewrite, plus another 20 minutes formatting and polishing the email, so call it about 1.5 hours. With this workflow running hourly, the drafts are already waiting in Gmail: you’ll usually spend about 15–20 minutes reviewing, trimming, and adding your own intro. That’s roughly an hour back each week, without skipping quality.

Requirements

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Gmail to create and store email drafts
OpenAI for summaries and newsletter-style writing
OpenAI API key (get it from the OpenAI API dashboard)

Skill level: Beginner. You’ll connect accounts, adjust a prompt, and test a draft.

Need help implementing this? Talk to an automation expert (free 15-minute consultation).

The Workflow Flow

An hourly RSS check kicks things off. n8n polls the RSS feed URL you choose and pulls in any newly published items since the last run.

The article gets “cleaned” into a useful summary. The workflow extracts the title, snippet, and main content, then an AI extractor turns it into structured notes you can actually use. If you want translation, you set that here in the system prompt.

The summary becomes newsletter copy. A second AI step rewrites everything in a consistent voice (the included “Patrik” assistant tone is a starting point), and you can ask for headings, bullets, a short CTA, or a tighter format.

Gmail receives a draft you can edit like normal. The workflow creates the email draft in your connected Gmail account, so you review, tweak, and send when it fits your schedule.

You can easily modify the RSS source to a different publication based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the RSS Trigger

Set up the RSS trigger to poll the news feed and kick off the automation when new items appear.

Add the RSS Intake Trigger node to your workflow.
Set Feed URL to https://www.artificialintelligence-news.com/feed/.
Set the polling schedule to Every Hour in the trigger’s schedule options.

Step 2: Connect OpenAI for Language Processing

The workflow relies on OpenAI for extracting content details and drafting the newsletter text.

Open the LLM Chat Engine node and set the Model to gpt-4.1-mini.
Credential Required: Connect your openAiApi credentials in LLM Chat Engine.
Open the Compose Newsletter Draft node and confirm the Model is gpt-4.1-mini.
Credential Required: Connect your openAiApi credentials in Compose Newsletter Draft.

The LLM Chat Engine is connected as the language model for Content Detail Extractor. Add credentials to LLM Chat Engine, not the extractor.

Step 3: Set Up Content Extraction

Extract structured fields from each RSS item so the AI has clean inputs for the newsletter draft.

Add the Content Detail Extractor node and connect it to RSS Intake Trigger.
Set Text to =Snippet: {{ $json['content:encodedSnippet'] }} Title: {{ $json.title }} Content: {{ $json['content:encoded'] }}.
In System Prompt Template, use Your task is a get information from content snippet, and translate it in {your prefer} language. Keep it clear and short about what is in content and title..
Ensure the attributes include Snippet, Title, and Content with the provided descriptions.

⚠️ Common Pitfall: If the RSS feed doesn’t return content:encoded fields, the extractor will have empty inputs. Validate the RSS feed output in the trigger test run.

Step 4: Set Up AI Drafting

Create the newsletter draft using the extracted content, with a personalized assistant voice.

Connect Content Detail Extractor to Compose Newsletter Draft.
In Compose Newsletter Draft → Messages, set the system content to =Your task is get information about article, use assistant role named Patrik to give personalisation and create a newsletter content. Content si here: {{ $json.output.Content }}.
Set the assistant content to Here give your tone of voice! to define the voice guidance.

Step 5: Configure the Email Draft Output

Send the AI-generated newsletter content into Gmail as a draft message.

Add the Generate Email Draft node and connect it to Compose Newsletter Draft.
Credential Required: Connect your gmailOAuth2 credentials in Generate Email Draft.
Set Resource to draft and Email Type to html.
Set Subject to Newsletter.
Set Message to ={{ $json.message.content }}.

Step 6: Test and Activate Your Workflow

Verify the workflow runs end-to-end and then enable it for live operation.

Click Execute Workflow to run a manual test from RSS Intake Trigger.
Confirm Content Detail Extractor outputs structured fields and Compose Newsletter Draft returns a generated newsletter body.
Check Gmail to ensure Generate Email Draft created a new draft with the Newsletter subject and HTML content.
When satisfied, toggle Active to enable the workflow for hourly runs.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Watch Out For

Gmail credentials can expire or need specific permissions. If things break, check the Gmail node’s connected account status in n8n 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.
Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Common Questions

How quickly can I implement this RSS Gmail automation automation?

Usually about 30 minutes if your Gmail and OpenAI accounts are ready.

Can non-technical teams implement this RSS Gmail automation?

Yes. No coding required. You’ll connect Gmail, paste an API key, and tweak a couple prompts.

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 (often just a few cents per draft, depending on article length).

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.

How do I adapt this RSS Gmail automation solution to my specific challenges?

You can change the RSS Feed Trigger to any feed URL, then update the “Information Extractor” prompt to control language, length, and what to extract (highlights, key stats, quotes). Most teams also customize the “Compose Newsletter Draft” AI prompt to match their brand voice and preferred structure, like a short intro + bullets + one CTA. If you want HTML output, you can ask the model for HTML and have Gmail store that as the draft body.

Why is my Gmail connection failing in this workflow?

Usually it’s expired OAuth access or the wrong Google account connected. Reconnect Gmail in n8n and confirm the Gmail node is using the account you expect. If drafts are created sometimes but not always, you may also be hitting Google API limits or sending malformed content from the AI step (very long bodies can be finicky), so check the execution logs for the exact error message.

What’s the capacity of this RSS Gmail automation solution?

Practically, it handles as many new RSS items as your schedule and account limits allow.

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

Often, yes, especially once you care about prompt control and multi-step AI processing. This workflow uses multiple AI stages (extract, then rewrite), and n8n makes that kind of branching and data shaping straightforward without turning your automation into a fragile chain of mini-zaps. You can also self-host for unlimited executions, which matters when the RSS feed gets busy. Zapier or Make can still be a fine pick for very simple “RSS to email” forwarding, but they get awkward when you want consistent voice, translation, and draft creation in one place. Talk to an automation expert if you’re not sure which fits.

Once this is running, your newsletter starts as a draft, not a blank page. Honestly, that’s the difference between “we should send one” and “it’s already ready.”

RSS + Gmail: newsletter drafts ready to send

How This Automation Works

n8n Workflow Template: RSS + Gmail: newsletter drafts ready to send

The Challenge: Turning RSS reads into a finished newsletter