# Working Nomads Remote Jobs Scraper (`muhammadafzal/working-nomads-scraper`) Actor

Extract public Working Nomads remote jobs for recruiting, job discovery, market research, and AI agents. Returns titles, companies, categories, tags, locations, dates, descriptions, URLs, and provenance. Public feed only; no login or applications.

- **URL**: https://apify.com/muhammadafzal/working-nomads-scraper.md
- **Developed by:** [Muhammad Afzal](https://apify.com/muhammadafzal) (community)
- **Categories:** Other, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 remote job returneds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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

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

### Run Working Nomads Remote Jobs Scraper with the Apify API

```javascript
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.

# Actor input Schema

## `searchQueries` (type: `array`):

Filter public remote jobs when the title, company, category, location, tags, or description contains any term. Example: \["typescript", "product manager"]. Leave empty for all jobs.

## `locations` (type: `array`):

Filter by a location substring such as "Worldwide", "Europe", or "United States". Leave empty for all locations.

## `categories` (type: `array`):

Filter by Working Nomads category names such as Development, Design, or Marketing. Leave empty for all categories.

## `tags` (type: `array`):

Filter by a job tag such as python, sales, or SEO. Leave empty for all tags.

## `startUrls` (type: `array`):

Optional Working Nomads /jobs or /api/exposed\_jobs/ URLs. The actor uses the public exposed jobs feed; omit this for the default feed.

## `maxResults` (type: `integer`):

Maximum unique jobs to write, from 1 to 500. Default: 50.

## `maxRequestRetries` (type: `integer`):

Retries for transient source errors, from 0 to 5. Default: 2.

## `includeDescriptionHtml` (type: `boolean`):

Also return the source HTML description alongside the cleaned text description. Default: false.

## Actor input object example

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

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("muhammadafzal/working-nomads-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("muhammadafzal/working-nomads-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call muhammadafzal/working-nomads-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,muhammadafzal/working-nomads-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/4bJlwlHxqKMPEXUQ5/builds/0OJfBGWF1h1fAxHtQ/openapi.json