Working Nomads Remote Jobs Scraper

Extract public remote job listings from Working Nomads. The actor reads the site's public exposed jobs feed, cleans HTML descriptions into readable text, applies optional local filters, deduplicates by job ID, and writes one structured record per job.

Input

• searchQueries: optional title/company/category/location/tag/description terms.
• locations, categories, tags: optional filters.
• startUrls: optional Working Nomads /jobs or /api/exposed_jobs/ URLs; the default public feed is used when omitted.
• maxResults: 1–500, default 50.
• includeDescriptionHtml: include the original HTML description in addition to cleaned text.

Output

Each dataset item includes jobId, title, company, category, tags, location, publishedAt, description, jobUrl, provenance, and scrapedAt.

The actor handles public records only. It does not log in, apply for jobs, or access private account data. Result PPE is configured at $0.002 per unique dataset item; the start event is $0.00005.

What data does Working Nomads Remote Jobs Scraper return?

Field	Type	Description
jobId	string	Job ID
title	string	Job title
company	string or null	Company
category	string or null	Category
tags	array	Tags
location	string or null	Location
publishedAt	string or null	Published at
description	string or null	Description
descriptionHtml	string or null	HTML description
jobUrl	string	Job URL
sourceApiUrl	string	Source API URL
scrapedAt	string	Scraped at

Use cases

• Schedule repeatable collection and export results to downstream workflows.
• Run a one-off research job and export the structured result as JSON, CSV, Excel, XML, or RSS from Apify.
• Schedule the same input to monitor changes over time and send completed datasets to a webhook or integration.
• Feed schema-shaped records into a database, spreadsheet, BI tool, or AI workflow with the source URL retained for verification.

Input example

{
  "searchQueries": [],
  "locations": [],
  "categories": [],
  "tags": [],
  "startUrls": [],
  "maxResults": 50,
  "maxRequestRetries": 2,
  "includeDescriptionHtml": false
}

Run Working Nomads Remote Jobs Scraper with the Apify API

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('muhammadafzal/working-nomads-scraper').call({
  "searchQueries": [],
  "locations": [],
  "categories": [],
  "tags": [],
  "startUrls": [],
  "maxResults": 50,
  "maxRequestRetries": 2,
  "includeDescriptionHtml": false
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

You can also run the Actor from Apify Console, schedules, webhooks, the REST API, Make, Zapier, n8n, or the hosted Apify MCP server.

Pricing and cost control

This Actor uses pay-per-event pricing. Charges follow the live event definitions shown below.

Event	Price (USD)	When it is charged
apify-actor-start	$0.00005	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
apify-default-dataset-item	$0.002	One unique public Working Nomads job written to the default dataset.

For example, 100 apify-default-dataset-item events cost $0.2, plus any enabled Actor-start event. Empty or failed work should be checked in the run log and dataset before reuse.

Reliability and limitations

Public websites and upstream APIs change over time. Start with a small result limit, inspect the dataset and run log, and keep a known-good input for scheduled canary runs. A valid query can return no records when the source has no matches. If a run is blocked, rate-limited, or missing an expected field, reduce concurrency or scope where the input supports it and include the run ID in a support report.

The Actor does not guarantee that every optional field is present on every record. Treat absent values as unavailable from that source response, not as proof that the real-world value does not exist.

Responsible use

Use this Actor only for data you are authorized to access. Follow the target website's terms, robots and access policies, and applicable privacy, database, copyright, anti-spam, and data-protection laws. Do not use it to bypass authentication or other access controls, collect private data, harass people, or make high-impact decisions without independent verification.

Frequently asked questions

Can I schedule Working Nomads Remote Jobs Scraper?

Yes. Use an Apify schedule to run the same saved input at a chosen interval, then connect a webhook or integration to process the dataset when the run finishes.

How should I test a new input?

Begin with the prefilled example or a small limit. Confirm that the output fields, source coverage, runtime, and live charges match your workflow before increasing the scope.

How do I export the results?

Open the run's default dataset in Apify Console and export JSON, CSV, Excel, XML, or RSS. Applications can retrieve the same records through the Apify API client or REST dataset endpoint.

Can an AI agent call this Actor?

Yes. Add muhammadafzal/working-nomads-scraper through the hosted Apify MCP server or call it through the API. The Actor's input and dataset schemas help agents construct valid requests and interpret returned records.