Zillow For-Sale, Rent & Sold Listing Extractor: MCP config, n8n workflow and API

{
  "search": "Houston, TX",
  "mode": "BUY",
  "maxItems": 3,
  "endPage": 1,
  "fsboOnly": false,
  "foreclosureOnly": false,
  "auctionOnly": false,
  "newConstructionOnly": false,
  "includePending": false,
  "openHouseOnly": false,
  "priceReducedOnly": false,
  "scrapeDetails": false
}

---
name: zillow-for-sale-rent-and-sold-listing-extractor
description: "One record per Zillow property, home or rental building. Records keep the 33 legacy fields and add sold, tax, parcel, builder, agent, MLS, open-house, GraphQL-enriched detail and building fields when Zillow exposes them. Runs the Apify Actor nimbryxo-studio/zillow-for-sale-rent-and-sold-listing-extractor. Use when the user needs Zillow data with fields such as url, zpid, status, price, zestimate, rentZestimate 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-for-sale-rent-and-sold-listing-extractor"
  store-url: "https://apify.com/nimbryxo-studio/zillow-for-sale-rent-and-sold-listing-extractor"
---

# Zillow For-Sale, Rent & Sold Listing Extractor

Use this skill to fetch Zillow data with the Apify Actor `nimbryxo-studio/zillow-for-sale-rent-and-sold-listing-extractor` 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 |
| --- | --- | --- |
| `search` | string | City, ZIP, neighborhood, county or state to search (for example 'Houston, TX' or '77002'). |
| `mode` | one of `BUY`, `RENT`, `SOLD`, required | Search active for-sale listings, rentals, or recently sold listings. |
| `maxItems` | integer | Maximum number of records for the whole run across all sources (1-5000). |
| `endPage` | integer | Maximum search result pages per search task (1-24). Zillow returns up to 41 listings per page. |
| `fsboOnly` | boolean | Only include for-sale-by-owner listings. |
| `foreclosureOnly` | boolean | Only include foreclosure listings. |
| `auctionOnly` | boolean | Only include auction listings. |
| `newConstructionOnly` | boolean | Only include new-construction listings. |
| `includePending` | boolean | Add pending and under-contract listings to active results. |
| `openHouseOnly` | boolean | Only include listings with an open house. |
| `priceReducedOnly` | boolean | Only include listings with a price reduction. |
| `scrapeDetails` | boolean | Fetch each search result's detail page for description, photos, MLS, tax, open house and building floor plans. Explicit URLs, ZPIDs and addresses are always enriched. |

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

```json
{
  "search": "Houston, TX",
  "mode": "BUY",
  "maxItems": 3,
  "endPage": 1,
  "fsboOnly": false,
  "foreclosureOnly": false,
  "auctionOnly": false,
  "newConstructionOnly": false,
  "includePending": false,
  "openHouseOnly": false,
  "priceReducedOnly": false,
  "scrapeDetails": false
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~zillow-for-sale-rent-and-sold-listing-extractor/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-for-sale-rent-and-sold-listing-extractor/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: `url`, `zpid`, `status`, `price`, `zestimate`, `rentZestimate`, `beds`, `baths`, `sqft`, `lotSize`, `yearBuilt`, `propertyType`, `stories`, `parking`, `address`, `city`, `state`, `zipCode`, `latitude`, `longitude`.

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