Naukri.com Job Listings Extractor with Salary & Skills: MCP config, n8n workflow and API

{
  "searches": [
    {
      "keywords": [
        "software engineer"
      ],
      "locations": [
        "bangalore"
      ]
    }
  ],
  "jobIds": [
    "221026015762"
  ],
  "maxItems": 3,
  "onlyNew": false,
  "resetState": false,
  "includeDescription": true,
  "includeDescriptionHtml": false,
  "includeCompanyReviews": false,
  "strictJobAge": true,
  "timeBudgetSecs": 0,
  "failOnEmpty": false,
  "browserFallback": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyCountry": "IN"
  }
}

---
name: naukri-com-job-listings-extractor-with-salary
description: "Naukri.com job listings with full descriptions, parsed salary and experience, skills, locations, work mode, education, role taxonomy and company profiles. Runs the Apify Actor nimbryxo-studio/naukri-com-job-listings-extractor-with-salary. Use when the user needs Naukri data with fields such as id, title, url, companyName, companyId, companyLogoUrl and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "nimbryxo-studio/naukri-com-job-listings-extractor-with-salary"
  store-url: "https://apify.com/nimbryxo-studio/naukri-com-job-listings-extractor-with-salary"
---

# Naukri.com Job Listings Extractor with Salary & Skills

Use this skill to fetch Naukri data with the Apify Actor `nimbryxo-studio/naukri-com-job-listings-extractor-with-salary` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `searches` | array | One or more search configurations. Each entry can hold several keywords and several locations; every keyword is combined with every location. Leave keywords empty to browse a location or company. |
| `jobIds` | array | Fetch these Naukri job IDs directly. Accepts bare IDs or Naukri job URLs. Job IDs are processed before searches. |
| `companyIds` | array | Naukri company IDs to search across. When searches are also supplied, each company is combined with every search. |
| `maxItems` | integer | Total records to return across all queries. Naukri allows at most 3,000 jobs per query (150 pages of 20). |
| `onlyNew` | boolean | Emit only jobs that were not emitted by an earlier run with the same state key. |
| `resetState` | boolean | Clear the saved job IDs before this run. |
| `includeDescription` | boolean | Include the full job description text. Turn off to keep records smaller. |
| `includeDescriptionHtml` | boolean | Include the raw HTML job description in addition to plain text. |
| `includeCompanyReviews` | boolean | Include up to three AmbitionBox review snippets per job. Off by default to keep records small. |
| `strictJobAge` | boolean | Drop promoted jobs older than the selected job age using Naukri's posting date. |
| `timeBudgetSecs` | integer | Stop gracefully after this many seconds. 0 means no time limit. |
| `failOnEmpty` | boolean | Mark the run as failed when no jobs are returned. |
| `browserFallback` | boolean | If the normal connection is blocked, retry through a browser session. Slower and uses more memory; leave off unless needed. |
| `proxyConfiguration` | object | Optional connection override. By default the actor uses an India-based Apify connection automatically. |

Example `input.json` (the Actor's published prefill):

```json
{
  "searches": [
    {
      "keywords": [
        "software engineer"
      ],
      "locations": [
        "bangalore"
      ]
    }
  ],
  "jobIds": [
    "221026015762"
  ],
  "maxItems": 3,
  "onlyNew": false,
  "resetState": false,
  "includeDescription": true,
  "includeDescriptionHtml": false,
  "includeCompanyReviews": false,
  "strictJobAge": true,
  "timeBudgetSecs": 0,
  "failOnEmpty": false,
  "browserFallback": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyCountry": "IN"
  }
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~naukri-com-job-listings-extractor-with-salary/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/nimbryxo-studio~naukri-com-job-listings-extractor-with-salary/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `id`, `title`, `url`, `companyName`, `companyId`, `companyLogoUrl`, `logoUrl`, `companyProfileUrl`, `companyWebsite`, `companyDescription`, `companyAddress`, `companyRating`, `companyReviewCount`, `companyReviews`, `companyApplyUrl`, `applyRedirectUrl`, `applyUrl`, `salary`, `salaryMin`, `salaryMax`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.