Upwork Job Alerts: New Jobs Monitor & Filters
Pricing
from $0.42 / 1,000 job posts
Get alerts for new Upwork jobs: schedule it every few minutes or hours and each run returns only the job posts published since the last run, filtered by keyword, budget, hourly rate, experience level, skills and category. Send them to email, Slack or Google Sheets with Apify integrations.
Upwork search URLs copied from the site (https://www.upwork.com/nx/search/jobs/?q=python&sort=recency). Only the keyword, the sort and the page are read from the URL: filters ticked on Upwork's page are not, so set them below — they apply to these URLs too. When this list is not empty, Search keyword below is ignored; the caps and monitoring below still apply. Max 100 URLs.
[]Free-text search, exactly as typed on Upwork: the keywords you want alerts for. Upwork's own search syntax works: title:(web scraping), python AND NOT wordpress, "exact phrase". Empty = every open job post (about 108 000).
Several keywords in one run: one search per keyword. Added to Search keyword. A job post found by several searches is saved once. Max 100.
[]Maximum number of job posts to save in one run (after deduplication and filters). 0 = no limit. For an alert, keep it above the number of new job posts that appear between two runs: with Only new job posts on, the newest ones are returned first and the run stops at this number.
Cap for EACH search, so the first keyword cannot use up the whole Max job posts budget. 0 = no per-search cap. Upwork itself never returns more than 5 050 job posts for one search, whatever you set here.
Upwork's own sort order. recency (newest first) is the only one that makes Only new job posts and early stopping work — keep it for monitoring.
Return only the job posts never delivered by a previous run of the same search (same Monitoring key). The first run of a search has nothing to compare with: it returns the newest job posts, up to Max job posts. Untick it for a plain search that returns every match, every time. A run that finds nothing new saves 0 items and pays only the run-start fee.
Name of the memory used by Only new job posts. Leave empty: every search (its keywords or Start URLs) then gets its own memory, so two Tasks never hide each other's job posts, and changing the keywords starts a new alert. Type a name to keep one memory when you change the keywords or the filters of an alert, or to share it between several runs. Letters, digits, _ and - only.
Forget everything remembered under this Monitoring key (or under this search, when the key is empty) before starting, so this run returns every match again.
Hourly or fixed-price contracts. Empty = both.
Client's required level. Several can be ticked.
[]How long the client expects the work to last. Checked on every job post, fixed-price ones included.
[]Workload the client asks for. Hourly posts only: fixed-price posts have no hours per week, so they drop out unless a fixed budget is set too.
[]Only job posts the client flagged as leading to a long-term contract.
Only fixed-price job posts with a budget at or above this. Hourly posts drop out, unless an hourly rate or hours per week is set too: then you get both kinds, each matching its own filter.
Upper bound of the fixed budget. Can be used alone.
Only hourly job posts whose rate range reaches this. Fixed-price posts drop out, unless a fixed budget is set too: then you get both kinds, each matching its own filter.
Upper bound of the hourly rate. Can be used alone.
Upwork category names as shown on the site, e.g. Web, Mobile & Software Dev, Design & Creative, Sales & Marketing. The list of categories is read from Upwork at the start of the run, so it is never out of date. An unknown name stops the run with the list of valid ones.
[]Upwork subcategory names, e.g. Web Development, Data Extraction. More precise than Categories; both can be used together.
[]Skills the job post asks for, as Upwork names them, e.g. Python, Web Scraping, Graphic Design (case ignored). Several skills = the job post must ask for ALL of them. Each name is looked up on Upwork at the start of the run; an unknown name stops the run with the closest names Upwork knows.
[]How many freelancers the client has hired before.
[]Country names as Upwork writes them, e.g. United States, United Kingdom, Canada. Several countries = job posts from any of them.
[]The client's time zone, as Upwork names it, e.g. Europe/Paris, America/New_York, Asia/Calcutta. Several zones = job posts from any of them. A zone with no open job post right now is kept and said in the log.
[]Only job posts published on or after this date (days are UTC): 2026-09-01, or a period before now such as 7 days, 2 weeks, 1 month (API: 2 hours and full ISO date-times work too). With Sort by: Newest first, the run stops after 5 hours of older posts (Upwork ranks a few posts up to 3 hours before it publishes them), so a short window costs very little.
Only job posts published on or before this date (days are UTC; the whole day is included), or older than a period such as 30 days. Same formats as Posted after. Upwork shows only the 5 050 newest posts of a search (on all of Upwork, about the last 31 hours): to reach older ones, narrow the search with a keyword or a category.
Keep only job posts whose title, description or skills contain at least one of these words. Case and accents are ignored. Runs on our side, after Upwork's own search.
[]Drop job posts whose title, description or skills contain any of these words, e.g. wordpress, unpaid. Case and accents are ignored.
[]Cut each description to this many characters (never inside an emoji). 0 = keep the full text, which is what Upwork returns.
Adds 24 client columns (clientTotalSpent, clientHires, clientRating, clientCountry, applicantsCount…) and clientDetailsRead. Each job post delivered WITH its client's details is charged the Client details event on top of the job post; a job post whose page gives no client (private or closed job) goes out without them and is not charged for it. About 3 seconds per job post.
Proxy, included in the price. Keep the default setting: the Actor picks the IP addresses Upwork accepts. The Apify residential proxy is refused, because it would cost you money this Actor does not need. On the Apify free plan the included proxy is not available: add your own proxy URLs, or the run stops at once with a message.
{ "useApifyProxy": true}Milliseconds waited between two requests to Upwork. 500 ms is the measured safe pace (no refusal over 120 calls). Lowering it risks 403s; raising it only makes the run slower.
How many times a failed request is retried before it is listed as failed.