We Work Remotely Jobs Scraper (WeWorkRemotely RSS)
Pricing
from $2.13 / 1,000 job saveds
We Work Remotely Jobs Scraper (WeWorkRemotely RSS)
WeWorkRemotely jobs from the official RSS: full descriptions, filters, only-new daily alerts. For alerts and research, not job boards. $2.50 per 1,000 jobs.
Pricing
from $2.13 / 1,000 job saveds
Rating
0.0
(0)
Developer
Kaizoku Data
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
25 days ago
Last modified
Categories
Features
Share
Get remote jobs from We Work Remotely (WeWorkRemotely) as clean, structured data: full description included, company, category, job type, region, countries, skills and dates. The Actor reads WWR's official public RSS feeds, which WWR offers for anyone to use, so it needs no browser and no proxies, and doesn't break when the website layout changes.
Price: $2.50 per 1,000 jobs ($0.0025 per job), full description included. No separate "detail" charge. A daily alert typically costs about $0.05–0.15 a day.
For alerts, research and internal tools, with a link back to WWR; not for job boards, aggregators or job search services (see Terms of use*).*
- Only new jobs: schedule it daily and each run returns (and charges for) only jobs you haven't seen, remembered for 120 days.
- Whole-word filters: keywords and exclude keywords (
gowon't match "Google";c++andnode.jswork), regions and countries, job types, posted within N hours. - All 11 category feeds plus the latest-jobs feed, de-duplicated.
- Emails and phone numbers removed from titles and descriptions; every row carries its WWR link and an attribution string.
- Quick start: press Start. The prefilled input reads the Programming feed and finishes in seconds.
What you can do with it
- Daily job alerts. Schedule it with Only new jobs turned on, and each run returns (and charges for) only jobs you haven't seen.
- Alerts and internal dashboards. Send new jobs to your own or your team's Slack, Discord, email or internal dashboard. Keep the link back to WWR (see Terms of use below). Not for public job boards, aggregators or job search services.
- Market research. Track which companies hire remotely, in which categories and regions.
Input
| Field | What it does |
|---|---|
| Categories | all (default) reads all 11 category feeds plus the latest-jobs feed and removes duplicates. Or pick any of: programming, full-stack, back-end, front-end, devops, design, product, customer-support, sales-marketing, management-finance, other, latest. |
| Keywords (any) | Keep a job if any keyword appears as a whole word in its title, company, category, skills or description (go won't match "Google"; c++ and node.js work). |
| Exclude keywords | Drop a job if any of these appear (whole words). |
| Regions / countries | e.g. Europe, United States. Whole-word match on the job's region, country list and state. |
| Always include worldwide jobs | On by default: "Anywhere in the World" jobs pass the region filter. |
| Job types | Full-Time, Contract, Part-Time. |
| Posted within (hours) | e.g. 24 for a daily digest. |
| Only new jobs since my last run | Remembers the job IDs it already returned to you (for 120 days) and skips them. |
| Only-new memory name | Optional label (stateName; older inputs may still send it as stateKey, which works the same). Use different names for separate histories; empty means default. |
| Max jobs | Newest first. |
| Include description HTML | Plain text is always included; turn HTML off for smaller datasets. |
Example inputs
1. Daily alert: Python or Go jobs open to Europe (schedule it daily; with Only new jobs each run returns only jobs you haven't seen):
{"categories": ["programming", "devops"],"keywords": ["python", "golang"],"regions": ["Europe"],"postedSinceHours": 24,"onlyNew": true}
2. All DevOps jobs open to Europe from the last 24 hours, full-time only ("Anywhere in the World" jobs are kept too unless you turn off Always include worldwide jobs):
{"categories": ["devops"],"regions": ["Europe"],"jobTypes": ["Full-Time"],"postedSinceHours": 24}
3. Product and design jobs without senior or lead roles (exclude words match whole words anywhere in the job):
{"categories": ["product", "design"],"excludeKeywords": ["senior", "lead", "principal", "head"],"maxItems": 100,"includeDescriptionHtml": false}
Output
One item per job:
{"id": "acme-senior-backend-engineer","url": "https://weworkremotely.com/remote-jobs/acme-senior-backend-engineer","title": "Senior Backend Engineer","company": "Acme","companyLogoUrl": "https://wwr-pro.s3.amazonaws.com/logos/…/logo.gif","companyHeadquarters": "Berlin","companyWebsite": "https://acme.dev","category": "Back-End Programming","jobType": "Full-Time","region": "Anywhere in the World","countries": ["Germany", "United Kingdom of Great Britain and Northern Ireland"],"state": null,"skills": ["Go", "PostgreSQL"],"descriptionHtml": "<p>…</p>","descriptionText": "…","publishedAt": "2026-10-17T13:11:19.000Z","expiresAt": "2026-11-16T13:11:19.000Z","feed": "back-end","source": "We Work Remotely","attribution": "Source: We Work Remotely (https://weworkremotely.com/remote-jobs/acme-senior-backend-engineer)","scrapedAt": "2026-10-18T06:00:00.000Z"}
You can export it as JSON, CSV, Excel or XML, or read it through the Apify API.
Fill rates in our 2026-10-18 sample of 529 listings: id, url, title, company, category, region, description and publishedAt 100%; jobType and expiresAt 95%; companyHeadquarters 98%; companyWebsite 35%; companyLogoUrl 26%; countries 21%; state 22%; skills 17%. The low numbers are fields WWR leaves empty in its feed.
Pricing
Pay per event:
- $0.0025 per job saved to the dataset.
- Apify's standard tiny start fee per run.
| Run | Jobs | Cost |
|---|---|---|
| Daily alert with Only new jobs | a few dozen | about $0.05–0.15 a day |
| One full read of all feeds | about 400–450 | about $1.00–1.13 |
| 1,000 jobs | 1,000 | $2.50 |
For example, 1,000 jobs cost $2.50. A daily alert with Only new jobs typically returns a few dozen jobs, about $0.05–0.15 a day. You can cap the cost of any run with Apify's Max total charge setting. The Actor stops when it reaches the cap, and jobs already delivered are remembered by Only new jobs, so you never pay twice for the same job.
Use it via API, n8n or Make
For alerts for yourself or your team, research and internal tools (not for job boards, aggregators or job search services; see Terms of use). Get an API token in Apify Console → Settings → API & Integrations, and keep it in an environment variable (APIFY_TOKEN below).
cURL (starts a run, waits for it and returns the jobs as JSON):
curl -X POST "https://api.apify.com/v2/acts/ataism~wwr-jobs/run-sync-get-dataset-items?token=$APIFY_TOKEN" \-H "Content-Type: application/json" \-d '{"categories": ["programming"], "keywords": ["python"], "postedSinceHours": 24}'
JavaScript (npm install apify-client):
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('ataism/wwr-jobs').call({categories: ['programming'],postedSinceHours: 24,onlyNew: true,});const { items } = await client.dataset(run.defaultDatasetId).listItems();for (const job of items) console.log(job.company, job.title, job.url);
Python (pip install "apify-client>=3"):
import osfrom apify_client import ApifyClientclient = ApifyClient(os.environ["APIFY_TOKEN"])run = client.actor("ataism/wwr-jobs").call(run_input={"categories": ["programming"],"postedSinceHours": 24,"onlyNew": True,})for job in client.dataset(run.default_dataset_id).iterate_items():print(job["company"], job["title"], job["url"])
(With apify-client versions before 3.0, call() returns a dict: use run["defaultDatasetId"].)
n8n (new jobs to your own Slack, sheet or email):
- Add a Schedule Trigger (for example daily at 08:00).
- Add the Apify node, operation Run an Actor and get dataset, Actor
ataism/wwr-jobs, and paste your input JSON with"onlyNew": true. - Add a Slack, Google Sheets or email node and post
title,companyandurl(the link back to WWR).
Make:
- Add the Apify module Run an Actor, choose
ataism/wwr-jobs, paste the input JSON and set Run synchronously to Yes. - Add the Apify module Get Dataset Items and map the run's default dataset ID.
- Send the rows to your own Slack, sheet or email, keeping each job's
url. Schedule the scenario daily.
Terms of use: attribution, and no job boards
This Actor reads only WWR's public RSS feed. It doesn't scrape the website or use WWR's API. WWR's feed page says: "Anyone can use the feed, all we ask is that you attribute the links back to We Work Remotely."
- Attribution on every row: each item carries the job's WWR
urland anattributionstring. Wherever you show a job, link it to itsurl. - Not for republishing on job boards: don't use this data to run or feed a job board, job aggregator or job search service. WWR's API terms rule that out for their data. Good uses are research, market analysis, alerts for yourself or your team, and internal tools.
Privacy
This Actor collects job listings only. To avoid passing on personal data, it removes email addresses and phone numbers from titles and descriptions; you'll see [email removed] or [phone removed] instead. Encoded addresses (HTML entities, %40) are caught too, and if an address is split across HTML tags, that listing's HTML is replaced by its cleaned plain text. Free-text tricks such as "john (at) example (dot) com" may not be caught. Apply through the job's WWR page.
Reliability
- Reads official RSS, not HTML, so website redesigns don't break it.
- Retries on network errors and 429/5xx responses with backoff, honours
Retry-After, and pauses between feeds. - If a feed returns an error page instead of RSS, it's retried. If it still fails, the run names the failed feeds in its status message and in the
RUN_SUMMARYrecord, and the run fails if every feed failed. - A daily self-test checks the live feeds against a recorded baseline (schema and field fill rates). We fix breakages fast.
FAQ
How many jobs are there? About 400–450 unique live jobs across all categories (2026-10-18). The latest feed alone holds roughly the newest 90.
Is it allowed? Yes, for alerts, research and internal tools with a link back to WWR. We read only the official RSS feeds WWR publishes ("Anyone can use the feed"), and WWR's robots.txt allows them. Not for running or feeding a job board, aggregator or job search service (see Terms of use). We're not affiliated with We Work Remotely.
Something's wrong? Open an issue on the Actor's Issues tab. We aim to reply within 2 working days.