Zillow Market Trends Scraper: MCP config, n8n workflow and API

{
  "mode": "regionTrends",
  "locations": [
    "Austin, TX"
  ],
  "historyMonths": 24,
  "historyMetric": "zhvi",
  "dataset": "zhviAllHomes",
  "geography": "city",
  "state": "all",
  "sortBy": "sizeRank",
  "maxItems": 3
}

---
name: zillow-market-trends-scraper
description: "One dataset with three record types: regionMarketTrends (ZHVI, ZORI, sale and list metrics, forecasts and benchmarks per location), marketHistoryObservation (monthly rows) and marketObservation (ranked Zillow Research rows). Runs the Apify Actor nimbryxo-studio/zillow-market-trends-scraper. Use when the user needs Zillow data with fields such as recordType, location, locationType, slug, url, sourceUrl 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/zillow-market-trends-scraper"
  store-url: "https://apify.com/nimbryxo-studio/zillow-market-trends-scraper"
---

# Zillow Market Trends Scraper

Use this skill to fetch Zillow data with the Apify Actor `nimbryxo-studio/zillow-market-trends-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 `regionTrends`, `history`, `marketScan`, required | What to collect. regionTrends = one detailed record per location. history = tidy monthly rows per location. marketScan = one row per region from a Zillow Research dataset. |
| `locations` | array | (mode=regionTrends, history) Cities, states, counties, ZIP codes or neighborhoods, e.g. 'Austin, TX', 'Travis County, TX', '78701', 'Barton Hills, Austin, TX', 'Texas'. |
| `historyMonths` | integer | (mode=regionTrends, history) Months of monthly history to include per metric. Zillow's page carries up to 100 months; larger values are capped at 100. |
| `historyMetric` | one of `zhvi`, `zori`, `both` | (mode=history) Which monthly series to emit as tidy rows. |
| `dataset` | string | (mode=marketScan) Zillow Research series to scan. Each dataset supports a subset of geographies; the actor tells you if the selected geography is unavailable. |
| `geography` | one of `metro`, `state`, `county`, `city`, `zip`, `neighborhood`, `us` | (mode=marketScan) Region level to scan. Available levels depend on the dataset. |
| `state` | string | (mode=marketScan) Keep only regions in this state. 'all' keeps every state. |
| `nameContains` | string | (mode=marketScan) Case-insensitive substring filter on the region name, e.g. 'Travis' or 'Springfield'. |
| `regionIds` | array | (mode=marketScan) Exact Zillow RegionIDs to keep, e.g. '3101'. Values not in the selected dataset are ignored. |
| `sortBy` | string | (mode=marketScan) Order rows and assign a 1-based rank over all matches before maxItems truncation. |
| `maxItems` | integer | Hard cap on emitted records for this run. |

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

```json
{
  "mode": "regionTrends",
  "locations": [
    "Austin, TX"
  ],
  "historyMonths": 24,
  "historyMetric": "zhvi",
  "dataset": "zhviAllHomes",
  "geography": "city",
  "state": "all",
  "sortBy": "sizeRank",
  "maxItems": 3
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~zillow-market-trends-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/nimbryxo-studio~zillow-market-trends-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: `recordType`, `location`, `locationType`, `slug`, `url`, `sourceUrl`, `dataSource`, `regionId`, `regionName`, `regionType`, `regionDisplayName`, `state`, `stateCode`, `county`, `metro`, `city`, `zhviLatest`, `zhviYoY`, `zhviAsOf`, `zhviChange1mPct`.

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