Catching "URGENT, our automation broke" posts with a pure-Python RSS pipeline (no API keys, no SaaS)

#python #rss #automation #freelancing

There's a category of freelance work where speed beats reputation: somebody's Zapier scenario died at 2am, their previous developer vanished, their Amazon listing got hijacked — and they'll hire whoever shows up first with a competent answer.

The problem: these "fires" are scattered across Reddit, community forums and job boards, and they go stale in hours. Manually checking ten places a day doesn't scale. So I built a monitor. It's ~250 lines of stdlib Python and it found 19 qualified leads on its first run.

The stack is deliberately boring

Reddit — every subreddit ships an Atom feed at /new.rss. No OAuth, no API keys, no rate-limit dance that the JSON API now requires. urllib + xml.etree and you're reading r/smallbusiness in 15 lines.
Discourse forums (n8n community, Make community) — every category exposes clean JSON at /c/<slug>/<id>.json. Again: no auth for public boards.
Freelance platforms — saved-session cookies + whatever JSON endpoint the SPA itself calls.

One scheduled run every 30 minutes, 2-second sleeps between requests, persistent dedup state. Total infrastructure cost: zero.

The interesting part is the filtering

Pulling posts is trivial. Not drowning in noise is the actual engineering. Three regex layers did it:

1. Urgency signals — urgent, asap, broken, stopped working, previous developer, ghosted, losing sales…

3. The noise killer (this one matters most): community boards are full of other freelancers advertising themselves and discussion threads that match every keyword. Kill patterns: posts starting with "I help / I build / Available for", question-form titles ("How do you…", "What's the best…"), co-founder fishing, "looking for feedback".

Per-source policies differ: a general business subreddit needs urgency AND relevance; a hiring board just needs a genuine hire signal; an Amazon-seller subreddit triggers on special events (hijacked, suspended, buy box) regardless of phrasing.

First run before the noise filter: 57 hits, maybe a third usable. After: 19 hits, almost all real — 13 of them genuine "hiring n8n developer" posts.

Lessons that transfer to any monitoring pipeline

RSS is undead. APIs get keys, quotas and pricing tiers; feeds quietly keep working. Check for a feed before you reach for an API or a headless browser.
First run is a baseline. Everything is "new" on run #1 — write state, alert nothing. Saved me from a 57-message Telegram flood.
Dedup across systems. I run a second monitor that watches an overlapping source; they share a seen-IDs file so nothing alerts twice.
Alert quality is a product decision. Every alert that's noise trains you to ignore the channel. I'd rather miss a borderline lead than mute the bot.

Does it work?

The monitor's job is to compress "check 12 places constantly" into "glance at Telegram". It does. Whether each lead converts is a sales problem — but you can't answer a fire you never saw.

I build monitoring and alerting pipelines like this for businesses — price watches, inventory alerts, mention tracking, compliance feeds. If you need eyes on something that changes fast, tell me what or email jobs@podlevskikh.com.