An n8n hiring-signal watcher, scored, deduped, no scraping

Most "watch for hiring signals" workflows scrape LinkedIn through a paid proxy service: a per-request fee before you've closed a single deal. This one watches public job feeds instead, at zero ongoing cost.

$29

Buy on Gumroad

The problem

Most "watch for hiring signals" workflows scrape LinkedIn through a paid proxy service: a per-request fee before you've closed a single deal, plus a scraping-ToS risk that a plain RSS watch doesn't carry.

What this workflow does

Polls a public job-board feed (Greenhouse, an aggregator like WeWorkRemotely, or any board that publishes RSS) on a schedule you set.
Filters by target role: you supply the role list, only matching postings continue.
Scores hiring intent: seniority language ("VP", "Head of", "Director") and urgency language ("immediate", "fast-growing") push a posting from Standard to Warm to Hot.
Never alerts twice: a cross-run dedup check, stored in n8n's workflow static data, survives restarts and role-list edits.
Formats the match into a clean alert payload and hands off to a notification slot you wire to Slack, email, or a CRM webhook.

Before and after

A LinkedIn-scraper template

A proxy account and a per-request or per-lead fee before any deal closes.
Scraping-ToS exposure on the account you're using.
No scoring, every posting looks the same.

With this workflow

Role matching, intent scoring, and cross-run dedup are real, wired logic, tested end to end on a live n8n instance.
Zero ongoing cost, zero scraping-ToS exposure, broader public feed coverage instead.
A setup guide and troubleshooting table travel with it.

What you get

The workflow JSON: RSS trigger, role-match filter, intent-score 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

Agencies and sales teams using "company X is hiring for Y" as a prospecting trigger, who want the role-matching and intent-scoring logic already wired instead of building it from a bare feed trigger, and who don't want a per-lead scraping API bill.

FAQ

Does this need any paid API keys?

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

Why not scrape LinkedIn directly for more coverage?

You can, but that means a proxy account, a per-request or per-lead fee, and exposure to LinkedIn's anti-scraping enforcement. This pack trades some coverage for zero ongoing cost and zero account risk. If you already have a scraping pipeline, the scoring and dedup Code nodes here can be adapted to feed off it.

What n8n version was this tested on?

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