# Working Nomads Jobs Lookup — Remote Jobs by Category (`accountable_eel/workingnomads-jobs-lookup`) Actor

Search Working Nomads' live remote-jobs feed by category or keyword and get every matching posting — title, company, location, tags, apply link. Charged once per posting returned, never for a search with no matches.

- **URL**: https://apify.com/accountable\_eel/workingnomads-jobs-lookup.md
- **Developed by:** [Adrian Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.60 / 1,000 job posting returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Jobs Lookup — Remote Jobs by Category

Paste one or more categories or keywords and get every matching posting from
[Working Nomads](https://www.workingnomads.com)' live remote-jobs feed — title, company,
location, category, tags, posting date, description and a direct link. This reads the site's own
exposed jobs feed: no API key, no scraping of the rendered page.

### Who it's for

The accountable\_eel catalogue also covers remote-jobs feeds — actors that take a category or a
keyword rather than a company, and return every current posting that matches as one flat,
stably-named row. Each reads the board's own API rather than scraping rendered HTML, so the
columns don't move when the site is redesigned, and an AI agent or a Clay column that reads the
schema once keeps working. Pricing is pay-per-event and per posting: you pay for postings
actually returned, and nothing at all for a search that comes back empty. No seat licence, no
monthly minimum, no credit system to decode. This one covers the Working Nomads remote feed.

### Why this one

- **Reads the site's own feed, not a scrape.** No CSS selectors that break when the page is
  redesigned.
- **You don't pay for an empty search.** A term nothing matches comes back `found: false` and is
  never billed.
- **Category *or* keyword.** Your term is matched against category, tags, title and company, so
  `python` works as well as `development`.
- **Tags come parsed.** `tags` is a real array rather than a comma-separated string, so you can
  filter on it directly.
- **One row per search, or one per job.** Turn on `expandRows` when you want postings as their
  own rows for a table.

### What you get

One row per input term by default, with postings nested in `jobs`. Turn on `expandRows` to get
one row per posting. Field names are stable and won't be renamed between runs.

| Field | Type / format | Description |
|---|---|---|
| `query` | text | The term exactly as submitted. |
| `found` | boolean | Whether anything in the current feed matched. Gates billing — `false` rows are never charged. |
| `status` | text | `OK` or `NOT_FOUND` (nothing in the current feed matched). |
| `searchTerm` | text | The normalized term that was matched against the feed. |
| `jobCount` | number | Postings that matched this term. |
| `totalInFeed` | number | How many postings were in the feed at all — the denominator for `jobCount`. |
| `jobs` | array | The matching postings, each with the fields below. |
| `title` | text | Job title. |
| `company` | text | Hiring company name. |
| `categoryName` | text | Working Nomads' own category for the posting. |
| `tags` | array | Tags on the posting, split into separate entries. |
| `location` | text | Stated location or region requirement. |
| `postedAt` | date (ISO 8601) | Publication date from the feed. |
| `url` | link | The posting's page. |
| `description` | text | Posting description with HTML stripped, truncated to 2,000 characters. |
| `scrapedAt` | date (ISO 8601) | When this actor fetched the row. |

**This is a rolling window, not an archive.** The feed carries recent postings only, so
`totalInFeed` is the size of that window rather than everything Working Nomads has ever listed.
A term that returns nothing today may return results next week.

### Price

$1 per 1,000 job postings, plus a $0.005 start fee. Misses (`found:false`) are never charged.

You're billed per job posting actually returned, not per search term and not per run. A term
nothing matches costs nothing. A search returning 200 postings costs about $0.20 at the
FREE-tier rate, less on paid Apify plans. The start fee is per run, so batch your terms into one
run rather than running them separately.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `items` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~workingnomads-jobs-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"items":["development"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

1) Paste your categories or keywords into `items` — one per line.
2) Run the actor. Each term is matched against the current feed, in parallel up to
   `maxConcurrency`.
3) Turn on `expandRows` if you want one row per posting rather than postings nested per term.
4) Read the dataset. Empty searches are written as `found: false` rows and are never charged.

**Common ways teams use this:**

- **Build a niche remote-jobs board** by pulling a handful of categories on a schedule.
- **Track which companies hire remotely** in a discipline by grouping postings on `company`.
- **Watch a specific technology's demand** by using a skill keyword like `python` as the term.
- **Feed a candidate-matching pipeline** with `tags` already parsed into an array.
- **Monitor a category week to week** by re-running on a schedule and diffing on `url`.

### Input

```json
{
  "items": [
    "development"
  ]
}
```

