Workana Scraper - LatAm Freelance Projects

Extracts freelance projects published on Workana, Latin America's largest freelance marketplace (Argentina, Brazil, Mexico, Chile, Colombia, Peru and more). Each project comes with its budget, skills, category and full description, output in the same unified field names (datePosted, salaryMin, employmentType...) shared by every job and freelance-mission actor from this author, so it drops straight into a pipeline already built for one of the others.

What you get	Open projects from Workana: title, budget, skills, category, client country and full description.
Price	$2.00 per 1,000 projects: a 50-project test run costs about $0.11, start fee included.
Speed	50 projects in under a minute. No login, no browser to configure for a default run.
Try it	Click Try for free: the default input already returns 50 of the most recent projects across every country.
Keep it fresh	Schedule it daily and keep only the new projects: turn on Only new results.

What you can do with it

• Find freelance work: filter by keyword or category and check new projects every morning.
• Monitor demand for a skill: how many projects mention "wordpress" or "traduccion" this week, and at what budget.
• Feed a lead list: a client posting a project for a skill you sell is a lead; filter by category and country.
• Study the LatAm freelance market: budgets, in-demand skills and project volume by country over time.

Input

Field	What it does
Keywords	Job title or skill, using Workana's own search (e.g. wordpress). Empty means every open project.
Client's country	Optional 2-letter ISO code (AR, BR, MX, CL, CO, PE...) of the client who posted the project. Empty means every country.
Category slug	Optional, Workana's own category slug (e.g. it-programming), copied from a filtered workana.com/jobs URL.
Published within (days)	Keep only projects published in the last N days. Use 1 for daily monitoring.
Maximum number of projects	The run stops once this many projects are saved.
Only new results	For scheduled runs: skip the projects an earlier run of this same search already delivered.
Include full descriptions	Adds the full project description as plain text, with any e-mail address or phone number removed.

Output

One record per project, with the unified field names shared by every job and freelance-mission actor from this author, plus a few fields specific to Workana kept alongside them:

Field	What it is
id, url, title	workana:<slug>, the public /job/<slug> page, and the full project title (the list truncates it; this reads the untruncated title).
companyName, companyUrl, confidentialCompany	Almost every client on Workana is an individual shown only as a first name and initial, which is personal data: companyName is null and confidentialCompany is true for those. When the client is an actual company (isCompany on the site), its name is kept here.
locationLabel, city, region, postalCode, country	The client's country, as published by Workana (e.g. "Argentina" / AR). Workana's list does not publish a city or region, so those stay null.
remote	Always "unknown": Workana does not publish whether a project is remote, hybrid or on-site (in practice almost all of them are remote, by the nature of the platform, but this is never asserted without the site actually saying so).
employmentType	Always "freelance".
salaryMin, salaryMax, salaryCurrency, salaryPeriod	Parsed from Workana's own budget text (always in USD), e.g. "USD 250 - 500" or "Less than USD 15 / hour". salaryPeriod is "hour" for hourly projects, null for a fixed project budget.
datePosted	Computed from Workana's relative label ("2 hours ago", "Yesterday"): approximate, to the hour or the day depending on the label.
validThrough, experienceLevel	Always null: not published by Workana's project list.
industry, subcategory	Workana's own "Category" and "Subcategory" labels (e.g. "IT & Programming" / "Web development").
skills	Skills listed by the client, as Workana's own tags.
source, sourceId, scrapedAt	"workana.com", the project's slug, and when this run read it.
isHourly, isUrgent, bidsCount, clientHasVerifiedPayment, budgetLabel	Fields specific to Workana: hourly vs. fixed budget, the site's "urgent" flag, number of freelancer bids so far, whether the client has a verified payment method, and the original budget text.
description	Full project description as plain text (only when Include full descriptions is on). Any e-mail address or phone number is removed before saving.

Three real results from the same run, side by side:

