An n8n keyword filter and dedup for RSS alerts, already wired

A plain RSS-to-alert workflow fires on every single item in the feed. Point it at a competitor's blog or a broad industry feed and you're buried in noise within a day. This one filters by keyword and never repeats a match.

$29

Buy on Gumroad

The problem

A plain RSS-to-alert workflow fires on every single item in the feed, most of which you don't care about. Point it at a competitor's blog or a broad industry feed and you're buried in noise within a day, or you end up building the keyword filtering and duplicate-suppression logic yourself, by hand, in a Code node, from scratch.

What this workflow does

Polls a feed on a schedule you set.
Filters by keyword: you supply the list (a competitor name, a topic, your own brand) and only matching items continue.
Never alerts twice: a cross-run dedup check, stored in n8n's workflow static data, survives restarts and keyword-list edits, so a match you've already been alerted on doesn't fire again.
Formats the match into a clean alert payload and hands off to a notification slot you wire to Slack, email, Discord, or anything else n8n has a node for.

Before and after

A bare RSS-to-alert template

Fires on every single item, no filtering.
The same match alerts you again after every restart.
Keyword matching and dedup are yours to build from scratch.

With this workflow

Keyword matching and cross-run dedup are real, wired logic in the JSON, tested end to end on a live n8n instance.
A match you've already seen never fires again, even across restarts.
A setup guide and troubleshooting table travel with it.

What you get

The workflow JSON: RSS trigger, keyword-match filter, already-alerted filter, alert formatter, notification slot for you to connect.
A setup guide: prerequisites, 15-minute walkthrough, troubleshooting table.
A test checklist showing exactly what was run against a live n8n instance, and the result.

Who it's for

Ops people and small agencies already tracking a competitor or an industry feed who are tired of either building the filter/dedup logic themselves or drowning in every-single-post noise from a bare RSS trigger.

FAQ

Does this need any paid API keys?

No, not for the watching, filtering or dedup steps. Only your chosen notification channel (e.g. a Slack bot token) needs its own credential, which you supply.

How is this different from just adding an IF node to a free template?

You can build this yourself in under an hour if you already know n8n's expression syntax and how workflow static data works for cross-run state. This skips that: the filter and dedup are wired, tested, and documented.

What n8n version was this tested on?

n8n 2.35.5. Pinned version and update policy are in the setup guide.