RSS to Slack, a clean daily digest your team reads

Your team “keeps up with the news” by skimming 12 tabs, saving random links, then forgetting where they saw that one critical update. By the time you share it in Slack, it’s buried under a hundred other messages.

This RSS Slack digest problem hits PMMs and PR/Comms first, because timing matters. Founders and Sales/CS leads feel it too, because you can’t act on what you never properly saw.

This workflow turns scattered RSS headlines into a crisp daily Slack briefing, then archives every item in Notion with clean tags and priorities. You’ll see exactly how it works, what you need, and where teams usually trip up.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: RSS to Slack, a clean daily digest your team reads

Click to explore

flowchart LR

    subgraph sg0["Daily Morning Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "Daily Morning Trigger", pos: "b", h: 48 }
        n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Workflow Configuration", pos: "b", h: 48 }
        n2@{ icon: "mdi:cog", form: "rounded", label: "Read RSS Feeds", pos: "b", h: 48 }
        n3@{ icon: "mdi:robot", form: "rounded", label: "AI Summarizer and Tagger", pos: "b", h: 48 }
        n4@{ icon: "mdi:database", form: "rounded", label: "Get Tag Dictionary", 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/>Parse AI Output"]
        n6["<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/notion.dark.svg' width='40' height='40' /></div><br/>Write to Notion Database"]
        n7@{ icon: "mdi:cog", form: "rounded", label: "Sort by Priority", pos: "b", h: 48 }
        n8@{ icon: "mdi:cog", form: "rounded", label: "Top 3 Headlines", 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/code.svg' width='40' height='40' /></div><br/>Format Slack Message"]
        n10["<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/>Post to Slack"]
        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/>Code in JavaScript"]
        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/>Aggregate Tags"]
        n13@{ icon: "mdi:brain", form: "rounded", label: "Google Gemini Chat Model", pos: "b", h: 48 }
        n2 --> n3
        n5 --> n6
        n8 --> n9
        n7 --> n8
        n11 --> n2
        n4 --> n12
        n9 --> n10
        n0 --> n1
        n1 --> n4
        n1 --> n11
        n3 --> n5
        n13 -.-> n3
        n6 --> n7
    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 n3 ai
    class n13 aiModel
    class n4,n6 database
    class n5,n9,n11,n12 code
    classDef customIcon fill:none,stroke:none
    class n5,n6,n9,n10,n11,n12 customIcon

The Problem: News Monitoring Turns Into Daily Busywork

Monitoring multiple sources sounds simple until it becomes part of everyone’s job and nobody owns it. You skim a few feeds, spot something important, then spend another chunk of time rewriting it into Slack-friendly context. Tomorrow, you do it again. And when someone asks, “Do we have a record of these updates?” you search Slack, scroll past memes, and realize the thread with the link is gone. The cost isn’t just time. It’s missed signals, duplicated work, and slower decisions.

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

Important items get shared inconsistently, so the team can’t trust the “daily update” to be complete.
Context gets lost because someone posts only the link, and now everybody has to click to understand why it matters.
Without a searchable archive, you re-find the same story three different times across a quarter.
Tags and priorities drift across people, which means reporting becomes a manual cleanup project later.

The Solution: A Daily RSS Digest in Slack, With Notion as Source of Truth

This n8n workflow runs on a morning schedule and pulls in new articles from a list of RSS feeds you control. It then uses an AI agent (with an LLM chat model behind it) to summarize each article and assign consistent tags based on a tag dictionary you maintain. After that, it parses the AI output into structured fields and writes each item into a Notion database with the properties your team can actually filter by (summary, tags, priority, URL, published date). Finally, the workflow sorts the day’s items by priority, selects the top headlines, formats a clean Slack message, and posts your digest to the channel you specify. You get the signal, and you keep the trail.

The workflow starts with a Morning Schedule Trigger and reads your feed list from a settings step. From there, it fetches RSS items, loads your tag catalog (commonly from Google Sheets), and hands everything to the AI summarizer and tagger. Notion becomes the archive, while Slack gets the short list your team will read.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

Pulls new posts from multiple RSS feeds on a daily schedule.
Summarizes each article and assigns tags using your maintained taxonomy.
Creates structured Notion records automatically, including URL and published date.
Builds and posts a formatted Slack digest of the top items.

Most teams get about 30–60 minutes back every weekday.
Less “link spam” in Slack, because only the top items make the digest.
More consistent tagging, which makes trend tracking possible later.
A searchable Notion archive that stops repeated “did we already see this?” work.
Faster reactions to competitor moves, product launches, and market chatter.

Example: What This Looks Like

Say you monitor 10 RSS feeds and usually share 6 relevant links a day. Manually, it’s maybe 5 minutes per link to skim, summarize, and tag, plus another 10 minutes to format a “top picks” Slack post, so you’re around 40 minutes daily. With this workflow, you spend about 10 minutes once to maintain your tag dictionary and tweak prompts, then each morning the run is hands-off: pull feeds, summarize, rank, post, archive. The time you get back is real, and the archive compounds in value week after week.

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.
Notion to store a structured, searchable news archive.
Google Sheets to maintain the tag dictionary (optional).
LLM provider key (set up in n8n credentials for Gemini/OpenAI).

Skill level: Beginner. You’ll connect accounts, paste a Notion database ID, and edit a short list of RSS URLs.

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

How It Works

A morning schedule kicks it off. The workflow runs on the Morning Schedule Trigger at the time you choose (many teams do weekdays around 9:00).

Your configuration controls everything. In the Workflow Settings Hub, you set the RSS feed URLs, your Notion database ID, and the Slack channel. That means changes don’t require rebuilding the workflow, just updating the settings fields.

Feeds and tags get pulled in. n8n splits your feed list, retrieves fresh RSS items, then loads your tag catalog (often from Google Sheets). A short code step compiles the tag list into a format the AI can use consistently.

AI summarizes, tags, then your systems get updated. The AI agent generates a summary plus tags and a priority score, the workflow parses that output into clean fields, creates Notion entries, sorts by priority, selects the top headlines, and posts a readable Slack digest.

You can easily modify the tag dictionary and priority rules to match how your team thinks about the market. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Schedule Trigger

Set the workflow to run automatically each morning and pass control into the settings hub.

Add or open Morning Schedule Trigger and set the schedule rule to run at 8 in triggerAtHour.
Connect Morning Schedule Trigger to Workflow Settings Hub to start the workflow.

Step 2: Connect Google Sheets

Load the tag catalog used by the AI for consistent tagging.

Open Load Tag Catalog and set Document ID to your spreadsheet, replacing [YOUR_ID].
Set Sheet Name to Tags (shown as gid=0 in the node).
Credential Required: Connect your Google Sheets credentials.
Ensure Load Tag Catalog outputs into Compile Tag List.

Tip: Keep your tag catalog clean and consistent. This list is injected into the AI prompt via {{ JSON.stringify($('Compile Tag List').first().json.tagDictionary) }}.

Step 3: Set Up the RSS Intake and Settings Hub

Define your RSS sources and route them into the feed reader in parallel with the tag load.

In Workflow Settings Hub, set rssFeeds to an array like ["https://techcrunch.com/feed/"].
Set notionDatabaseId to [YOUR_ID] and slackChannel to [YOUR_ID].
Verify that Workflow Settings Hub outputs to both Load Tag Catalog and Split Feed List in parallel.
In Retrieve RSS Articles, set URL to ={{ $json.rssFeeds }} to read each feed from Split Feed List.

⚠️ Common Pitfall: If rssFeeds is not an array in Workflow Settings Hub, Split Feed List will not create items for Retrieve RSS Articles.

Step 4: Set Up AI Summarization and Tagging

Use Gemini to generate structured JSON summaries and tags for each RSS item.

Open Gemini Chat Engine and confirm Model Name is models/gemini-2.0-flash-lite.
Credential Required: Connect your Google Gemini (PaLM) credentials in Gemini Chat Engine.
In AI Summary & Tags, keep the prompt as provided and ensure it references {{ JSON.stringify($('Compile Tag List').first().json.tagDictionary) }}, {{ $json.title }}, and {{ $json.content }}.
Confirm AI Summary & Tags outputs to Parse AI JSON for structured parsing.

Tip: The AI output parser is enabled in AI Summary & Tags, but the robust parsing logic in Parse AI JSON protects against invalid JSON.

Step 5: Configure Notion and Slack Outputs

Store enriched insights in Notion, rank by priority, and post the top headlines to Slack.

In Create Notion Entry, set Database ID to ={{ $('Workflow Settings Hub').first().json.notionDatabaseId }}.
Map the properties as configured: summary to ={{ $json.summary }}, tags to ={{ $json.tags }}, priority to ={{ $json.priority }}, url to ={{ $json.url }}, and publishedDate to ={{ $json.publishedDate }}.
Credential Required: Connect your Notion credentials in Create Notion Entry.
In Order by Priority, ensure the sort field is property_priority with Order set to descending.
In Select Top Headlines, set Max Items to 3.
In Dispatch to Slack, set Text to ={{ $json.message }} and Channel to ={{ $('Workflow Settings Hub').first().json.slackChannel }}.
Credential Required: Connect your Slack OAuth2 credentials in Dispatch to Slack.

⚠️ Common Pitfall: Notion property keys in Create Notion Entry must match your database fields exactly (e.g., summary, tags, priority).

Step 6: Test and Activate Your Workflow

Run a full test to validate RSS ingestion, AI output, Notion entries, and Slack delivery.

Click Execute Workflow and confirm Workflow Settings Hub fans out to Load Tag Catalog and Split Feed List in parallel.
Verify Retrieve RSS Articles emits items and AI Summary & Tags returns valid JSON, then check Parse AI JSON for clean fields.
Confirm a new page appears in Notion from Create Notion Entry, and a Slack message is posted by Dispatch to Slack with three headlines.
Once validated, toggle the workflow to Active for daily production runs.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

Notion credentials can expire or need specific permissions. If things break, check your Notion integration access and the target database share settings 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 Slack digest automation?

About 30 minutes if your Slack, Notion, and LLM accounts are ready.

Do I need coding skills to automate RSS Slack digest delivery?

No. You’ll mostly paste IDs, connect credentials, and edit the RSS feed list. The code steps are already built into the workflow.

Is n8n free to use for this RSS Slack digest 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 LLM API costs (often just a few dollars a month at typical digest volume).

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 Slack digest workflow for per-topic digests?

Yes, and it’s one of the best tweaks. You can expand the Google Sheets tag dictionary, then adjust the “Compose Slack Digest” step to group items by tag and post separate sections (or even separate channel posts). Common customizations include increasing “Top 3” to “Top 10,” sorting by recency for fast-moving categories, and creating one Notion database per team.

Why is my Slack connection failing in this workflow?

Most of the time it’s missing permissions on the Slack app, especially chat:write for the target channel. It can also fail if the channel ID changed, the app wasn’t invited to a private channel, or your token was rotated. Check the Slack node credentials in n8n, then confirm the channel and app access in Slack itself. If you’re posting a lot of items, rate limits can show up, so keep the digest concise and lean on the Notion archive for the full list.

How many articles can this RSS Slack digest automation handle?

Plenty for typical monitoring, and the practical limit is your n8n plan plus your LLM rate limits.

Is this RSS Slack digest automation better than using Zapier or Make?

Often, yes, because the AI + parsing + sorting logic is where simpler tools get clunky. n8n makes it easier to keep everything in one workflow: pull feeds, call an LLM, transform the output, write to Notion, then post to Slack. It’s also nice that you can self-host if you want more control and higher volume. Zapier or Make can still be fine for a basic “RSS to Slack” alert, but the moment you add tagging rules and a Notion archive, costs and complexity creep in. Talk to an automation expert if you want a quick recommendation for your setup.

Once this is running, your team gets a briefing they actually read and a Notion archive you can search when decisions come up later. Honestly, it’s the kind of “small” automation that quietly fixes a daily annoyance.

RSS to Slack, a clean daily digest your team reads

How This Automation Works

n8n Workflow Template: RSS to Slack, a clean daily digest your team reads

The Problem: News Monitoring Turns Into Daily Busywork