Workana Jobs Scraper

Workana Jobs Scraper: open freelance projects with budgets, proposal counts and client country

Give it a keyword, a Workana category or a search link, and it returns the open freelance projects that match, one row each. Every row carries the client's full brief, the budget bracket, fixed or hourly, how many freelancers have already sent a proposal, and the client's country and rating. The catch is coverage: Workana shows a signed-out visitor only part of each search, about 35 to 42% of what its own counter says, and the same part on every run.

🔍 What Workana Jobs Scraper does

Workana keeps three boards, English, Spanish and Portuguese, and a project sits on exactly one of them. They do not overlap. The same four pages returned 30 English projects and 32 Spanish ones with nothing in common, and the English board is by far the smallest. If you want volume, tick Spanish and Portuguese.

Each combination of language, category, subcategory and country runs as its own search, up to 200 in one run. maxItems is shared out across them, so three boards give you roughly a third each instead of the first one taking the lot. A project that turns up in two searches is kept once. Slicing like this is also how you reach more of the board, because every search stops at page 99.

Budgets are brackets. Workana asks clients to pick one rather than type an amount, so budgetMin and budgetMax are the bracket's edges, and an open-ended bracket leaves that side null: "Less than USD 50" gives budgetMin: null and budgetMax: 50. On an hourly project the numbers are per hour, and budgetUnit says so.

Dates are an age. Workana prints "5 hours ago", never a date, so postedAt is that age turned into a timestamp and postedAtPrecision tells you how far to trust it.

📥 What you give it

{
  "searchQuery": "wordpress",
  "languages": ["es", "pt"],
  "categories": ["it-programming"],
  "clientCountries": ["BR", "AR"],
  "maxProposals": 5,
  "maxItems": 200
}

Everything is optional, but a run needs something to search. Called through the API with an empty input, it writes one free sample row and stops.

projectType, the two proposal counts and postedWithinDays are applied after Workana answers, because the site has no filter of its own for them. Projects they drop never reach your dataset and are never charged. With one of them set, a search reads on until enough pass. It gives up after ten pages in a row with none, and a run where nothing passes stops within 25 pages; the status message says how many were read and passed.

📤 What you get back

A real row from a run on 27 September 2026, with the brief cut short:

{
  "projectId": "experienced-wordpress-developer-for-website-page-redesign-and-modernization",
  "title": "Experienced Wordpress Developer for Website Page Redesign and Modernization",
  "projectUrl": "https://www.workana.com/job/experienced-wordpress-developer-for-website-page-redesign-and-modernization",
  "description": "We are a UK-based company seeking an experienced WordPress developer to renew and modernize a specific existing page on ...",
  "category": "IT & Programming",
  "subcategory": "Wordpress",
  "projectDetails": {
    "Category": "IT & Programming",
    "Subcategory": "Wordpress",
    "What is the scope of the project?": "Custom development"
  },
  "skills": ["WordPress", "HTML", "CSS", "PHP", "Responsive Web Design", "User Interface", "Testing"],
  "skillSlugs": ["wordpress", "html", "css", "php", "responsive-web-design", "user-interface", "testing"],
  "projectType": "fixed",
  "budgetText": "USD 100 - 250",
  "budgetMin": 100,
  "budgetMax": 250,
  "budgetCurrency": "USD",
  "budgetUnit": "project",
  "proposalsCount": 45,
  "clientCountryCode": "GB",
  "clientCountry": "United Kingdom",
  "clientNameMasked": "R. S.",
  "clientRating": 0,
  "clientHasRating": false,
  "clientPaymentVerified": false,
  "clientPlan": null,
  "postedRelative": "22 hours ago",
  "postedAt": "2026-09-26T16:25:38.599Z",
  "postedAtPrecision": "hour",
  "isFeatured": false,
  "isUrgent": false,
  "projectLanguage": "en",
  "searchUrl": "https://www.workana.com/jobs?query=wordpress&language=en",
  "page": 1,
  "position": 1,
  "scrapedAt": "2026-09-27T14:25:38.599Z"
}

🧾 Reading the output

Three kinds of row can share the dataset. Only the first one costs anything.

Real project rows carry no charged field at all. The sample row has a projectId like a real one, so filter on the flags, not on projectId: drop any row with _sample or _diagnostic and what is left is the projects you paid for.

A diagnostic about one search names it in search, and one failed search does not stop the others.

▶️ How to run it

1. Open Workana Jobs Scraper and click Try for free. 2. Type what you are after into Keyword, or leave it empty for the newest projects. 3. Tick the boards you want under Project language. 4. Set Maximum projects. To narrow it, open Narrow the search or Filter the results. 5. Click Start, then download the dataset as JSON, CSV or Excel.

The form arrives with wordpress, English and 50 already filled in, so a run started without editing it is a real search.

💰 How much does it cost?

$1.80 per 1,000 projects, flat on every Apify plan. That is $0.0018 a project.

Not charged: the sample row, diagnostic rows, projects dropped by projectType, the proposal counts or postedWithinDays, and repeats. A project that turns up in two of your searches is charged once. If you set a maximum cost for the run, it stops when that is reached.

💡 What people use it for

• Finding projects few people have pitched on, with maxProposals. On a busy board those are mostly old posts: on

Spanish "wordpress" on 30 September 2026, 17 of the first 20 with 5 or fewer proposals were two months old or more.

• Pricing your own services against what clients actually budget, by category and client country.
• A daily feed of new projects in one category, with projectId to skip the ones you have already seen.
• Reading which skills clients ask for together, straight off skillSlugs.

🚧 What it does not do

• It does not return every project Workana counts. About 35 to 42% of each search, measured across nine searches in

September 2026, because Workana serves a signed-out visitor about 7 of the 20 projects on each page. This does not sign in.

• No client names or contact details. Workana shows initials to signed-out visitors, and that is all there is.
• No exact budgets. Workana only ever collects the bracket.
• No posting timestamp, only the age Workana prints, converted and labelled with its precision.
• No proposals, messages or freelancer profiles. Open projects only.
• No budget filter. Filter on budgetMin and budgetMax after you export.
• Nothing past page 99 of a single search. Workana stops serving there.

🧭 Which freelance scraper do you need?

❓ Questions people ask

Do I need a Workana account or an API key? No. It reads the same public board a signed-out visitor sees.

Why do I get fewer projects than the search says it found? Because Workana shows a signed-out visitor only part of each search while counting all of it. Tick more languages and add categories or countries to reach more.

Is postedAt accurate? To the hour on anything from the last day, to the day within a week, coarser after that. postedAtPrecision says which on every row.

Can I paste a search I built on the site? Yes. Copy the address bar into startUrls and the keyword, category, skills, country and language are read out of it.

Is scraping Workana legal? These are public project listings, and Workana masks client names itself. Apify's write-up on the legality of web scraping is a good starting point, and we are not lawyers.

🆘 If something breaks

Open the Issues tab on the actor page. Send the input you used and the run ID, and the errorCode on any diagnostic row.