JobsFlow avatar

JobsFlow

Pricing

from $0.01 / 1,000 results

Go to Apify Store
JobsFlow

JobsFlow

The most comprehensive remote job scraper on Apify. This Actor aggregates and de-duplicates thousands of remote tech job postings from multiple high-quality sources, providing you with a clean, structured dataset in a single run.

Pricing

from $0.01 / 1,000 results

Rating

0.0

(0)

Developer

Silicate Labs

Silicate Labs

Maintained by Community

Actor stats

0

Bookmarked

66

Total users

2

Monthly active users

6 days ago

Last modified

Features

Limited permissions

Share

What does JobsFlow do?

JobsFlow collects fresh remote jobs from 8 job boards in one run and gives you one clean, de-duplicated list with salaries, job types and locations in the same format, whatever board they came from.

Job boardWhat it adds
HimalayasLarge remote board, salaries on many jobs, supports keyword search
JobicyRemote jobs with structured salary and seniority
RemoteOKPopular tech and startup remote jobs
We Work RemotelyOne of the largest remote-only boards, all categories
RemotiveCurated remote tech jobs
ArbeitnowEurope-focused jobs (remote and on-site)
Working NomadsCurated remote jobs
Hacker News "Who is hiring?"This month's startup hiring thread, parsed into structured jobs

A typical run takes 15 to 40 seconds, returns jobs posted in the last 30 days, and needs no proxies or login.

Why use JobsFlow?

  • Job alerts. Schedule it daily with Only jobs I haven't seen yet turned on, and connect Slack, email, Google Sheets or Make. You get only new postings each time.
  • Job boards and newsletters. Feed a niche board ("remote Rust jobs", "remote jobs in LATAM") from 8 sources at once.
  • Market research. Track which technologies, salaries and companies are hiring remotely.
  • AI agents. Clean JSON with plain-text descriptions, ready for LLM matching or summaries.

How to use it

  1. Click Try for free.
  2. Add search terms (e.g. python developer, "machine learning" engineer), or leave them empty for all jobs.
  3. Optionally narrow by tech stack, locations (e.g. worldwide, usa, europe), job type, minimum salary or posted within N days.
  4. Click Start and download the results as JSON, CSV, Excel or HTML, or get them through the API.

Get only new jobs on a schedule

Turn on Only jobs I haven't seen yet and save the input as a task, then add a schedule (e.g. every morning). Each run returns only jobs that earlier runs of that task have not already returned. The same job reposted on another board counts as already seen too. Use a different Memory key for each task so they keep separate histories.

Input example

{
"searchQueries": ["python developer", "data engineer"],
"techStack": ["aws", "django"],
"locations": ["worldwide", "europe"],
"jobTypes": ["full_time", "contract"],
"postedWithinDays": 14,
"maxJobs": 200,
"onlyNewJobs": true,
"stateKey": "python-eu"
}

How matching works: a job matches if it matches any search term, and every word of that term appears in the job (whole words only, so go does not match "Google"). Put a phrase in quotes to match it exactly. By default terms are searched in the title and tags; set Match search terms in to Everywhere to include the full description.

Output example

{
"id": "49f905f1f911138b98af",
"title": "Senior Backend Engineer (Python)",
"company": "Acme",
"companyLogo": "https://cdn-images.himalayas.app/....png",
"location": "Worldwide",
"isRemote": true,
"jobTypes": ["full_time"],
"seniority": "Senior",
"category": "Engineering",
"tags": ["python", "aws", "django"],
"salary": "USD 140,000 - 180,000 / year",
"salaryMin": 140000,
"salaryMax": 180000,
"salaryCurrency": "USD",
"salaryPeriod": "year",
"postedAt": "2026-11-14T16:07:57+00:00",
"expiresAt": "2027-01-14T01:38:53+00:00",
"url": "https://himalayas.app/companies/acme/jobs/senior-backend-engineer",
"applyUrl": "https://himalayas.app/companies/acme/jobs/senior-backend-engineer",
"source": "himalayas",
"sourceJobId": "…",
"alsoPostedOn": [{ "source": "remoteok", "url": "https://remoteok.com/remote-jobs/…" }],
"description": "Plain-text job description…",
"scrapedAt": "2026-11-15T01:55:26+00:00"
}
  • id stays the same across runs and boards, so you can use it as a primary key.
  • alsoPostedOn lists the other boards where the same job appeared. The duplicates are merged, and missing fields (salary, logo, location) are filled in from them.
  • salaryMin / salaryMax / salaryPeriod are numbers parsed from structured data or free text such as $35k - $52k or €5,000/month.
  • description can be plain text, HTML, both or left out (Job description setting).

Every run also saves a summary in the run's key-value store under OUTPUT: how many jobs came from each board, the time each board took, duplicates merged, and any board that was unavailable.

How much does it cost?

You pay a small fee per job returned, shown on the Pricing tab, plus minimal platform usage. Most runs finish in under 40 seconds on 512 MB of memory. Set Max jobs or a maximum cost per run to cap your spend. The Actor stops cleanly when the limit is reached.

Good to know

  • Reliability: each board is fetched independently with retries. If one board is down, you still get results from the others, and the run summary names the board that failed.
  • Freshness: Remotive asks API users to fetch at most a few times a day, so JobsFlow caches Remotive (6 h) and the monthly Hacker News thread (3 h) between runs. All other boards are fetched live on every run.
  • Attribution: these boards share their jobs on the condition that you link back to them. Every job includes its source and original url. Please keep those links when you republish jobs.
  • Remote only: on by default. Turn it off to include on-site and hybrid jobs from Arbeitnow and Hacker News.

FAQ

Can I add another job board? Open an issue on the Issues tab with the board's name. Boards with a public API or feed are added first.

Is this legal? JobsFlow only uses the public APIs and feeds that these boards publish for sharing their jobs, and it keeps their attribution. If you republish jobs, follow each board's terms.

The field names changed from version 0.x. Version 1.0 uses camelCase (postedAt instead of posted_at). The old inputs searchKeywords and comma-separated techStack still work.