🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home n8n Workflow
January 22, 2026

RSS to Google Docs, drafts ready for review fast

Lisa Granqvist Partner Workflow Automation Expert

Your RSS feed is full of good ideas. The problem is turning those links into publishable drafts without losing half a day to copy-paste, rewriting, and chasing approvals.

This RSS Google Docs automation hits content managers first, honestly. But agency leads and in-house marketers feel it too, because the “draft” is never really the hard part. Review is.

This workflow pulls new RSS items every few hours, turns each into a structured GPT-4 draft, routes it through gotoHuman for approval, then creates a Google Doc and pings Slack. You’ll see how it works, what you need, and where teams typically tweak it.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: RSS to Google Docs, drafts ready for review fast

The Problem: RSS Ideas Don’t Become Publishable Drafts

Most teams are not short on topics. They’re short on time and consistency. You find an RSS item worth covering, open 6 tabs, summarize it, try to match your tone, add headings, add SEO details, and then send it out for review. That review comes back in a DM, an email thread, or a doc comment that nobody tracks. Meanwhile, the feed keeps moving and the backlog gets heavier. It’s a weird kind of stress because it feels “easy,” but it still eats your week.

It adds up fast. And the friction compounds once more than one person touches the content.

  • Creating one decent draft from an RSS article can burn about 1–2 hours once you include formatting, sources, and basic SEO structure.
  • Approvals get messy because the feedback is scattered across Slack, email, and comments, so you end up guessing what “approved” means.
  • Your tone drifts over time, especially when multiple writers are summarizing the same type of content in different ways.
  • When drafts aren’t centralized in Google Docs, it’s harder to delegate edits, reuse sections, or hand content off to another teammate.

The Solution: RSS → GPT-4 Draft → Human Approval → Google Doc + Slack

This workflow runs on a schedule (every 6 hours) and checks your RSS feed for new items. When it finds something new, it prepares the feed data, then uses GPT-4 to produce a structured blog draft instead of a rough summary. Next, it packages the draft into a clean “article payload” and sends it to gotoHuman so someone can review it with clear accept/reject decisions. If it’s approved, n8n creates a Google Doc and inserts the final content automatically. Then it notifies your Slack channel so the team can see what shipped and where it lives.

The workflow starts with the scheduled trigger and RSS retrieval. From there, AI creates the long-form draft, and gotoHuman keeps quality control in the loop. Finally, Google Docs becomes the single home for the approved version, and Slack tells everyone it’s ready.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you publish 5 RSS-inspired posts per week. Manually, you might spend about 90 minutes per post between extracting the key points, drafting, formatting, and sending it around for review, which is roughly 7–8 hours weekly. With this workflow, the “hands-on” part is closer to 10 minutes to skim the draft in gotoHuman and approve or reject it, then the Google Doc and Slack update happen automatically. You still get editorial control, but you stop paying the copy-paste tax.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • RSS feed URL for the content source you monitor
  • OpenAI (GPT-4) to generate structured blog drafts
  • gotoHuman for human-in-the-loop approval decisions
  • Google Docs to store approved drafts in one place
  • Slack to notify the team when drafts are ready
  • OpenAI API key (get it from the OpenAI dashboard)

Skill level: Intermediate. You’ll mostly be connecting accounts and editing prompts, but this workflow requires self-hosting because of the gotoHuman community node.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

Scheduled check for new content. A schedule trigger runs every 6 hours and kicks off the RSS Read step to fetch the newest items from your feed.

Feed data gets cleaned and shaped. A code step prepares the RSS fields you actually care about (title, description, keywords, and link), so the AI prompt stays consistent and doesn’t get junk input.

GPT-4 writes the draft. n8n calls the OpenAI chat model and composes a full blog post draft from the RSS item, then structures the output into a predictable “article payload” your team can review quickly.

Approval becomes a real gate. gotoHuman receives the draft and routes the result through an approval check. Approved drafts go to Google Docs and Slack. Rejected drafts get logged, so they don’t silently disappear.

You can easily modify the AI prompt to match your brand voice, or change the destination from Google Docs to another publishing tool based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Scheduled Trigger

Set the workflow to run automatically on a fixed schedule so it can fetch new RSS items without manual input.

  1. Add and open Scheduled Automation Trigger.
  2. Set the schedule rule to run every 6 hours (the node uses hoursInterval: 6).
  3. Connect Scheduled Automation Trigger to Retrieve RSS Items.

Step 2: Connect the RSS Data Source

Define the RSS feed URL to pull the latest articles into the workflow.

  1. Open Retrieve RSS Items.
  2. Set URL to https://example.com/rss-feed.xml.
  3. Ensure Retrieve RSS Items flows to Prepare Feed Data.

Step 3: Prepare Article Inputs and AI Generation

Normalize RSS fields, then generate a full article using the AI agent.

  1. Open Prepare Feed Data and keep the JavaScript as-is to extract topic, keywords, and other metadata.
  2. Open Compose Article with AI and confirm the prompt text uses RSS fields like {{ $json.original_title }} and {{ $json.original_description }}.
  3. Confirm that OpenAI Chat Engine is connected as the language model for Compose Article with AI.
  4. Ensure Compose Article with AI outputs to Shape Article Payload.