Title	Country	Budget	Category
Dynamic Event Page for Artist Tours and Venue Openings	US	USD 250 - 500	IT & Programming
Senior Full-Stack Engineer for Internal App Architecture & Development	UA	USD 15 - 45 / hour	IT & Programming
Part-Time Operations & Technology Coordinator, Executive Coaching Firm	US	Less than USD 15 / hour	Admin Support

One full record:

{
  "id": "workana:dynamic-event-page-for-artist-tours-and-venue-openings",
  "url": "https://www.workana.com/job/dynamic-event-page-for-artist-tours-and-venue-openings",
  "title": "Dynamic Event Page for Artist Tours and Venue Openings",
  "companyName": null,
  "companyUrl": null,
  "locationLabel": "United States",
  "city": null,
  "region": null,
  "postalCode": null,
  "country": "US",
  "remote": "unknown",
  "employmentType": "freelance",
  "salaryMin": 250,
  "salaryMax": 500,
  "salaryCurrency": "USD",
  "salaryPeriod": null,
  "datePosted": "2026-10-31T23:52:42.684Z",
  "validThrough": null,
  "experienceLevel": null,
  "industry": "IT & Programming",
  "skills": ["HTML", "CSS", "JavaScript", "Responsive Web Design", "WordPress"],
  "source": "workana.com",
  "sourceId": "dynamic-event-page-for-artist-tours-and-venue-openings",
  "scrapedAt": "2026-11-01T00:52:42.684Z",
  "confidentialCompany": true,
  "subcategory": "Web development",
  "isHourly": false,
  "isUrgent": false,
  "bidsCount": 49,
  "clientHasVerifiedPayment": true,
  "budgetLabel": "USD 250 - 500"
}

Export the dataset as JSON, CSV or Excel, or read it through the Apify API.

Good to know

• No login, proxy or browser needed for a default run: the Actor reads Workana's own public project feed directly.
• Workana only exposes its most recent pages through this feed: a very large Maximum number of projects (or a narrow filter) can return fewer results than requested once the site's own window is exhausted. That is the normal end of the list, not an error.
• datePosted is approximate, computed from Workana's relative label, not an exact timestamp: the site does not publish one.
• No personal data is collected. A client posting a project is public information, but on Workana almost every client is an individual, not a company: their name is never saved, companyName stays null and confidentialCompany is true. A freelancer's own profile (name, photo, rating, portfolio, bids) is never part of this feed in the first place; only the client's project is.
• Any e-mail address or phone number a client typed into the description is removed before saving.

Why this one

• Reads Workana's own JSON feed directly, not a brittle HTML parse of the page: fast, and the full project description is already there without opening a second page per project.
• One schema with this author's other job and freelance actors. The same field names everywhere (datePosted, salaryMin, employmentType, skills...), so Workana drops into a pipeline built for Codeur.com, Free-Work or any other source from this author without remapping a single field.
• Individual clients are never named. Most freelance marketplaces show a client's first name; this Actor treats that as personal data and keeps it out of the dataset, unlike a generic scraper that would copy whatever the page shows.

Frequently asked questions

Do I need an account or a proxy for Workana? No. The Actor reads publicly visible projects only.

Why is companyName almost always empty? Because almost every client on Workana is an individual, not a company, and an individual's name is personal data. See "Good to know" above.

Why is remote always "unknown"? Workana's project feed does not publish a remote/hybrid/on-site flag, so the Actor never guesses one.

Which formats can I export? JSON, CSV, Excel, XML, HTML table or RSS, from the dataset page or through the API.

Is it legal to scrape? The Actor collects publicly visible projects and respects the robots.txt rules of the site. How you use the data is your responsibility: check the site's terms and the laws that apply to you, for example the GDPR.

Something does not work? Open an issue in the Issues tab. Every public actor is test-run daily and the broken ones are repaired.

Did this save you time? A short review on the Store page helps other people find the Actor, and tells me what to improve next.

