Remote Jobs Scraper - RemoteOK, Himalayas & WWR ($1.50/1K)

For job-alert bots, remote-job newsletter writers, recruiters and job-board sites who need one clean feed instead of four. One run pulls current remote listings from RemoteOK, Himalayas, Jobicy and We Work Remotely, normalises them into a single flat schema, merges cross-posted duplicates, and filters by keyword, recency, location and salary. Turn on job alerts mode (onlyNewSinceLastRun) and run it on a schedule to get billed only for genuinely new listings each time. Pay-per-result: $0.0015 per job — 1,000 jobs = $1.50. Try it free with Apify's monthly platform credit.

This Actor exists because a "remote python jobs" search touches four different sites with four different formats. This Actor is the merge step: one request, one schema, no duplicates.

Quick start (1 minute)

Open the Input tab and use this prefill (swap in your own keywords):

{
  "keywords": ["python"],
  "postedWithinDays": 7,
  "maxItems": 20
}

Click Start. It finishes in a few seconds. Export the dataset to CSV/JSON, or pull it through the API shown below.

Use cases

• Job-alert bots polling on a schedule for new listings matching a keyword set, then posting to Slack/Discord/email.
• Remote-job newsletter writers pulling a fresh, de-duplicated shortlist every week without visiting four sites.
• Recruiters and sourcers scanning what's currently open across boards for a given skill or location.
• Job-board and aggregator sites backfilling or supplementing their own listings with a normalised external feed.

Job alerts: get only new jobs

Turn on onlyNewSinceLastRun and put this Actor on a schedule for a real job alert: every run after the first delivers (and charges for) only jobs it hasn't delivered before for that exact search — cross-posted duplicates are still recognised even if a job moves between boards between runs, using the same company+title identity as the dedupe above.

1. Set your keywords/filters as usual, plus:

{
  "keywords": ["python"],
  "onlyNewSinceLastRun": true,
  "maxItems": 50
}

