RSS to Slack, daily summaries your team will read
Your Slack gets flooded with links, but nobody clicks them. You skim headlines, miss the good stuff, and still spend about an hour a day trying to keep up.
This is where RSS Slack summaries help. Marketing managers feel it when content ideas get lost in noise, founders feel it when “research” turns into doomscrolling, and ops leads feel it when nobody shares what they’re learning.
This workflow pulls articles from your RSS feeds, summarizes the full pages with AI, and posts a clean daily digest to Slack (with optional logging to Google Sheets). You’ll see how it works, what you need, and where teams usually tweak it.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: RSS to Slack, daily summaries your team will read
flowchart LR
subgraph sg0["Schedule Flow"]
direction LR
n0["<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/slack.svg' width='40' height='40' /></div><br/>Send a message"]
n1@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
n2@{ icon: "mdi:cog", form: "rounded", label: "RSS Read", pos: "b", h: 48 }
n3@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items", pos: "b", h: 48 }
n4@{ icon: "mdi:swap-vertical", form: "rounded", label: "Config", 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/code.svg' width='40' height='40' /></div><br/>Convert to loop items"]
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/>Filter Rss Feeds"]
n13@{ icon: "mdi:cog", form: "rounded", label: "Call Sub-workflow", pos: "b", h: 48 }
n14@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Is not empty", pos: "b", h: 48 }
n4 --> n5
n2 --> n7
n14 --> n13
n14 --> n3
n0 --> n3
n3 --> n2
n7 --> n14
n1 --> n4
n13 --> n0
n5 --> n3
end
subgraph sg1["When Executed by Another Workflow Flow"]
direction LR
n6@{ icon: "mdi:play-circle", form: "rounded", label: "When Executed by Another Wor..", pos: "b", h: 48 }
n8@{ icon: "mdi:web", form: "rounded", label: "HttpRequestTool", pos: "b", h: 48 }
n9@{ icon: "mdi:robot", form: "rounded", label: "AI Agent (Access URL)", pos: "b", h: 48 }
n10@{ icon: "mdi:brain", form: "rounded", label: "Google Gemini Chat Model", pos: "b", h: 48 }
n11["<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/>Format Request"]
n12["<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/>Format Response"]
n11 --> n9
n8 -.-> n9
n9 --> n12
n10 -.-> n9
n6 --> n11
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 n1,n6 trigger
class n9 ai
class n10 aiModel
class n14 decision
class n8 api
class n5,n7,n11,n12 code
classDef customIcon fill:none,stroke:none
class n0,n5,n7,n11,n12 customIcon
The Problem: RSS Turns Into Link Spam (Fast)
RSS sounds like the perfect solution until you actually use it with a team. Feeds publish constantly, titles are vague, and the snippet is often useless. So you click through, scroll, hunt for the key point, then paste a link into Slack with a half-baked “seems interesting.” Multiply that by a few feeds and a busy week. Suddenly you’ve created a new job: part-time internet librarian. Worse, the team learns to ignore the channel because it never feels digestible.
It’s not one big failure. It’s lots of small frictions stacked on top of each other.
- RSS previews rarely include the real substance, which means you waste time opening every source page.
- Most Slack link drops have no context, so teammates don’t know what’s worth reading.
- Important themes get buried because there’s no daily rhythm or consistent format.
- When someone asks “what are we seeing lately?” you end up re-reading yesterday’s posts and guessing.
The Solution: Daily AI Summaries Sent to Slack
This n8n workflow fetches your chosen RSS feeds on a daily schedule (or via a webhook trigger if you want more control). When it finds new items, it doesn’t rely on the short RSS excerpt. Instead, it visits the source links, pulls the full article content, and asks an AI agent to summarize what actually matters. Then it posts those summaries into Slack in a consistent digest format, so your team can scan quickly and decide what’s worth a deeper read. If you want an audit trail, it can also log the items and summaries into Google Sheets for later searching and trend tracking.
The workflow starts with RSS reads and filtering, then uses HTTP requests to fetch full pages for better context. After the AI agent generates a clean summary, Slack receives a single, readable update rather than a pile of raw links.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you follow 10 RSS feeds and skim about 5 new posts per day. Manually, you’ll spend roughly 10 minutes per article to open the page, find the point, and write a summary, which is about 50 minutes daily. With this workflow, you spend maybe 5 minutes updating the feed list once, then just read the Slack digest. The run happens in the background; even if summarization takes a few minutes, you’re not doing it.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Slack for posting the daily digest message
- Google Sheets to log summaries for later searching
- Google AI Studio API key (get it from Google AI Studio)
Skill level: Beginner. You’ll connect accounts, paste an API key, and edit a feed list in a config node.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
Daily trigger runs the check. The workflow runs on a schedule (and can also be triggered via webhook), then reads from the RSS URLs you set in the Config node.
New items are identified and prepared. n8n cleans up fields, merges items when needed, and uses simple “if” logic so you don’t post duplicates or empty results.
Full articles get fetched for real context. An HTTP request visits each source URL so the AI agent summarizes the actual page, not a thin RSS excerpt. This is the part that makes the summaries worth reading, honestly.
Summaries land in Slack (and optionally Sheets). Slack receives the digest message your team can scan quickly, and Google Sheets can store the link, title, and summary so you can review patterns later.
You can easily modify the RSS source list to switch industries, clients, or competitors based on your needs. See the full implementation guide below for customization options.
Common Gotchas
- Slack credentials can expire or need specific permissions. If things break, check your Slack App scopes and the n8n credential connection test 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
About 30 minutes if your Slack app and AI key are ready.
No. You’ll mostly paste credentials and edit the RSS URL list. If you can handle basic “connect account” screens, you’re fine.
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 Google Gemini API usage, which is usually low for a daily digest.
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, and it’s the most common tweak. Update the prompt inside the AI Agent (and its chat model node) to change tone, length, and structure, then adjust the Slack message formatting so each summary lands the way your team likes. You can also change the takeCount parameter in the Config node to pull fewer or more items per feed. Some teams add a “must include” keyword filter before summarizing to keep the channel ultra-clean.
Usually it’s missing permissions on your Slack App or an expired token in n8n. Re-check the Slack node credential, confirm the app is allowed to post to the target channel, and make sure the channel still exists (private channels trip people up). If it fails only on bigger digests, you may be hitting message formatting issues, so shorten the summary length in the AI prompt.
On a typical setup, dozens of items per day is fine, and self-hosting scales mostly with your server. The practical limit is usually your AI summarization quota and how long you’re willing to wait for HTTP fetches to finish. If you expect hundreds daily, add keyword filters and keep takeCount conservative so Slack stays readable.
Often, yes, because n8n is comfortable with multi-step logic like “fetch RSS, pull full article pages, summarize, then format for Slack,” all in one scenario. You also get the option to self-host, which keeps execution limits from becoming a constant tax when you monitor a lot of feeds. Zapier and Make can still work if you only need a simple RSS → Slack link post, but the moment you add full-page scraping and AI summarization, things get fiddly and expensive. If you’re unsure, Talk to an automation expert and describe your feed volume and Slack preferences.
A Slack channel full of links doesn’t change anything. A daily digest with real summaries does, because your team will actually read it.
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.
