ZipRecruiter Job Search Results & Salary Scraper: MCP config, n8n workflow and API

{
  "mode": "search",
  "searchQueries": [
    "registered nurse"
  ],
  "locations": [
    "Chicago, IL"
  ],
  "jobType": "any",
  "workplace": "any",
  "daysPosted": 0,
  "radiusMiles": 0,
  "salaryMin": 0,
  "salaryMax": 0,
  "fetchDescriptions": false,
  "includeCompanyProfile": false,
  "maxItems": 3,
  "maxSearches": 1,
  "salaryRoles": [
    "registered nurse"
  ],
  "salaryLocations": [
    "Chicago, IL"
  ]
}

---
name: ziprecruiter-job-search-results-and-salary-scraper
description: "One flat dataset with job postings and salary benchmark records. Job rows carry the full description, structured pay, company profile, benefits, dates and apply link; salary rows carry median, percentile and average pay. Runs the Apify Actor vexaloom-labs/ziprecruiter-job-search-results-and-salary-scraper. Use when the user needs ZipRecruiter data with fields such as type, recordType, id, jid, listingKey, openSeatId 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/ziprecruiter-job-search-results-and-salary-scraper"
  store-url: "https://apify.com/vexaloom-labs/ziprecruiter-job-search-results-and-salary-scraper"
---

# ZipRecruiter Job Search Results & Salary Scraper

Use this skill to fetch ZipRecruiter data with the Apify Actor `vexaloom-labs/ziprecruiter-job-search-results-and-salary-scraper` 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 |
| --- | --- | --- |
| `mode` | one of `search`, `byUrls`, `salary` | Search job postings, scrape URLs you already have, or get salary benchmarks for a role and location. |
| `searchQueries` | array | Job titles or keywords, e.g. `registered nurse` or `software engineer`. Every keyword is searched in every location below. |
| `locations` | array | Cities, states, ZIP codes or `United States` for a nationwide search. Every keyword is searched in every location. |
| `startUrls` | array | Search, job, company or salary URLs. Use this with `Scrape specific URLs`; filters already in a search URL are kept. |
| `jobType` | string | Employment-type filter for keyword searches. |
| `workplace` | one of `any`, `remote`, `hybrid`, `onsite` | Work arrangement for keyword searches. |
| `experienceLevels` | array | Restrict to one or more seniority levels. Empty means no filter. |
| `daysPosted` | integer | Only jobs posted within the last N days. 0 means any time. |
| `radiusMiles` | integer | Distance around each location. 0 uses ZipRecruiter's default. |
| `salaryMin` | integer | Only jobs whose advertised annual pay reaches this amount. 0 means no lower bound. |
| `salaryMax` | integer | Only jobs whose advertised annual pay stays at or below this amount. Best effort; 0 means no upper bound. |
| `fetchDescriptions` | boolean | Fetch each posting's detail page for the complete description, benefits, company profile and apply details. Off gives faster card-only rows. |
| `includeCompanyProfile` | boolean | Add industry, website, size, headquarters, rating and about text from the posting's company data. |
| `maxItems` | integer | Maximum number of job or salary records to return across all searches and URLs. |

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

```json
{
  "mode": "search",
  "searchQueries": [
    "registered nurse"
  ],
  "locations": [
    "Chicago, IL"
  ],
  "jobType": "any",
  "workplace": "any",
  "daysPosted": 0,
  "radiusMiles": 0,
  "salaryMin": 0,
  "salaryMax": 0,
  "fetchDescriptions": false,
  "includeCompanyProfile": false,
  "maxItems": 3,
  "maxSearches": 1,
  "salaryRoles": [
    "registered nurse"
  ],
  "salaryLocations": [
    "Chicago, IL"
  ]
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/vexaloom-labs~ziprecruiter-job-search-results-and-salary-scraper/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~ziprecruiter-job-search-results-and-salary-scraper/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: `type`, `recordType`, `id`, `jid`, `listingKey`, `openSeatId`, `matchId`, `url`, `title`, `company`, `companyId`, `companyUrl`, `companyLogo`, `companyWebsite`, `companyIndustries`, `companySize`, `companyHqLocation`, `companyRating`, `companyAbout`, `companyFoundedYear`.

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