Indeed Job Search Scraper with Salary & Benefits Data: MCP config, n8n workflow and API

{
  "searchQueries": [
    "web developer in San Francisco"
  ],
  "country": "US",
  "location": "San Francisco",
  "radius": 25,
  "easyApplyOnly": false,
  "maxItems": 3,
  "includeDescriptionHtml": false,
  "includeCompanyRatings": false,
  "includeContacts": false,
  "includeCompanyReviews": false,
  "includeCompanySalaries": false,
  "expandBeyondCeiling": false
}

---
name: indeed-job-search-scraper-with-salary-and-benefits
description: "One record per Indeed job listing, with title, company, salary, benefits, remote-work status, full description and apply links. Runs the Apify Actor vexaloom-labs/indeed-job-search-scraper-with-salary-and-benefits. Use when the user needs Indeed data with fields such as jobTitle, company, location, salaryText, salarySource, workplaceType 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: "vexaloom-labs/indeed-job-search-scraper-with-salary-and-benefits"
  store-url: "https://apify.com/vexaloom-labs/indeed-job-search-scraper-with-salary-and-benefits"
---

# Indeed Job Search Scraper with Salary & Benefits Data

Use this skill to fetch Indeed data with the Apify Actor `vexaloom-labs/indeed-job-search-scraper-with-salary-and-benefits` 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 |
| --- | --- | --- |
| `searchQueries` | array | Job searches. Write a location after " in " to search one city, e.g. `software engineer in New York`, `registered nurse in Houston, TX`. A query without " in " uses the Location field below, or searches the whole country. |
| `country` | string | Indeed country site to search. Results come in the site's language and salaries in its currency. |
| `location` | string | City, region or postal code for searches that don't name a location themselves, e.g. `Austin, TX`, `10001`, `London`. Leave empty to search the whole country. Ignored for remote-only searches (remote jobs are searched country-wide). |
| `radius` | integer | How far from the location to search. |
| `easyApplyOnly` | boolean | Only jobs that accept Indeed's one-click application. |
| `maxItems` | integer | Maximum number of job listings to save across all searches. |
| `includeDescriptionHtml` | boolean | Also save each job description as HTML next to the plain text. |
| `includeCompanyRatings` | boolean | Look up each employer's Indeed rating and review count. Off by default; a rating that cannot be read is left out of the record. |
| `includeContacts` | boolean | Extract email addresses and phone numbers written in the posting's own description text (pattern extraction, not an Indeed field). Off by default. |
| `includeCompanyReviews` | boolean | Fetch the first page of each employer's Indeed reviews (up to 20 full reviews with pros/cons and sub-ratings); combine with Include company ratings. Off by default. |
| `includeCompanySalaries` | boolean | Fetch each employer's Indeed salaries page (total salary reports, satisfaction and the broader salary-by-title list); combine with Include company ratings. Off by default. |
| `expandBeyondCeiling` | boolean | Indeed's app search stops at roughly 600-900 unique jobs per query. When a search reaches that ceiling, split its time range into date windows and merge them, so the run returns the full set Indeed's index holds for the query. |

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

```json
{
  "searchQueries": [
    "web developer in San Francisco"
  ],
  "country": "US",
  "location": "San Francisco",
  "radius": 25,
  "easyApplyOnly": false,
  "maxItems": 3,
  "includeDescriptionHtml": false,
  "includeCompanyRatings": false,
  "includeContacts": false,
  "includeCompanyReviews": false,
  "includeCompanySalaries": false,
  "expandBeyondCeiling": false
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/vexaloom-labs~indeed-job-search-scraper-with-salary-and-benefits/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/vexaloom-labs~indeed-job-search-scraper-with-salary-and-benefits/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: `jobTitle`, `company`, `location`, `salaryText`, `salarySource`, `workplaceType`, `companyRating`, `datePosted`, `applyUrl`, `jobUrl`.

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