Credential Required: Connect your OpenAI credentials in OpenAI Chat Engine (the AI sub-node). Do not add credentials directly to Compose Article with AI.

Step 4: Structure the AI Output and Send for Review

Format the AI output into a clean payload and send it to a reviewer for approval.

  1. Open Shape Article Payload and keep the JavaScript that extracts the title, meta_description, and article_body.
  2. Open Submit for Human Review and verify the mapped fields use expressions like {{ $json.article_body }} and {{ $json.title }}.
  3. Set reviewTemplateID to your GoToHuman template ID (currently YOUR_GOTOHUMAN_TEMPLATE_ID).
  4. Ensure Submit for Human Review connects to Verify Approval Result.

Credential Required: Connect your GoToHuman credentials in Submit for Human Review.

Step 5: Configure Approval Routing and Google Docs Output

Route approved items to Google Docs creation and reject items to a log placeholder.

  1. Open Verify Approval Result and confirm the condition checks {{ $json.response }} equals approved.
  2. Verify the true path of Verify Approval Result goes to Generate Google Doc.
  3. Verify the false path of Verify Approval Result goes to Review Rejected Log (this is a placeholder node).
  4. Open Generate Google Doc and set Title to {{ $('Prepare Feed Data').item.json.original_title }}.
  5. If needed, specify driveId and folderId; they are currently empty (=).

Credential Required: Connect your Google Docs credentials in Generate Google Doc and Insert Article Content.

Tip: If you want rejected items to be stored, replace Review Rejected Log with a database or notification node.

Step 6: Insert Content and Send Slack Notification

Write the approved article into the Google Doc, then notify your team in Slack and mark completion.

  1. Open Insert Article Content and confirm Operation is set to update.
  2. Set Document URL to {{ $json.id }} so it uses the document created by Generate Google Doc.
  3. Keep the two insert actions, including {{ $('Shape Article Payload').item.json.article_body }} and the metadata block with reviewer and approval date.
  4. Open Post Slack Update and verify the message uses values like {{ $('Shape Article Payload').item.json.title }} and {{ $now.toLocaleString('en-US') }}.
  5. Set the Slack channel in Post Slack Update to your channel ID (currently YOUR_SLACK_CHANNEL_ID).
  6. Confirm the flow continues to Publication Complete.

Credential Required: Connect your Slack OAuth2 credentials in Post Slack Update.

Step 7: Test and Activate Your Workflow

Run a manual test to verify the full flow from RSS retrieval to document creation and Slack update.

  1. Click Execute Workflow and confirm Retrieve RSS Items returns at least one item.
  2. Check that Compose Article with AI outputs a complete article and that Shape Article Payload extracts a title and meta description.
  3. Verify that Submit for Human Review receives the data and returns an approval response.
  4. Confirm that approval routes to Generate Google Doc and Insert Article Content, then that Post Slack Update posts the notification.
  5. Once validated, toggle the workflow to Active for live scheduled execution.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Google Docs credentials can expire or need specific permissions. If things break, check the Google connection in n8n’s Credentials section 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.

Frequently Asked Questions

How long does it take to set up this RSS Google Docs automation?

Plan on about an hour if your accounts are ready.

Do I need coding skills to automate RSS to Google Docs drafts?

No. You’ll connect credentials and adjust a few fields and prompts.

Is n8n free to use for this RSS Google Docs 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 draft depending on 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.

Can I customize this RSS Google Docs workflow for WordPress publishing instead?

Yes, but you’ll swap the Google Docs creation steps for a WordPress publish step after approval. The easiest change is replacing “Generate Google Doc” and “Insert Article Content” with a WordPress node (or an HTTP Request to your CMS) while keeping the same gotoHuman approval gate. Common customizations include changing the AI prompt for your tone, adding a category based on RSS keywords, and routing “rejected” drafts to a backlog sheet. If you want a ready-made variant, the related workflows section includes an RSS-to-WordPress option.

Why is my Google Docs connection failing in this workflow?

Usually it’s expired Google credentials or the wrong Google account connected. Reconnect the Google Docs credential in n8n, then confirm the account can create files in the target Drive. If you’re inserting large drafts, occasional API limits can show up too, so retrying after a minute can help.

How many drafts can this RSS Google Docs automation handle?

It depends on your n8n plan and how often your RSS feed updates, but most small teams comfortably run dozens of drafts per week on a basic setup.

Is this RSS Google Docs automation better than using Zapier or Make?

For this use case, n8n is usually the better fit because you can keep the approval logic, branching, and self-hosting in one workflow without paying per tiny step. gotoHuman is also easier to treat as a true editorial gate inside n8n. Zapier or Make can still work if your flow is lightweight and you’re fine with simpler review handling. But once you care about consistent structure, approvals, and reliable routing, the limits show up quickly. Talk to an automation expert if you want a quick recommendation based on your volume and stack.

You end up with drafts that are actually reviewable, already in Google Docs, with a clear approval trail. Set it up once, then let the feed do its job.

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.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Launch login modal Launch register modal