Indeed Global Job Scraper with Company Salary Reports: MCP config, n8n workflow and API

{
  "position": "web developer",
  "location": "San Francisco",
  "country": "US",
  "maxItemsPerSearch": 3,
  "maxItems": 3,
  "shardByDate": false,
  "easyApplyOnly": false,
  "includeCompanyRatings": false,
  "includeSponsored": false,
  "includeDescriptionHtml": false,
  "saveOnlyUniqueItems": true
}

---
name: indeed-global-job-scraper-with-company-salary
description: "One record per Indeed job listing, with title signals, normalized salary, location, benefits, contacts, coverage counts, and the employer's rating and salary-by-title report. Runs the Apify Actor nimbryxo-studio/indeed-global-job-scraper-with-company-salary. Use when the user needs Indeed data with fields such as positionName, displayTitle, company, rating, location, salary 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/indeed-global-job-scraper-with-company-salary"
  store-url: "https://apify.com/nimbryxo-studio/indeed-global-job-scraper-with-company-salary"
---

# Indeed Global Job Scraper with Company Salary Reports

Use this skill to fetch Indeed data with the Apify Actor `nimbryxo-studio/indeed-global-job-scraper-with-company-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 |
| --- | --- | --- |
| `position` | string | Job title, skill or keywords, e.g. `web developer`, `nurse`. Search one company's jobs with `company:Amazon`, titles only with `title:(data analyst)`; quotes, OR and -exclusions work too. |
| `location` | string | City, region or postal code, e.g. `San Francisco`, `Austin, TX`, `10001`, `London`. Leave empty to search the whole country. |
| `country` | string | Indeed country site to search. Results come in the site's language and salaries in its currency. |
| `maxItemsPerSearch` | integer | Maximum number of jobs to save for each search (the keyword search and each search URL). Indeed's cursor stops at roughly 1,000 fetched rows, including duplicates; use `locationShards` or more search URLs to collect more. |
| `maxItems` | integer | Optional hard cap across every search and pasted job URL. The run stops as soon as this many jobs are saved. Leave empty for no global cap. |
| `shardByDate` | boolean | Run each keyword search five times, for the last 1, 3, 7, 14 and 30 days, and remove duplicates. Useful for freshness coverage when you need more than one cursor walk per search. |
| `easyApplyOnly` | boolean | Only jobs you can apply to directly on Indeed. |
| `includeCompanyRatings` | boolean | Add the employer's HTML company report: CEO approval, founding year, work wellbeing scores and average salaries by job title, plus an industry fallback. |
| `includeSponsored` | boolean | Add `isSponsored` from Indeed's mobile search page for jobs that also appear there. This costs one extra lightweight page per search and is best effort: jobs outside the first mobile result page keep the field omitted rather than guessed. |
| `includeDescriptionHtml` | boolean | Also save the job description as HTML (`descriptionHtml`) with its formatting. The plain-text `description` is always included. |
| `saveOnlyUniqueItems` | boolean | Save each job once even when several searches find it. Jobs are always unique within one search. |

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

```json
{
  "position": "web developer",
  "location": "San Francisco",
  "country": "US",
  "maxItemsPerSearch": 3,
  "maxItems": 3,
  "shardByDate": false,
  "easyApplyOnly": false,
  "includeCompanyRatings": false,
  "includeSponsored": false,
  "includeDescriptionHtml": false,
  "saveOnlyUniqueItems": true
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~indeed-global-job-scraper-with-company-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~indeed-global-job-scraper-with-company-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: `positionName`, `displayTitle`, `company`, `rating`, `location`, `salary`, `jobType`, `remoteWorkType`, `postedAt`, `isRepost`, `isSponsored`, `easyApply`, `searchFacetTotal`, `searchRetrieved`, `url`, `salaryMin`, `salaryMax`, `salaryPeriod`, `salaryCurrency`, `salarySource`.

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