Computrabajo Scraper — Mexico, Colombia & LatAm Jobs (Empleos) avatar

Computrabajo Scraper — Mexico, Colombia & LatAm Jobs (Empleos)

Pricing

from $0.64 / 1,000 jobs

Go to Apify Store
Computrabajo Scraper — Mexico, Colombia & LatAm Jobs (Empleos)

Computrabajo Scraper — Mexico, Colombia & LatAm Jobs (Empleos)

Computrabajo jobs scraper for Mexico, Colombia, Argentina, Peru, Chile +5 more: title, company, city, salary with currency and period, contract type, posting and expiry dates, full description — plus job alerts: only jobs new since your last run. Keyword, city or search URL. No login.

Pricing

from $0.64 / 1,000 jobs

Rating

0.0

(0)

Developer

Northbell

Northbell

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

18 hours ago

Last modified

Share

Computrabajo Scraper

Search Computrabajo (Mexico, Colombia, Argentina, Peru, Chile and 5 more countries) by keyword, city or a pasted search URL and get every matching job as clean JSON with the salary split into min / max / interval. Put your searches on a daily schedule: each run marks which jobs are new since your last run, so you only read the new ones.

Try it now — the input is already filled in. Press Start: the example searches (contador, vendedor) return 84 jobs in Mexico in about 11 seconds, for about $0.08.

titlecompanylocationsalaryMinsalaryMaxsalaryCurrencysalaryInterval
Contador Público - Experiencia en Egresos e Inventarios, Sap, ExcelGeneral ProductsJalisco, San Pedro Tlaquepaque, México3500035000MXNmonth
Auxiliar Contable - BilingüeGrupo HB MéxicoCiudad de México DF, Benito Juárez, México1700017000MXNmonth
Vendedor de Campo - Materiales de ConstrucciónPotential Achieve LabsPuebla, Tepeaca, México1083310833MXNmonth

60 of these 84 show a monthly salary, read from the salary the employer filed on the job page, never guessed from the text. Change Countries for Colombia, Argentina, Peru, Chile and 5 more. Scheduled, each run marks which jobs are new since the last one.

Call it from a script or a schedule

curl -X POST "https://api.apify.com/v2/acts/northbell~computrabajo-jobs-scraper/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"searches":["contador"],"countries":["MX"]}'

The response is the rows themselves (a JSON array). To run it on a timetable instead, save the input as a task in Apify Console and add a Schedule; n8n, Make and Zapier run it through their Apify app with the same input.

How "new since last run" works

The Actor remembers which jobs each search returned last time. A job it has not seen before is marked isNewSinceLastRun: true. If the whole search fits within Max jobs, the comparison is exact and jobs that disappeared come back as type: "closed" rows. If the search is bigger than Max jobs, a job only counts as new when it was also posted after your previous run — so an old job that merely moved into view is never reported as new.

Filters (title, location text, salary, remote) never change the comparison, so changing a filter never makes jobs look new.

What you get

Field
country, title, company, locationas listed
salaryMin, salaryMax, salaryCurrency, salaryIntervalin local currency, as published — null when the employer hides it
employmentType, industryfrom the job page
descriptionthe full job text
postedAt, expiresAtpublication and expiry dates

Offers that Computrabajo still lists but whose page has already closed are skipped (about 1 in 4 in our tests), so you only pay for jobs that are really open. | isNewSinceLastRun | true / false, or null on the first run (unknown, not "old") | | jobUrl | link to the job on Computrabajo | | search | which of your searches returned it |

Does the job need Spanish?

Every job row ends with four columns that say how much Spanish (the local language) the job asks for, read from what the job text says — not from the language the ad is written in, so "fluent German (C1) required" in an English ad counts as required.

Field
localLanguageNeedrequired, preferred (a plus), one-of (this or another language), not-required (said outright), unknown (the text says nothing), or null (no text was read)
localLanguageLevelnative, fluent, good, basic, or a CEFR level such as B2, when the text names one
localLanguagethe language this is about
languagesRequiredevery language the text names: { language, level, need, matched, evidence } — matched are the words that decided it and evidence the sentence, so you can check each call

Jobs that don't need Spanish keeps only jobs that say so (or, in the second option, where it is only a plus). Silence is unknown, never "not required". Words only, no AI model, so the same text always gives the same answer.

Changed 2026-10-15: these four columns were added at the end of each row; existing columns and their order are unchanged.

Input

