Gupy Jobs Scraper — Brazil Jobs: CLT or PJ, Remote, Steps avatar

Gupy Jobs Scraper — Brazil Jobs: CLT or PJ, Remote, Steps

Pricing

from $0.48 / 1,000 jobs

Go to Apify Store
Gupy Jobs Scraper — Brazil Jobs: CLT or PJ, Remote, Steps

Gupy Jobs Scraper — Brazil Jobs: CLT or PJ, Remote, Steps

Brazil jobs (vagas de emprego) from Gupy: title, company, city and state, remote, hybrid or on-site, CLT, PJ or internship, exact posting time, apply-by date, responsibilities, requirements and hiring steps, newest first. Or get only the jobs new since your last run. No login.

Pricing

from $0.48 / 1,000 jobs

Rating

0.0

(0)

Developer

Northbell

Northbell

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Features

Limited permissions

Share

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.

Try it now. The input is already filled in. Press Start: the example searches (desenvolvedor, analista de dados) return 16 jobs in Brazil (8 per search) in about 25 seconds, for about $0.02. Raise Max jobs per search for more.

titlecompanycitystateworkplaceTypecontractType
DESENVOLVEDOR JAVA PLGlobalwebremoteCLT (permanent employee)
Analista Desenvolvedor .Net SêniorMontreal / Tecnologia e InovaçãoSão PauloSão PaulohybridCLT (permanent employee)
DESENVOLVEDOR BAIXA PLATAFORMA - JAVACertsysremoteCLT (permanent employee)

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, companyas listed; the company is the employer's own Gupy career page
location, city, state, workplaceType, remote, hybridcity and state as Gupy lists them, and remote, hybrid or on-site
contractType, employmentTypesthe 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, applyBythe exact posting time and the last day to apply
disabilityFriendlytrue when the company marks the job as open to people with disabilities (PcD)
responsibilities, requirements, niceToHave, descriptionthe sections of the job page, and all of them as one text
hiringSteps, employerJobCode, quickApplythe stages of the hiring process (Cadastro, Entrevista Técnica, …), the company's own job code, and whether one-click apply is on
companyJobsUrllast in the row: the employer's own jobs page on Gupy (https://<company>.gupy.io/)
isNewSinceLastRuntrue / false, or null on the first run (unknown, not "old")
jobUrllink to the job on Gupy
searchwhich 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.

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

For AI agents

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

Use it from Claude Code (or another coding agent)

Save this as ~/.claude/skills/gupy-jobs/SKILL.md (other agents that read SKILL.md files: their skills folder), put your Apify API token in the APIFY_TOKEN environment variable, and ask the agent in plain words, for example "Any new desenvolvedor jobs on Gupy since yesterday?".

---
name: gupy-jobs
description: Job listings from Gupy by keyword, location and filters, and only the jobs that are new since the last run. Runs the Apify Actor northbell/gupy-jobs-scraper with the user's APIFY_TOKEN.
---
Run: curl -s -X POST "https://api.apify.com/v2/acts/northbell~gupy-jobs-scraper/run-sync-get-dataset-items?timeout=300" -H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" -d '{"searches":["desenvolvedor"],"maxJobsPerSearch":50,"output":"new"}'
"output": "new" returns only jobs not seen in the previous run (the first run returns all). Use "all" for a one-off list.
Rows have type job, closed or error. Never print the token. Tell the user the price on the Actor's Store page before a large run.

Prefer MCP? Add https://mcp.apify.com?tools=northbell/gupy-jobs-scraper as a remote MCP server (in Claude Code: claude mcp add --transport http apify "https://mcp.apify.com?tools=northbell/gupy-jobs-scraper") and sign in to Apify when asked; the Actor then shows up as a tool.

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, with no extra requests and 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 · Job-Room · Platsbanken · eFinancialCareers · MyCareersFuture · EURES · USAJOBS · Job Bank · Internshala · Gupy · CutShort · iimjobs & hirist · Naukrigulf · Jobindex · karriere.at · Arbeitnow · Wellfound · Remote OK · We Work Remotely · Just Join IT & No Fluff Jobs · OnlineJobs.ph.

Running more than one board? Job Dedupe & Merge turns the rows of several job scrapers into one row per job, with every URL it was found at.

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

**Something broke or looks wrong?** Open an issue on this Actor's Issues tab and I'll look at it. **Found it useful?** A short review on the Store page helps other people find it.