2. Click Schedule on the run page (or create one under Schedules in the Apify Console) — daily is typical for an active search.
3. The first scheduled run is a baseline: it delivers every job currently matching (it's all new to you) and remembers it — you're charged normally for that run. Every run after that only delivers jobs it hasn't seen before for this exact search.
4. Add a Webhook under the schedule's Integrations for ACTOR.RUN.SUCCEEDED, pointing at:
   • Slack: Apify's own Slack integration (or a Zapier/Make webhook step) posting each run's new dataset items to a channel.
   • Email: a Zapier/Make "on webhook, send email" step, or Apify's own email integration, summarising that run's new jobs.
   • Google Sheets: the Apify-to-Google-Sheets integration, appending each run's rows to a sheet you watch.

The run's status message tells you what happened: "First run: 12 job(s) delivered and remembered; next runs return only new ones." on the baseline, then "2 new job(s) since last run (10 already seen)." on later runs. A run that finds nothing new still succeeds with an empty dataset — that's the point of the mode, not a failure.

Each distinct combination of keywords/excludeKeywords/sources/postedWithinDays/locationContains/worldwideOnly/minSalary/includeUnknownSalary is tracked as its own watch, so several alert schedules (e.g. one per keyword set) don't mix up each other's history. stateStoreName only needs changing if you want to reset a watch's memory or explicitly isolate it.

Get new remote job alerts in Discord, Telegram, Slack, Teams, Google Chat, your phone (ntfy/Pushover) or any app (webhook)

Want a remote job alert in Discord, Telegram or on your phone instead of checking a dataset? Add one or more destinations in the Actor's Notifications (optional) section and each run sends the jobs it delivered. It is a monitor that notifies you: it only reads the public RemoteOK, Himalayas, Jobicy and We Work Remotely feeds, and it never applies to a job, contacts an employer or logs in anywhere.

Channel	Fill in	What you get
Discord	discordWebhookUrl	One card per job, 10 per message
Telegram	telegramBotToken + telegramChatId	Up to 10 jobs per message, one line each
Slack	slackWebhookUrl	Block Kit message, up to 10 jobs per message
Mattermost, Rocket.Chat	slackCompatibleWebhookUrl	Slack-style incoming webhook: a Markdown list (these apps do not render Slack Block Kit)
Microsoft Teams	teamsWebhookUrl	Adaptive Card from a Teams Workflows webhook, up to 10 jobs per card
Google Chat	googleChatWebhookUrl	Card in a space, up to 10 jobs per message
ntfy (phone push, no account)	ntfyTopic (optional ntfyServer, ntfyToken)	A push per job, up to 10, then one "...and N more"
Pushover (phone push)	pushoverUserKey + pushoverAppToken	A push per job, up to 10, then one "...and N more"
Any app: Zapier, Make, n8n, Pipedream, IFTTT, Home Assistant	webhookUrl	One JSON POST per run with every delivered row

Fill in as many as you like; each channel works on its own and a failing one never stops the others.

Setup, channel by channel

• Discord (1 minute): Server Settings → Integrations → Webhooks → New Webhook → pick the channel → Copy Webhook URL.
• Telegram (2 minutes): chat with @BotFather, send /newbot, paste the token into telegramBotToken. Add the bot to the chat or channel (administrator for a channel; for a chat with yourself press Start on the bot). telegramChatId is a numeric id (123456789, or -1001234567890 for a group or channel) or a public @channelusername.
• Slack: at api.slack.com/apps create an app (From scratch) → Incoming Webhooks → switch it on → Add New Webhook to Workspace → pick the channel → copy the https://hooks.slack.com/services/... URL.
• Mattermost or Rocket.Chat: create an incoming webhook in the app and paste its public https:// URL into slackCompatibleWebhookUrl. It must be reachable from the internet: localhost, private IP addresses and .local / .internal names are rejected.
• Microsoft Teams: in the channel open ... → Workflows → Post to a channel when a webhook request is received → finish the wizard and copy the URL (a host ending in .logic.azure.com or .powerplatform.com). The old "Office 365 connector" webhooks are retired and not supported.
• Google Chat: in the space open Apps & integrations → Webhooks → Add webhook, name it and copy the https://chat.googleapis.com/v1/spaces/... URL (needs a Google Workspace account that allows webhooks).
• ntfy (free, no account): install the ntfy app (or open ntfy.sh), subscribe to a topic with a long random name, and put the same name in ntfyTopic. Anyone who knows the topic can read it, so make it unguessable. Own server or a protected topic: set ntfyServer (public https:// address) and ntfyToken.
• Pushover: copy your user key from pushover.net into pushoverUserKey, create an application at pushover.net/apps/build and put its API token in pushoverAppToken. Pushover itself is a separate paid app after its trial: check their pricing.
• Any app (webhook): paste the catch-hook URL from Zapier, Make, n8n, Pipedream, IFTTT or Home Assistant into webhookUrl. It must be a public https:// address.

The recipe: a remote job alert in five steps

1. Set your keywords (and any worldwideOnly, minSalary or locationContains filters).
2. Turn on onlyNewSinceLastRun.
3. Add your destination(s) from the table above.
4. Run it once. The first run is the baseline and sends the jobs currently matching (up to maxNotifications).
5. Create a Schedule (daily is typical; remote boards post all day, so every few hours also works). From then on you only hear about jobs it has not delivered before.

{
  "keywords": [
    "python"
  ],
  "worldwideOnly": true,
  "onlyNewSinceLastRun": true,
  "maxItems": 50,
  "discordWebhookUrl": "https://discord.com/api/webhooks/<id>/<token>",
  "ntfyTopic": "your-long-random-topic-name",
  "maxNotifications": 25
}

The generic webhook (webhookUrl)

Each run sends one POST per 100 delivered rows (so usually one) with this body, followed by whatever your tool does with it:

{
  "source": "apify",
  "actor": "remote-jobs-aggregator",
  "runId": "HG7ML7M8z78YcAPEB",
  "count": 2,
  "total": 2,
  "part": 1,
  "parts": 1,
  "items": [
    {
      "...": "the full dataset rows"
    }
  ]
}

count is the number of rows in this POST, total the number delivered in the run, and part / parts number the POSTs when a run delivers more than 100 rows. maxNotifications does not cap the webhook: your tool gets every delivered row. Your endpoint should answer with a 2xx status; redirects are not followed and a failure is reported in the run status, never retried in a loop.

What each message contains

Each job is announced as New job: <title> at <company> — <location> (Worldwide for jobs open to applicants anywhere) with the link, the stated salary range when the board published one, the employment type, posting date, up to five tags, the other boards the job was also posted on, and the company logo where the channel can show one. Anything the board does not publish is left out. Discord gets a card per job, Telegram one line per job, Slack Block Kit sections, Teams an Adaptive Card, Google Chat a card, and ntfy/Pushover a push that opens the job. Link previews are off, and titles are escaped so a title can never inject formatting or mentions.

What to expect

• Only delivered jobs are sent. A run that finds nothing new sends nothing, so there is no "no new jobs" spam. Rows the run could not deliver (for example because your spending limit was reached) are not sent.
• Without onlyNewSinceLastRun, every delivered row is sent, so a scheduled plain run would repeat the same jobs: use alert mode for alerts (the message then says "New job"; a plain run says "Job").
• maxNotifications (default 25, max 100) caps how many jobs go to chat and phone channels per run (the webhook is not capped). The rest are still in the dataset and the status message says so. ntfy and Pushover send at most 10 individual pushes, then one "...and N more" summary.
• Cost: notifications are free. You pay only the usual price for delivered jobs, exactly as without alerts. There is no extra charge for any channel.
• Failures never fail the run. A deleted webhook or an unreachable service leaves the run successful and the dataset complete, and the status message says what happened, for example Notified: Discord 12, Slack 12, ntfy 10 (+summary). Teams failed (HTTP 404) - check the webhook URL. The logs show the channel name and HTTP status only, never a URL or token.
• Your URLs, tokens and ntfy topic are stored as secret inputs. Anyone holding a webhook URL can post to that channel, so treat it like a password.
• It is a monitor that notifies you. It never applies to jobs, contacts employers or logs in to any job board. The messages go only to the destinations you set up.
• Nothing changes by default. With no destination set, a run behaves exactly as before and the dataset rows are identical.

Input

{
  "keywords": ["python"],
  "excludeKeywords": [],
  "sources": ["remoteok", "himalayas", "jobicy", "wwr"],
  "postedWithinDays": 7,
  "locationContains": "",
  "worldwideOnly": false,
  "minSalary": null,
  "includeUnknownSalary": true,
  "maxItems": 20,
  "includeFullDescription": false,
  "onlyNewSinceLastRun": false,
  "stateStoreName": "remote-jobs-aggregator-seen-jobs"
}

Field	Type	Default	Description
keywords	string[]	[] (all)	Keep jobs whose title, tags or description match ANY of these words (case-insensitive)
excludeKeywords	string[]	[]	Drop jobs matching ANY of these words
sources	string[]	all 4	remoteok, himalayas, jobicy, wwr — any subset
postedWithinDays	integer	7	1–90. Jobs with no parseable posting date are kept regardless
locationContains	string	—	Case-insensitive substring match on location. Ignored if worldwideOnly is on
worldwideOnly	boolean	false	Only jobs open to applicants anywhere (isWorldwide: true)
minSalary	integer	—	Keep only jobs whose stated salary (min or max, whichever is higher) meets this. Currency-naive — see Limitations
includeUnknownSalary	boolean	true	With minSalary set, whether to still keep jobs that state no salary
maxItems	integer	50	1–1000. Hard cap on jobs delivered — this is your cost cap
includeFullDescription	boolean	false	Off truncates descriptionText to 2000 characters
onlyNewSinceLastRun	boolean	false	Job alerts mode — see above. Delivers and charges only jobs not delivered by a previous run of the same search
stateStoreName	string	remote-jobs-aggregator-seen-jobs	Name of the store that remembers what a job-alerts search has already delivered. Change it only to isolate or reset a watch
discordWebhookUrl	string (secret)	(none)	Discord webhook URL. Must look like https://discord.com/api/webhooks/<id>/<token>. Empty means no Discord messages. See the alerts section above.
telegramBotToken	string (secret)	(none)	Telegram bot token from @BotFather. Needs telegramChatId.
telegramChatId	string	(none)	Telegram chat to post to: a numeric chat id or @channelusername. The bot must be added to that chat or channel. Needs telegramBotToken.
slackWebhookUrl	string (secret)	(none)	Slack incoming webhook, https://hooks.slack.com/services/....
slackCompatibleWebhookUrl	string (secret)	(none)	Mattermost / Rocket.Chat incoming webhook (public https:// URL; Markdown list, no Block Kit).
teamsWebhookUrl	string (secret)	(none)	Microsoft Teams Workflows webhook (host ending .logic.azure.com or .powerplatform.com).
googleChatWebhookUrl	string (secret)	(none)	Google Chat space webhook, https://chat.googleapis.com/v1/spaces/....
ntfyTopic	string (secret)	(none)	ntfy topic name; setting it turns ntfy phone pushes on. Pick a long, unguessable name.
ntfyServer	string	https://ntfy.sh	ntfy server. Only change it for your own public https:// ntfy server.
ntfyToken	string (secret)	(none)	Optional ntfy access token for a self-hosted server or protected topic. Needs ntfyTopic.
pushoverUserKey	string (secret)	(none)	Pushover user key. Needs pushoverAppToken.
pushoverAppToken	string (secret)	(none)	Pushover application API token. Needs pushoverUserKey.
webhookUrl	string (secret)	(none)	Generic JSON webhook (Zapier, Make, n8n, Pipedream, IFTTT, Home Assistant): every delivered row, 100 per POST. Public https:// only.
maxNotifications	integer	25	1–100. Most jobs sent to chat and phone channels per run (the webhook is not capped). Extra jobs are still in the dataset. Only used when a destination is set.

For most users, only keywords and maximum jobs matter — the defaults handle the rest.

Output fields

Category	Fields
Identity	id, source, duplicateOf, alsoPostedOn
Job	title, company, companyUrl, companyLogo, employmentType, tags
Links	url, applyUrl
Timing	postedAt
Location	location, isWorldwide
Salary	salaryMin, salaryMax, salaryCurrency
Description	descriptionText

Missing values are returned as null rather than guessed.

Output example

{
  "id": "remoteok:1137421",
  "title": "Senior Backend Engineer (Python)",
  "company": "Acme Robotics",
  "companyUrl": null,
  "companyLogo": "https://remoteok.com/assets/logo.png",
  "source": "remoteok",
  "url": "https://remoteok.com/remote-jobs/senior-backend-engineer-python-acme-robotics-1137421",
  "applyUrl": "https://remoteok.com/remote-jobs/senior-backend-engineer-python-acme-robotics-1137421",
  "postedAt": "2026-09-24T16:00:06.000Z",
  "location": "Germany",
  "isWorldwide": false,
  "employmentType": null,
  "salaryMin": 70000,
  "salaryMax": 80000,
  "salaryCurrency": "USD",
  "tags": ["python", "backend", "senior"],
  "descriptionText": "We are looking for a Senior Backend Engineer...",
  "duplicateOf": null,
  "alsoPostedOn": [
    { "source": "himalayas", "url": "https://himalayas.app/companies/acme-robotics/jobs/senior-backend-engineer" }
  ]
}

Cross-posting dedupe

Many roles are posted to more than one board word-for-word. Jobs are grouped by normalised company + title; only the first one seen is delivered (and charged for) — the rest are merged into its alsoPostedOn list, so a cross-posted job is never billed twice. duplicateOf is always null on delivered rows: it is reserved for a possible future partial-dedupe mode and does nothing yet.

Use it as an API

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")

run = client.actor("lukehunter/remote-jobs-aggregator").call(
    run_input={"keywords": ["python"], "postedWithinDays": 7, "maxItems": 50}
)

for job in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(job["title"], job["company"], job["url"])

Use Apify schedules to poll on a cadence for a job-alert bot, and webhooks to push new results into Slack, Discord or email.

Pricing and cost control

This Actor uses pay per delivered job.

Current configured rate: $0.0015 per job delivered. Check the Apify Pricing tab for the latest published rate.

Jobs delivered	Cost at $0.0015/job
20	$0.03
100	$0.15
1,000	$1.50

There is no charge for merely starting a run, and no charge for a job dropped by filtering or dedupe. maxItems gives you a clear upper bound on the number of billable jobs.

Notifications to Discord, Telegram, Slack, Teams, Google Chat, ntfy, Pushover and webhooks are free: you pay only for delivered jobs, never for messages sent.

Reliability

• A failure fetching one source (site down, format changed) is logged and the run continues with the other three — it never fails the whole run over one board. Which sources failed is recorded in the run's key-value store under OUTPUT.
• The run only fails outright if every requested source failed to fetch — a narrow keyword/location/salary filter that matches nothing is a normal, successful, empty result.
• descriptionText is plain text (HTML stripped), truncated to 2000 characters by default.

Important limitations

• RemoteOK: its public API returns one fixed page of its current ~100 most recent listings — there is no further pagination to request.
• Himalayas: paginated up to 10 pages (up to ~1,000 jobs) per run to bound runtime; increasing maxItems beyond that will not pull more from Himalayas alone.
• Jobicy: requested in a single page, capped at 50 jobs per run from this source (Jobicy's own documented ceiling for one request).
• We Work Remotely: only the single combined feed (weworkremotely.com/remote-jobs.rss) is read, not the per-category RSS feeds.
• Salary comparisons are currency-naive. minSalary compares raw numbers regardless of salaryCurrency — no FX conversion is performed.
• postedWithinDays cannot filter a job whose source did not publish a usable date; such jobs are kept rather than guessed away.
• Descriptions, salaries and locations are exactly what each source publishes — this Actor does not verify a listing is still live or accurate.
• RemoteOK attribution: per RemoteOK's API Terms of Service, every RemoteOK-sourced row keeps its url linking back to the RemoteOK job page and source: "remoteok" naming RemoteOK — please preserve these if you republish RemoteOK-sourced listings.
• This is an independent aggregator and is not affiliated with, endorsed by, or connected to RemoteOK, Himalayas, Jobicy or We Work Remotely. Each is a trademark of its respective owner.

Use it from your code, Make, Zapier or n8n

Built for automated pipelines: small runs, stable field names, one row per item, and you pay only for rows actually delivered.

One API call that runs the Actor and returns the data (replace $APIFY_TOKEN with your token from Apify Console → Settings → Integrations):

curl -s -X POST "https://api.apify.com/v2/acts/lukehunter~remote-jobs-aggregator/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"keywords": ["engineer", "developer"], "postedWithinDays": 14, "maxItems": 20}'

JavaScript (npm i apify-client):

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('lukehunter~remote-jobs-aggregator').call({
  "keywords": [
    "engineer",
    "developer"
  ],
  "postedWithinDays": 14,
  "maxItems": 20
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Python (pip install apify-client):

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('lukehunter~remote-jobs-aggregator').call(run_input={"keywords": ["engineer", "developer"], "postedWithinDays": 14, "maxItems": 20})
items = client.dataset(run['defaultDatasetId']).list_items().items

Schedules, webhooks and no-code tools: save your input as a Task, add a Schedule (e.g. hourly or daily), and attach a webhook or one of the Integrations tab's connectors (Make, Zapier, n8n, Google Sheets, Slack) to push each run's results into your own system.

Only new items each run: set "onlyNewSinceLastRun": true on a scheduled Task and every run after the first delivers, and charges for, only items it hasn't delivered before for that same input. That makes it a ready-made change feed.

Reliability: an automated test runs this Actor's parser against the live site every day, and failures are fixed fast.

Feedback: an honest rating on the Store page, good or bad, helps others decide if this Actor fits their needs. Missing a field or found a problem? Open an issue on the Actor page.

FAQ

Does this bypass any login, CAPTCHA or paywall?

No. All four sources are public, unauthenticated feeds intended for programmatic access (three JSON APIs, one RSS feed). No personal data is collected — only public job listings.

Why is a job I saw on RemoteOK also on Himalayas in the results?

It's the same listing, merged. See "Cross-posting dedupe" above — check alsoPostedOn on the delivered row.

Can I get only fully remote/worldwide jobs?

Yes — set worldwideOnly: true.

Can I run this on a schedule for job alerts?

Yes — set onlyNewSinceLastRun: true, create an Apify Schedule with your keyword input, and use a webhook or integration to forward new dataset items to Slack/Discord/email. See "Job alerts" above. The first scheduled run delivers everything (and remembers it); later runs only deliver, and charge for, what's new.

Can I get remote job alerts in Discord, Telegram, Slack or on my phone?

Yes. Set discordWebhookUrl, telegramBotToken + telegramChatId, slackWebhookUrl, teamsWebhookUrl or googleChatWebhookUrl, or use ntfyTopic (free, no account) or pushoverUserKey + pushoverAppToken for phone pushes. Mattermost and Rocket.Chat work through slackCompatibleWebhookUrl. With onlyNewSinceLastRun on and a schedule, each run sends only the jobs it has not delivered before; a job cross-posted on several boards is announced once. Setup steps for each are in the alerts section above. Notifications cost nothing extra.

Can I get remote job alerts by email?

Not natively. There are two routes. (1) Set webhookUrl to a Zapier, Make or n8n catch hook and add an email or Gmail step: the webhook delivers every row as JSON, so the email can list the jobs. (2) Apify's own run integrations and run notifications can email you when a run finishes, but they only send a link to the run or dataset, not the jobs themselves. For instant alerts without building anything, Telegram, ntfy or Pushover reach your phone directly.

Can I get remote job alerts in WhatsApp?

Not natively, and we do not use unofficial WhatsApp APIs, which risk getting your number banned. The official route is the WhatsApp Business Platform (Cloud API) with its own business account, message templates and pricing: point webhookUrl at a Zapier, Make or n8n flow that calls it. For free phone alerts use Telegram or ntfy instead.

Related Actors

Other data tools from the same developer, built to the same standard: official or public sources, hard cost caps, and honest documentation of limits.

• Wellfound (AngelList) Jobs Scraper: startup jobs from Wellfound with salary ranges, equity and company stage.
• Greenhouse Jobs Scraper & Job Alerts: jobs from many Greenhouse careers boards with filters and new-job alerts.
• YouTube Channel Scraper: new-video alerts and channel monitoring for any list of YouTube channels: subscribers, latest videos and a new-uploads-only mode for scheduled runs.
• Google Play App Scraper: ratings, installs, developer contact info and pricing for any Google Play app.
• Apple App Store Reviews Scraper: Apple App Store reviews for any iOS app, across countries, with rating, version and date.
• Spotify Scraper: play counts, monthly listeners and playlist track lists for any public Spotify artist, playlist, album or track.
• Shopify Product Scraper by URL: price, compare-at price and stock for specific Shopify product URLs, with a change-only feed.
• Walmart Category Scraper: product names, prices, was-prices and ratings from Walmart category pages.