Zillow Property Manager Directory by City: MCP config, n8n workflow and API

{
  "mode": "location",
  "locations": [
    "Dallas, TX"
  ],
  "specialties": [
    "property-management"
  ],
  "isTopAgent": false,
  "maxManagers": 3,
  "endPage": 1,
  "maxReviews": 3
}

---
name: zillow-property-manager-directory-by-city
description: "Property manager profiles from Zillow — business and contact details, ratings, reviews, licenses, team, service areas, rental and for-sale listings, and social links. Runs the Apify Actor vexaloom-labs/zillow-property-manager-directory-by-city. Use when the user needs Zillow data with fields such as name, businessName, phone, reviewRating, reviewCount, location 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/zillow-property-manager-directory-by-city"
  store-url: "https://apify.com/vexaloom-labs/zillow-property-manager-directory-by-city"
---

# Zillow Property Manager Directory by City

Use this skill to fetch Zillow data with the Apify Actor `vexaloom-labs/zillow-property-manager-directory-by-city` 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 `location`, `urls` | What to scrape. Search by location uses the directory; Scrape specific URLs reads directory pages and profile pages you supply. |
| `locations` | array | One location per line: city and state ("Dallas, TX"), ZIP code ("92104"), or a neighborhood ("Hyde Park, Austin, TX"). Each location is searched with the Property Management specialty filter. |
| `startUrls` | array | Zillow professionals directory pages or individual profile URLs. Legacy /professionals/property-manager-reviews/... URLs are converted to the live directory path automatically. |
| `specialties` | array | Zillow professional specialties to include. The actor is built for property managers, so Property Management is selected by default; add another specialty to widen the search. |
| `languages` | array | Only include profiles that speak at least one of these languages. Leave empty for all languages. |
| `isTopAgent` | boolean | Only include profiles Zillow has awarded its Top Professional badge. |
| `maxManagers` | integer | Maximum number of property manager profiles to return. Zillow serves at most 400 per location and filter combination (16 per page, 25 pages). |
| `endPage` | integer | Maximum directory pages to crawl per location or directory URL. Each page contains 16 profiles and Zillow clamps at page 25. |
| `maxReviews` | integer | Maximum recent reviews to include per profile. Zillow exposes the 10 most recent reviews on a profile page. |

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

```json
{
  "mode": "location",
  "locations": [
    "Dallas, TX"
  ],
  "specialties": [
    "property-management"
  ],
  "isTopAgent": false,
  "maxManagers": 3,
  "endPage": 1,
  "maxReviews": 3
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/vexaloom-labs~zillow-property-manager-directory-by-city/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~zillow-property-manager-directory-by-city/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: `name`, `businessName`, `phone`, `reviewRating`, `reviewCount`, `location`, `profileUrl`.

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