Put one search per line in Searches (e.g. contador) and optionally a Location (e.g. Monterrey). Or set the filters on the site and paste the result page into Search URLs (e.g. https://mx.computrabajo.com/trabajo-de-contador-en-nuevo-leon) — every filter the site has then applies. Many searches in one run are cheaper than one run each.

A search the site refuses comes back as an error row and the run carries on.

Example output

One real row from a test run (long text shortened here with …).

{
"type": "job",
"provider": "computrabajo",
"search": "contador",
"country": "MX",
"jobId": "0B16822F7F0869CB61373E686DCF3405",
"title": "Contador analista - Contador",
"company": "HONEY WHALE",
"location": "Jalisco, Guadalajara, México",
"locations": [
"Jalisco, Guadalajara, México"
],
"salaryMin": 18000,
"salaryMax": 18000,
"salaryCurrency": "MXN",
"salaryInterval": "month",
"employmentType": "FULL_TIME",
"remote": null,
"industry": "RRHH / Personal",
"description": "Supervisar la contabilidad general y la elaboración de estados financieros conforme a las NIF y normativas fiscales.\nDiseñar, implementar y monitorear controles…",
"postedAt": "2026-10-06T00:00:00.000Z",
"expiresAt": "2026-12-05T00:00:00.000Z",
"companyUrl": null,
"companyLogo": "",
"jobUrl": "https://mx.computrabajo.com/ofertas-de-trabajo/oferta-de-trabajo-de-contador-analista-contador-en-guadalajara-0B16822F7F0869CB61373E686DCF3405",
"countryCode": "MX",
"seniority": "mid",
"employmentTypes": [
"full-time"
],
"isNewSinceLastRun": false
}

Get only the new jobs every morning (3 steps)

  1. Open this Actor in Apify Console, fill in your searches, set What to return to Only jobs that are new since the last run, and click Save as a new task.
  2. On the task, add a Schedule — for example daily at 07:00.
  3. Open the task's Integrations tab and connect Slack, email, Google Sheets (or Zapier / Make / a webhook). Each morning you get only the new jobs.

You pay only for the new jobs plus $0.01 per run, so a quiet day costs about a cent. When you export by hand, pick the Jobs view: 13 tidy columns, title first, instead of every raw field.

Pricing

$0.80 per 1,000 jobs, plus $0.01 per run. Closed-job rows and errors are free. With Only jobs that are new since the last run, a daily schedule only pays for the new ones.

Don't know which companies to watch? The Greenhouse Jobs Scraper searches 4,800 companies by job title — no company names needed — and reports exactly which matching roles are new or closed each run.

**Measured, not estimated:** 244 jobs in 42 s, about **$0.0031 of Apify platform usage per 1,000 jobs** at 512 MB (our running cost — included in the price, nothing on top) (2026-09-30).

For AI agents

For a fast answer call with {"searches": ["contador"], "maxJobsPerSearch": 20} — a few seconds. The defaults (up to 200 jobs) can take about a minute, which is longer than many agent tool timeouts. Each row has type: job, closed or error. isNewSinceLastRun: null means "no previous run to compare with".

Same filters on every site (10/2026): experience level (read from the title: intern → executive, returned as a seniority column) and employment type (the site's own words normalised into full-time / part-time / contract / temporary / internship, returned as employmentTypes). They only narrow what is returned — no extra requests, no extra cost.

Zero rows is never ambiguous. The run's status message says why, per search — e.g. "zzz": no results on the site, results found but all removed by your filters or nothing new since the last run — and the OUTPUT record in the run's key-value store has the same as JSON: perSearch[].status is ok, no-results, all-filtered, nothing-new or error, with listed, read, returned, new and closed. Set summaryRows: true to get it as free type: "summary" rows instead.

Same core columns on every northbell job scraper (15 job sites + 10 company-career-page scrapers), so you can stack them into one table: jobId, title, company, location, countryCode (ISO, job sites), remote (true / false / null), employmentType (the site's own words), postedAt, jobUrl, salaryMin, salaryMax, salaryCurrency, salaryInterval, isNewSinceLastRun. Unknown is null, never a guess.

More job scrapers from northbell

Job sites: SEEK · Instahyre · Reed · InfoJobs · XING · Dice · HelloWork · Computrabajo · Foundit · jobs.ch · Arbeitsagentur · Arbeitnow · Remote OK · We Work Remotely.

Company career pages with exact new/closed tracking: Greenhouse · Lever · Workday · AI companies.