WeWorkRemotely Scraper at a glance
WeWorkRemotely Scraper is a ready-to-run Apify actor from abotapi for collecting jobs data. Its documented output includes title, company, type, category and region, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $1.80 per 1,000 results on the Apify Free plan and from $1.20 on paid plans, with smaller per-run or optional feature charges listed on Apify.
- Runs on
- Apify cloud: console, API, schedules and integrations
- Data type
- Jobs, Automation, Lead Generation
- Pricing
- $1.80 per 1,000 results (Free plan), from $1.20 on paid plans
- Output
- Documented below · JSON, CSV, Excel
- Inputs
- 25 options
Extract current remote job listings from weworkremotely.com. Use keyword search or WWR feed, category, and remote-jobs URLs. Returns clean job rows with title, company, category, region, tags, salary text, description matches, and filtered structured output.
What WeWorkRemotely Scraper can do
- Two ways in. Search current listings by keyword across one or all supported categories, or paste a specific We Work Remotely feed or category URL directly.
- Eleven category feeds, one run. Choosing All categories scans all eleven category feeds (programming, design, customer support, sales and marketing, product, devops and sysadmin, management and finance, full-stack, front-end, back-end and all other remote jobs) and deduplicates jobs by listing URL, for broader coverage than the main feed alone.
- Filter before you pay. Keep only listings that match a region, a posting age window, a salary hint, a company website, or a minimum description length.
- Full descriptions on demand. Turn on Include full description fields for cleaned description text and parsed sections (About the company, Responsibilities, Requirements, Benefits); extracted technologies and an inferred seniority level are always computed regardless of this toggle.
- Built for schedules. Incremental mode tracks one search over time and returns only new and changed jobs on later runs, so a daily monitor never re-bills an unchanged posting.
- Resume a run that hit its cap. Continue one earlier run that finished but stopped at Max items before reaching every feed, by its run or dataset id; jobs it already collected are skipped rather than re-scraped and re-billed.
Choose what to collect
These inputs let you configure WeWorkRemotely Scraper - Remote Jobs, Salaries & Companies. Open the actor on Apify to enter your values and review the current options.
| Input | What it controls |
|---|---|
modestring | Keyword search filters live WWR job feeds by search terms. URL list reads WWR feed, category, or remote-jobs URLs. Precedence: the selected mode decides which source is used; the other mode's field (Start URLs or Keyword search terms) is ignored. |
startUrlsarray | Accepts WWR RSS feeds, category pages (with or without .rss), the main remote jobs page, search URLs (the term becomes a keyword filter) and job posting URLs (matched by job slug across the feeds). |
searchTermsarray | Search terms to match in current remote job listings. Left empty with no category chosen, the run searches the example term python instead of stopping; that example run never saves or expires Incremental mode state. |
categoriesarray | Restrict keyword search to selected WWR categories. Leave empty or choose All categories to scan all supported category feeds. |
regionsarray | Only keep listings whose region contains one of these values. Examples: Anywhere in the World, United States, Europe. |
includeDetailsboolean | When enabled, each row includes full description HTML and cleaned description text. |
maxItemsinteger | Maximum number of matching job rows to save. The run can return fewer rows when the selected keywords and filters match fewer current listings. |
Show 18 more inputs
| Input | What it controls |
|---|---|
sortstring | Order of the saved rows, applied after the filters and before Max items. Feed order is the site's own order. With incremental mode on, the sort orders only the rows returned in this run. |
results_wantedinteger | Alias of Max items; when set it wins. |
search_urlsarray | Alias input: We Work Remotely URLs (search, category, feed or job URLs). When set the actor runs in URL list mode with these URLs. |
categorystring | Alias of Categories for a single category, using the remote--jobs feed names. Keyword mode then runs without search terms. |
postedWithinDaysinteger | Only keep jobs posted within this many days. Leave empty for no date filter. |
requireSalaryboolean | Only keep rows where a salary hint was found in the listing text. |
requireCompanyWebsiteboolean | Only keep rows with a company website URL. |
requireApplyUrlboolean | Only keep rows with an apply URL. |
minDescriptionLengthinteger | Only keep rows whose cleaned description text has at least this many characters. |
resumeFromRunIdstring | ID of a previous run of this actor (or a dataset ID). Jobs already collected by that run (matched by job id) are skipped, so this run returns only the remainder, a delta. Combine both runs' datasets for the full set. Use this when a run was aborted, timed out, or stopped early at its Max items cap before every selected feed was read. Leave empty for a normal fresh run. For recurring daily monitoring of the same search, use Incremental mode below instead. |
incrementalModeboolean | Turn this on for daily or recurring monitoring. The first run returns all matching jobs as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED jobs. Turn on "Emit unchanged" or "Emit expired" only when you also want those jobs returned (and billed). Jobs are compared on every output field except scrapedAt, postedAgeDays, expiresInDays and isExpired (always excluded because they change with the clock) and anything you list in "Ignore fields when detecting changes". State is kept separately per search/URL, filter, and detail-mode setup; use State key to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above. |
stateKeystring | Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from the search/URL, filters, and detail settings: different searches then never mix state with each other. With your own State key and Incremental mode on, keyword mode needs a search term or a category: with neither, the run stops with an input message and collects nothing. |
emitUnchangedboolean | Off by default. Turn on to also return jobs that have not changed since the last run, marked UNCHANGED. This returns (and bills) extra rows you already have, so leave it off unless you specifically want the full snapshot every run. |
emitExpiredboolean | Off by default. Turn on to also return jobs that were present in a previous run but are no longer found in the feed, marked EXPIRED. Only produced once a run has fetched and fully scanned every requested feed, not when Max items capped it and not when Resume from a previous run was used (a resumed run deliberately skips jobs, so it cannot tell missing from already collected). This returns (and bills) extra synthetic rows, so leave it off unless you need expiry tracking. |
ignoreFieldsForChangesarray | Incremental mode only. Field names (for example title, or a dotted path such as salary.min) whose changes do NOT make a job UPDATED and are left out of changedFields. The fields stay in the output. Always excluded already: scrapedAt, postedAgeDays, expiresInDays and isExpired, which change with the clock rather than with the posting. Changing this list never causes a wave of UPDATED rows. |
mcpConnectorsarray | Optionally send the scraped jobs into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify → Settings → API & Integrations, then select it here. Notion gets a rich page-per-job export; other connectors receive a best-effort write/digest. Leave empty to skip; this never changes the dataset output. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com). |
notionParentPageUrlstring | URL (or id) of the Notion page under which job pages are created. Required to enable the Notion export; ignored by other connectors. |
maxNotifyListingsinteger | Cap on how many jobs are written to each selected connector per run. Does not affect the dataset. |
Fields in the output
The documented dataset includes the fields below. Availability can depend on the source page and selected mode.
titleTitle (text)companyNameCompany (text)jobTypeType (text)categoryCategory (text)regionRegion (text)countryCountry (text)stateState (text)salaryTextSalary (text)salaryIntervalSalary interval (text)salaryCurrencyCurrency (text)salaryMaxSalary max (number)salaryMinSalary min (number)Show 24 more fields
locationTextLocation (text)categoriesCategories (array)seniorityLevelSeniority (text)technologiesTechnologies (array)companyWebsiteUrlCompany website (link)applyUrlApply URL (link)applyUrlIsExternalExternal apply (boolean)canonicalUrlWWR URL (link)postedAtPosted at (date)expiresAtExpires at (date)scrapedAtScraped at (date)changeTypeChange type (text)changedFieldsChanged fields (array)firstSeenAtFirst seen at (date)lastSeenAtLast seen at (date)jobIdJob ID (text)descriptionTextDescription (text)descriptionSectionsSections (object)aboutCompanyTextAbout company (text)responsibilitiesTextResponsibilities (text)requirementsTextRequirements (text)benefitsTextBenefits (text)skillsSkills (array)descriptionLengthDescription length (text)Example output
An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.
{
"rowType": "job",
"jobId": "3f9a1c2b7e0d4a58",
"jobSlug": "nimbus-robotics-senior-backend-engineer-example",
"title": "Senior Software Engineer, Backend (Python)",
"rawTitle": "Nimbus Robotics: Senior Software Engineer, Backend (Python)",
"companyName": "Nimbus Robotics",
"url": "https://weworkremotely.com/remote-jobs/nimbus-robotics-senior-backend-engineer-example",
"canonicalUrl": "https://weworkremotely.com/remote-jobs/nimbus-robotics-senior-backend-engineer-example",
"applyUrl": "https://careers.nimbusrobotics.example/jobs/1234",
"applyUrlIsExternal": true,
"companyWebsiteUrl": "https://nimbusrobotics.example",
"region": "Anywhere in the World",
"category": "Back-End Programming",
"jobType": "Full-Time",
"skills": [
"Python",
"Django",
"AWS"
],
"technologies": [
"Python",
"AWS",
"PostgreSQL"
],
"seniorityLevel": "Senior",
"salaryText": "$140,000 - $170,000",
"salaryMin": 140000,
"salaryMax": 170000,
"salaryCurrency": "USD",
"postedAt": "2026-09-20T14:05:00Z",
"postedAgeDays": 8,
"expiresAt": "2026-10-20T14:05:00Z",
"expiresInDays": 21,
"isExpired": false,
"descriptionText": "We're looking for a senior backend engineer to own our core payments API...",
"descriptionLength": 3187,
"descriptionSections": {
"About the company": "Nimbus Robotics builds...",
"Responsibilities": "Own our core payments API..."
},
"externalLinks": [
"https://nimbusrobotics.example",
"https://careers.nimbusrobotics.example/jobs/1234"
],
"sourceType": "rss",
"searchKeyword": "python",
"scrapedAt": "2026-09-29T08:00:00Z"
}Ways to use this data
- Recruiting and talent sourcing: run a keyword search across every category to build a daily shortlist of remote openings to reach out against.
- Lead generation and market tracking: watch which companies are hiring remotely as a signal for sales or investment research.
- Job board aggregation: mirror We Work Remotely postings, with normalized fields, into your own site, newsletter or app.
- Compensation and skills research: collect salary hints, seniority levels and extracted technologies across categories to study pay and skill trends.
- Job alert automation: schedule a keyword search with Incremental mode and forward only newly posted jobs to Slack, email or a chat bot.
Before you run
Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.
Questions about this actor
What data does WeWorkRemotely Scraper return?
The documented output for WeWorkRemotely Scraper includes title, company, type, category, region, country, state and salary. Availability of each field depends on the source page and the selected mode.
How much does WeWorkRemotely Scraper cost?
It costs $1.80 per 1,000 results on the Apify Free plan and from $1.20 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.
Can I get only new or changed jobs on a schedule?
Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new and updated jobs by default; jobs that have not changed are suppressed and not billed unless you turn on Emit unchanged, and expired jobs only appear once you also turn on Emit expired, with reappeared jobs only possible after that on a later run.
What do the output views show?
The dataset has three views: Overview (the main job columns), Changes (change type and changed fields, for Incremental mode) and Detail (descriptions, sections and links). The same rows are available through the API and every export format.
Can I use it with AI agents or MCP?
Yes. Call it from any Apify integration or MCP client, and use the connector field to push a summary of each saved job into Notion, Linear or Airtable.
