🌍 Working Nomads Jobs Scraper - Remote Job Data

Scrape remote job listings from Working Nomads in one run. Get job titles, hiring companies, categories, tags, locations, publication dates, job URLs and cleaned descriptions from the public Working Nomads job feed. Export to JSON/CSV/Excel, run on a schedule, call via API, or connect to Make, Zapier or n8n.

🔎 What is the Working Nomads Jobs Scraper?

Working Nomads is a remote-job board focused on distributed work across software development, customer success, operations, marketing, management and other professional categories. This actor turns the public Working Nomads job feed into a structured dataset that can be used for recruiting, job aggregation, market research and lead generation.

The actor uses the public Working Nomads job API directly. It does not need a browser, account, proxy or API key, which makes it fast and suitable for scheduled monitoring.

What data does it extract?

• Job title - the public role title.
• Company - hiring company name.
• Category - Working Nomads job category.
• Tags - role tags and skills when exposed by the feed.
• Location - remote location text or timezone requirements.
• Published date - date when the listing was published.
• Job URL - direct Working Nomads listing URL.
• Description - cleaned HTML description, optional for smaller datasets.
• Remote flag - every row is marked as remote.
• Stable ID - extracted from the job URL for deduplication.

⬇️ Input

Field	Type	Description
keyword	string	Optional keyword filter matched against title, company, category, location, tags and description.
category	string	Optional category filter, for example development, marketing or customer success.
includeDescriptions	boolean	Include cleaned job descriptions in the output.
maxResults	integer	Maximum remote jobs to return.

Example input

{
  "keyword": "python",
  "includeDescriptions": true,
  "maxResults": 50
}

Filter by category:

{
  "category": "development",
  "maxResults": 100
}

⬆️ Output

Each dataset item is one remote job.

{
  "id": "1701460",
  "title": "Client Success Manager",
  "company": "Integrated Hire",
  "category": "Customer Success",
  "tags": ["customer success", "remote"],
  "location": "Remote",
  "is_remote": true,
  "published_date": "2026-07-02",
  "job_url": "https://www.workingnomads.com/job/go/1701460/",
  "description": "Position: Client Success Manager...",
  "description_short": "Position: Client Success Manager...",
  "source": "workingnomads"
}

💡 Use cases

• Remote-job aggregation - feed current Working Nomads roles into a jobs product or newsletter.
• Recruiting lead generation - identify companies actively hiring remote talent.
• Sales triggers - remote hiring can signal distributed-team tooling needs.
• Market research - track remote roles by category, company and publication date.
• Talent sourcing - monitor new remote openings matching a candidate profile.
• Automation - send new jobs to Airtable, Google Sheets, Notion, HubSpot, Make, Zapier or n8n.

🧭 How to use the data

Run the actor daily with a small maxResults value for monitoring, or increase it to collect the full current feed. Use id or job_url as the deduplication key in your database. If you only need new-job alerts, compare each run against the previous dataset and trigger workflows only for unseen IDs.

For broad remote hiring coverage, combine this actor with We Work Remotely, Remotive, RemoteOK, Jobicy, Greenhouse, Lever, Ashby, Workable and SmartRecruiters actors. Working Nomads is especially useful when you need a clean feed of curated remote roles rather than a broad general-purpose job search engine.

Descriptions can be long. Disable includeDescriptions if you only need lightweight lead records with title, company, category, tags, location and URL.

Because the source is remote-first, the dataset is also useful for tracking distributed-work demand by category. For example, you can monitor whether customer success, engineering, marketing or operations roles are appearing more often, then use those changes as recruiting, content or sales signals.

❓ FAQ

Does this require a Working Nomads account? No. It reads public job feed data.

Does it use a browser? No. The actor calls the public JSON feed directly.

Can I search by keyword? Yes. The keyword input filters across title, company, category, tags, location and description.

Can I filter by category? Yes. Use category for broad categories like development, marketing, management or customer success.

Are all jobs remote? Working Nomads is a remote-job board, and the actor marks every row with is_remote: true.

Does it include the full job description? Yes, when includeDescriptions is true. The actor also emits a short description preview.

Is this suitable for lead generation? Yes. Companies posting remote jobs are often actively growing distributed teams, making them useful prospects for recruiting, HR, payroll, collaboration and SaaS workflows.

How often should I run it? Daily is usually enough for monitoring new listings. Hourly runs are possible but rarely necessary.

Is it legal to scrape Working Nomads jobs? The actor collects publicly available job listings. You are responsible for using the output lawfully and respecting privacy, employment, anti-spam and platform rules.

How do I avoid duplicates? Use id or job_url as the stable key.

🔗 You might also like

• We Work Remotely Jobs Scraper
• Ashby Jobs Scraper
• Recruitee Jobs Scraper
• Workable Jobs Scraper
• SmartRecruiters Jobs Scraper
• StepStone Scraper

Keywords: Working Nomads scraper, Working Nomads jobs scraper, remote jobs scraper, scrape Working Nomads, remote job board API, remote hiring data, job postings scraper, recruitment leads, job board scraper, distributed teams, remote work data, remote developer jobs, hiring intelligence, recruiting automation, Apify jobs scraper.