Why this one

• Reads Workana's own JSON feed directly, not a brittle HTML parse of the page: fast, and the full project description is already there without opening a second page per project.
• One schema with this author's other job and freelance actors. The same field names everywhere (datePosted, salaryMin, employmentType, skills...), so Workana drops into a pipeline built for Codeur.com, Free-Work or any other source from this author without remapping a single field.
• Individual clients are never named. Most freelance marketplaces show a client's first name; this Actor treats that as personal data and keeps it out of the dataset, unlike a generic scraper that would copy whatever the page shows.

Who uses it

• Recruiting agencies and HR teams watch which companies hire, for which roles and at which salary, in their market.
• Job boards and aggregators feed their own site with fresh postings in a stable schema, without maintaining a parser.
• B2B sales and lead generation: a company that is hiring is a company that is buying. Filter postings by role to spot prospects early.
• Labour-market research: salaries, skills in demand, remote share and hiring volume over time.

Pricing

Pay per result: $2.00 per 1,000 postings, plus $0.01 per run start with the default 4 GB of memory. For example, 100 postings cost about $0.21. You only pay for the postings you receive, and platform usage is included in that price. Store discounts apply automatically on paid Apify plans: up to 20% off every event on the higher tiers.

Run it from your code

JavaScript:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('bibian/workana-projects-scraper').call({
  keywords: 'wordpress',
  publishedWithinDays: 7,
  maxItems: 50,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Python:

from apify_client import ApifyClient

client = ApifyClient(token="<APIFY_TOKEN>")
run = client.actor("bibian/workana-projects-scraper").call(run_input={
    "keywords": "wordpress",
    "publishedWithinDays": 7,
    "maxItems": 50
})
items = client.dataset(run["defaultDatasetId"]).list_items().items

Monitor new postings daily and connect your tools

1. Schedule it. Save a task, set its publication date filter to the shortest window, and schedule it daily with Apify Schedules. Deduplicate on the id field if you keep your own copy. Tick Only new results in the input and each run returns, and charges, only the postings that earlier runs of the same search did not deliver.
2. Push the results where you work. Add an Apify integration or a webhook to the task: Google Sheets, Slack, Make, Zapier, n8n or your own endpoint, triggered at the end of every run.
3. Call it from your stack. The API and the JavaScript and Python clients return the dataset as JSON, CSV or Excel.
4. Let an AI agent use it. Through the Apify MCP server, assistants such as Claude or ChatGPT can search the Store, read this page and run the actor as a tool.

Frequently asked questions

Do I need an account, cookies or a proxy for Workana? No. The actor reads publicly visible pages only.

Which formats can I export? JSON, CSV, Excel, XML, HTML table or RSS, from the dataset page or through the API.

Is it legal to scrape? The actor collects publicly visible postings and respects the robots.txt rules of the site. How you use the data is your responsibility: check the site's terms and the laws that apply to you, for example the GDPR.

Need another site, a missing field or a new filter? Open an issue in the Issues tab and say what you need, with an example URL if you have one. Requests are read, and the most asked ones are built next.

Need a custom version built for you? I also build private versions and custom scrapers: another site, extra fields, a specific output format, or delivery straight to Google Sheets, a database or a webhook. Open an issue in the Issues tab with what you need and an example URL, and I will reply there with a quote.

Something does not work? Open an issue in the Issues tab. Every public actor is test-run daily and the broken ones are repaired.

Did this save you time? A short review on the Store page helps other people find the actor, and tells me what to improve next.

More job scrapers by the same author

• Free-Work Jobs & Freelance Missions Scraper (France)
• Infoempleo Jobs Scraper (Spain)
• Arbeitsagentur Jobs Scraper (Germany)
• Bumeran, Zonajobs & Laborum Jobs Scraper (LatAm)
• Universal Job Postings Scraper (any job site)
• Codeur.com Freelance Projects Scraper (France)