Remote Job Leads Monitor — New RemoteOK Jobs

Watch RemoteOK and WeWorkRemotely on a schedule and get only the new remote jobs matching your keywords since your last run. Both boards are read from their official public feeds, normalized into one format and deduplicated across runs, so a weekly schedule gives you a stream of remote job leads instead of the same 200 rows every time.

Remote job boards move fast: the good postings get hundreds of applicants within days. The applicants who land them are the ones who applied in the first hours. This monitor turns two of the biggest remote boards into a deduplicated alert stream, so you're always in the first wave.

What it does

1. Reads RemoteOK's official public API and WeWorkRemotely's public RSS feed.
2. Normalizes both into one job format: title, company, location, tags, employment type, salary range when published, direct link.
3. Applies your filters — keywords (title, company, tags, location) and optionally contract/freelance signals only.
4. Remembers every job it has already seen (per filter set, in a persistent state store) and outputs only the NEW ones on every later run.

Monitor, not scraper

A RemoteOK or WeWorkRemotely scraper hands you the board's current jobs on every run and leaves the diff to you. This Actor keeps the memory instead: the first run saves a baseline, every later run outputs only what appeared since, per keyword set.

Who these remote job leads are for

• Job seekers / freelancers: schedule every few hours with your skill keywords → apply in the first wave.
• Contract hunters: contractOnly: true keeps only gigs with contract/freelance/part-time signals.
• Talent watchers: keyword on a competitor's name to see when they hire remotely.

Input example

{
  "keywords": ["video", "motion"],
  "contractOnly": true
}

The defaults work as-is (both boards, all new jobs).

Output example

{
  "jobId": "wwr:pixelworks-motion-designer",
  "source": "weworkremotely",
  "title": "Motion Designer & Video Editor",
  "company": "PixelWorks",
  "location": "Europe Only",
  "employmentType": "Full-Time",
  "tags": ["Design"],
  "salaryMinUsd": null,
  "salaryMaxUsd": null,
  "url": "https://weworkremotely.com/remote-jobs/pixelworks-motion-designer",
  "postedAt": "2026-07-05T08:00:00.000Z",
  "matchedKeywords": ["video"],
  "isNewSinceLastRun": true
}

A SUMMARY record in the run's key-value store gives the counts per run — including per-source errors, so one board having a bad day never silently empties your feed.

Data returned for every remote job

Field	What it holds
jobId, source	Stable id and which of the two boards it came from
title, company	Role and hiring company
location	Region restriction published by the board
employmentType	Full-time, contract or part-time when the board publishes it
tags	Board tags, also used for keyword matching
salaryMinUsd, salaryMaxUsd	Salary range when published
url, postedAt	Direct link to the posting and its publication date
matchedKeywords, isNewSinceLastRun	Why it matched and whether this run is the first to see it

Fair use & data

• Reads only official public endpoints: the Remote OK API (jobs link back to Remote OK as their terms request) and WeWorkRemotely's public RSS feed.
• No personal data — these are company job postings; no candidate or poster identities are collected.
• Feeds are naturally bounded (~100 jobs each); the monitor's memory turns them into a complete over-time stream.

FAQ

Why these two boards? They're the two largest remote boards with clean public feeds. More sources can be added — tell us in the Issues tab which one you need.

First run floods me. That's the baseline (flagged isBaseline: true); disable includeBaselineInOutput to start silent.

How do I reset the memory? Set a new monitorId.