One category or keyword per line, matched against the current Working Nomads feed's category, tags, title, and company — e.g. development, marketing, sales, design, python, customer-support. Accepted formats: development, marketing, python.

```json
{
  "items": ["development", "python"],
  "expandRows": false,
  "onlyFound": false,
  "maxConcurrency": 5
}
```

`items` is your list of categories or keywords. Each term is matched against the feed's
category, tags, title and company, so broad terms like `development`, `marketing` and `sales`
work alongside specific ones like `python` or `customer-support`. Turn on `testRun` to try a
small sample first. `expandRows` switches between one row per term and one row per posting.
`onlyFound` drops empty searches, `maxResults` stops the run early, `includeKeywords` and
`excludeKeywords` filter rows by content, and `columns` picks which fields come back — useful
for dropping `description`, which is by far the widest field.

### Sample output

| query | found | status | searchTerm | jobCount | totalInFeed | jobs | title | company | categoryName | tags | location | postedAt | url | description | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| development | true | OK | development | 27 | 43 | \<all postings found (full list)> | Senior QA Engineer | Lemon.io | Development | \["qa engineer","cypress","selenium","automation","english"] | Europe | 2026-08-25T06:43:33-04:00 | https://www.workingnomads.com/job/go/1814693/ | Are you a talented QA looking for a remote job that lets you show your skills and get better compensation and career growth? Look no further than Lemon.io - the marketplace that connects you with hand-picked startups in the US and Europe. We are seeking a Senior QA Engineer for our client — a B2B service provider in the gambling domain — for direct hire. The client is a B2B service provider based in Cyprus that specializes in building and managing technology and operational services for online businesses. The company provides the backend platform and operational infrastructure for iGaming, online casino, and gambling brands. We are looking for a detail-oriented and proactive QA Engineer who is passionate about quality and thrives in a fast-paced development environment. You'll play a key role in ensuring our products meet the highest standards by working across both manual testing and automation. Experience with tools like BrowserStack, TestRail, and Playwright (or willingness to grow into them) will help you succeed in this role. If you are a clear communicator who is proactive, takes ownership, collaborates well, and asks clarifying questions — and if you're comfortable working independently, managing your time effectively, and delivering high-quality results — please apply. Overlap: 8 hours with Cyprus (standard working day). Remote from the EU, or on-site in Limassol, Cyprus. Benefits: paid leave (available after 6 months of work) and an annual Christmas party trip. Requirements: 3+ years of experience in automation testing 2+ years of experience in manual testing 2+ years of experience working with Cypress, Playwright or Selenium Exceptional attention to detail Good command of English, both written and spoken. Strong organizational skills — ability to work full-time remotely with no supervision Responsibility — we want to trust you! Soft skills — we don’t ask you to find a topic for small talk, but being just polite is OK. NOT YOUR TECH STACK? We're placing Sen | 2026-08-26T06:01:14.253Z |

That table lists every available column. With `expandRows` on, a single posting reads like this:

```json
{
  "query": "development",
  "found": true,
  "status": "OK",
  "searchTerm": "development",
  "jobCount": 84,
  "totalInFeed": 512,
  "title": "Senior Python Engineer",
  "company": "Acme Remote",
  "categoryName": "Development",
  "tags": ["python", "django", "postgresql"],
  "location": "Europe",
  "postedAt": "2026-08-22T09:14:00Z",
  "url": "https://www.workingnomads.com/jobs/senior-python-engineer-acme",
  "description": "We're looking for a senior engineer to...",
  "scrapedAt": "2026-08-24T06:01:11.918Z"
}
```

A term nothing currently matches still returns a row, and is never charged:

```json
{
  "query": "underwater-basket-weaving",
  "found": false,
  "status": "NOT_FOUND",
  "message": "No jobs in the current feed match this term.",
  "scrapedAt": "2026-08-24T06:01:11.918Z"
}
```

