Gupy Scraper

Every job (vaga) on Gupy — the hiring platform that thousands of Brazilian companies use for their career pages — for your words and city or state, newest first: title, company, city and state, remote, hybrid or on-site, CLT, PJ, internship or apprentice, the exact posting time, apply-by date, and from each job page the responsibilities, requirements, nice-to-haves and hiring steps, as clean JSON. Schedule it and you get only the jobs that are new since the last run.

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.

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
title, company	as listed; the company is the employer's own Gupy career page
location, city, state, workplaceType, remote, hybrid	city and state as Gupy lists them, and remote, hybrid or on-site
contractType, employmentTypes	the kind of hire in plain words (CLT (permanent employee), PJ (contractor company), Internship (estágio), Young apprentice (jovem aprendiz), Talent pool (no open vacancy)), and full-time, contract, internship or temporary
postedAt, applyBy	the exact posting time and the last day to apply
disabilityFriendly	true when the company marks the job as open to people with disabilities (PcD)
responsibilities, requirements, niceToHave, description	the sections of the job page, and all of them as one text
hiringSteps, employerJobCode, quickApply	the stages of the hiring process (Cadastro, Entrevista Técnica, …), the company's own job code, and whether one-click apply is on
isNewSinceLastRun	true / false, or null on the first run (unknown, not "old")
jobUrl	link to the job on Gupy
search	which of your searches returned it

Gupy has no salary field; some companies write pay in the text. Email addresses and phone numbers in the job text are replaced with [email removed] / [phone removed]. Company logos are not returned.

Input

Put one search per line in Searches (e.g. desenvolvedor) and optionally a Location (e.g. São Paulo). Location takes a Brazilian state (São Paulo, SP, Minas Gerais), a city (Campinas, Curitiba), a city with its state (Campinas, SP) or remote. Leave it empty for all of Brazil. 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. When the job board itself is down or failing (HTTP 5xx or no answer), the error row says so and carries sourceDown: true, so you can tell it from a problem in this Actor; nothing is charged for what could not be read.

How the search works: your words go to Gupy's job-title search (desenvolvedor, analista de dados, vendedor, enfermeiro, estágio). Location is a state by name or its two letters, a city, a city with its state, or remote. Jobs come newest first by their exact posting time.

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: 10 tidy columns, title first, instead of every raw field.

Pricing

$0.60 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.

For AI agents

For a fast answer call with {"searches": ["desenvolvedor"], "maxJobsPerSearch": 20, "includeDescription": false} — a few seconds. The defaults (up to 200 jobs with full descriptions) 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.