Naukrigulf Scraper: Gulf Jobs with Salary (UAE, Saudi, Qatar) avatar

Naukrigulf Scraper: Gulf Jobs with Salary (UAE, Saudi, Qatar)

Pricing

from $0.80 / 1,000 jobs

Go to Apify Store
Naukrigulf Scraper: Gulf Jobs with Salary (UAE, Saudi, Qatar)

Naukrigulf Scraper: Gulf Jobs with Salary (UAE, Saudi, Qatar)

Gulf jobs from Naukrigulf (UAE, Saudi Arabia, Qatar, Kuwait, Oman, Bahrain), newest first: title, company, cities, country, years of experience, skills, salary as numbers in local currency and US$ when shown, industry, full description. Job alerts: only new jobs since your last run.

Pricing

from $0.80 / 1,000 jobs

Rating

0.0

(0)

Developer

Northbell

Northbell

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Security

Limited permissions

Share

Every new job on Naukrigulf, the Gulf job site of Info Edge (Naukri), for your words and place, best matches first, as clean JSON: title, company, cities and country code, the years of experience asked, skills, vacancies, the salary as numbers when the employer shows it (in the local currency, e.g. AED, SAR, QAR, and in US$), industry, job function, full-time or not, on-site or remote, education asked, whether a recruitment agency posted it, the exact posting time and the full description. Schedule it and you get only the jobs that are new since the last run.

How "new since last run" works

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.

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
location, cities, countryCodethe place as listed (Abu Dhabi , Dubai - United Arab Emirates (UAE)), the cities alone, and the two-letter country code (AE, SA, QA, KW, OM, BH)
experienceYearsMin, experienceYearsMax, vacanciesthe years of experience asked, and how many people the employer hires
salaryMin, salaryMax, salaryCurrency, salaryIntervalthe salary as numbers in the local currency (AED, SAR, QAR, …), only when the employer shows it; the site does not say per month or per year, so the interval is null unless it does
salaryUsdMin, salaryUsdMaxthe same salary in US$, as the site converts it
summary, highlights, skillsthe short summary and bullet points from the list, and the skill tags
industry, functionalArea, employmentType, workplace, remote, educationfrom the job page: industry, job function, Full-time etc., On-site or remote, and the education asked
recruitmentAgency, confidentialCompany, easyApply, topEmployer, sponsoredwhether a recruitment agency posted it, whether the employer is hidden, one-click apply, and the site's badges
postedAt, descriptionthe exact posting time, and the full job text
isNewSinceLastRuntrue / false, or null on the first run (unknown, not "old")
jobUrllink to the job on Naukrigulf
searchwhich of your searches returned it

Input

Put one search per line in Searches (e.g. accountant) and optionally a Location (e.g. Dubai). Location is a city or country as Naukrigulf knows it (Dubai, Abu Dhabi, Riyadh, Saudi Arabia, Qatar, Kuwait). Leave Searches empty and set a Location to get every job there. 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 and Location go to Naukrigulf's own search (accountant, civil engineer, nurse, sales executive) in its own best-match order, so the jobs whose title is what you searched come first (a newest-first order mixes in jobs that only mention a word). With Posted within, or when only jobs new since the last run are asked for, it reads newest first instead and stops as soon as jobs get older. The salary comes from each job page, so it needs Include description (on by default); about half of the jobs show one. The site does not say whether a salary is per month or per year, so salaryInterval is null unless it does.

Recruiter names, phone numbers and e-mail addresses are never returned, and contact details inside job texts are removed. Only public job listings are read, without signing in, with a pause between requests. This Actor is not affiliated with or endorsed by Naukrigulf or Info Edge (India) Limited; you are responsible for how you use the data and for following the site's terms.

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

$1 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": ["accountant"], "maxJobsPerSearch": 20, "includeDescription": false}. It takes a few seconds. The defaults (up to 40 jobs with full descriptions) can take about 2 minutes (2 seconds between requests, one per job for the description), 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/naukrigulf-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 accountant jobs on Naukrigulf since yesterday?".

---
name: naukrigulf-jobs
description: Job listings from Naukrigulf by keyword, location and filters, and only the jobs that are new since the last run. Runs the Apify Actor northbell/naukrigulf-jobs-scraper with the user's APIFY_TOKEN.
---
Run: curl -s -X POST "https://api.apify.com/v2/acts/northbell~naukrigulf-jobs-scraper/run-sync-get-dataset-items?timeout=300" -H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" -d '{"searches":["accountant"],"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/naukrigulf-jobs-scraper as a remote MCP server (in Claude Code: claude mcp add --transport http apify "https://mcp.apify.com?tools=northbell/naukrigulf-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.

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