Miss rows are written so you can see exactly which terms failed rather than diffing your input
list against the output. Set `onlyFound` to drop them.

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~workingnomads-jobs-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"items":["development"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~workingnomads-jobs-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"items":["development"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~workingnomads-jobs-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"items":["{{category or keyword search}}"]}`, mapping the row's category or keyword search into the `items` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Working Nomads Jobs Lookup | Apify" — the agent will find and run this actor.

### Tips

- **Read `jobCount` against `totalInFeed`.** It tells you whether your term is narrow or the
  feed itself is small that day.
- **Broaden the term before concluding nothing is hiring.** `development` will match where
  `senior golang engineer` won't — the match runs on category, tags, title and company, not on a
  full-text description search.
- **Drop `description` with `columns` on big runs.** It's truncated at 2,000 characters and is
  still the widest field by a wide margin.
- **Re-run on a schedule and diff on `url`** to catch new postings, since the feed is a rolling
  window rather than an archive.
- **Batch terms into one run.** The start fee is per run, so five terms in one run costs one
  start fee rather than five.

### vs. alternatives

| | What it costs | What you get | Trade-off |
|---|---|---|---|
| **This actor** (`workingnomads-jobs-lookup`) | $1 per 1,000 postings returned, $0.005 actor start, nothing for a term that matches nothing | Every current posting matching a category or keyword — company, location, category, parsed tags, date, description — as one flat row | Rolling window, not an archive. Matching runs on category, tags, title and company rather than full description text. |
| **automation-lab/working-nomads-jobs-scraper** (4 users) | $0.0000747 per item, $0.005 start | Substantially cheaper per posting for the same source | Roughly a thirteenth of the per-posting price here. If cost per row is your binding constraint, that's the cheaper tool. |
| **benthepythondev/remote-jobs-aggregator** (693 users) | $0.015 per result, $0.01 per salary extracted, $0.00005 start | Aggregates many remote boards at once rather than one, with salary extraction | Fifteen times the per-posting price, but far broader coverage. If you want the whole remote market rather than one board, that breadth is the point. |
| **Doing it yourself** | Your time + finding the feed, stripping HTML, splitting tags, retries | The same data | This actor absorbs the parsing and the retries and hands you a flat table. |

Competitor prices are their published FREE-tier list prices as of August 2026 and are not
tracked here — check the actor's own page before relying on the comparison.

### FAQ

**What terms work as input?**
Categories like `development`, `marketing`, `sales` and `design`, and keywords like `python` or
`customer-support`. Each is matched against the feed's category, tags, title and company.

**How am I billed?**
Per job posting actually returned. A term nothing matches costs nothing beyond the per-run start
fee.

**Why did my search return nothing?**
Either the term is too specific, or nothing in the current feed matches it. This reads a rolling
window of recent postings rather than a full archive, so try a broader term like `development`
before concluding the category is empty.

**Is `description` the full posting text?**
No — HTML is stripped and the text is truncated to 2,000 characters, which keeps rows usable in
a spreadsheet. Use `url` to reach the full posting.

**Can I look up a specific company?**
Only indirectly, by passing the company name as the term — it's matched against the company
field. For proper company-keyed lookups, use one of the ATS actors in this catalogue.

**Do I need a proxy?**
No. The feed is public and unauthenticated. `proxyConfiguration` is exposed if your own network
policy requires it.

**Can an AI agent call this directly?**
Yes — it's registered with the Apify MCP server. An agent with that MCP connected can find and
run "Working Nomads Jobs Lookup" by name and get dataset rows back with no integration code.

### Related actors

- [Jobgether Jobs Lookup](https://apify.com/accountable_eel/jobgether-jobs-lookup) — the same
  category-keyed shape for Jobgether's remote-jobs categories.
- [ATS Jobs Unified Lookup](https://apify.com/accountable_eel/ats-jobs-unified-lookup) —
  company-keyed lookups across Greenhouse, Lever, Ashby, Workable and more.
- [Greenhouse Jobs Lookup](https://apify.com/accountable_eel/greenhouse-jobs-lookup) — every open
  role on a specific company's Greenhouse board.

# Actor input Schema

## `items` (type: `array`):

One category or keyword per line, matched against the current Working Nomads feed's category, tags, title, and company — e.g. development, marketing, sales, design, python, customer-support. Accepted formats: development, marketing, python. You're only charged for the ones we actually find — a miss costs nothing.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

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

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each job posting found gets its own row instead of being grouped under its category or keyword search. You're still only charged once per category or keyword search, no matter how many rows it produces.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

## `proxyConfiguration` (type: `object`):

Apify Proxy config. Residential recommended for anti-bot-sensitive targets.

## Actor input object example

```json
{
  "items": [
    "development"
  ],
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "columns": [
    "searchTerm",
    "jobCount",
    "totalInFeed",
    "jobs",
    "title",
    "company",
    "categoryName",
    "tags",
    "location",
    "postedAt",
    "url",
    "description"
  ],
  "expandRows": true,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (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 = {
    "items": [
        "development"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/workingnomads-jobs-lookup").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 = {
    "items": ["development"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/workingnomads-jobs-lookup").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 '{
  "items": [
    "development"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/workingnomads-jobs-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/workingnomads-jobs-lookup"
        }
    }
}

```

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/uDF5zWyXX5ahilmAy/builds/P4YpM33eBp6WujzXv/openapi.json