Property Finder MENA Listings & Agent Contact Extractor: MCP config, n8n workflow and API

{
  "mode": "search",
  "country": "ae",
  "city": "dubai",
  "purpose": "buy",
  "propertyType": "apartment",
  "bedrooms": "any",
  "furnishing": "any",
  "completionStatus": "any",
  "maxItems": 2,
  "includeDetails": true
}

---
name: property-finder-mena-listings-and-agent-contact
description: "Dataset of Property Finder listings, agent profiles and brokerages with prices, location, amenities, permit data, media and public broker/listing contact details. Runs the Apify Actor dataspryva/property-finder-mena-listings-and-agent-contact. Use when the user needs Property Finder data with fields such as title, purpose, price, priceCurrency, propertyType, bedrooms 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: "dataspryva/property-finder-mena-listings-and-agent-contact"
  store-url: "https://apify.com/dataspryva/property-finder-mena-listings-and-agent-contact"
---

# Property Finder MENA Listings & Agent Contact Extractor

Use this skill to fetch Property Finder data with the Apify Actor `dataspryva/property-finder-mena-listings-and-agent-contact` 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`, `listings`, `agents`, `brokers`, required | What to scrape. Search listings by filters, scrape specific listing URLs, or collect agent/broker profiles. |
| `country` | one of `ae`, `sa`, `qa`, `bh`, `eg` | Market to search or the country used for bare agent/broker ids. |
| `city` | string | City, province or governorate to search. Choose All cities for a country-wide search. |
| `purpose` | one of `buy`, `rent`, `commercial-buy`, `commercial-rent` | Buy, rent, or the commercial equivalents. |
| `propertyType` | string | Residential types: apartment, villa, townhouse, penthouse, duplex, compound, land, whole building, half floor. Commercial types: office, shop, warehouse, factory, showroom. |
| `bedrooms` | string | Bedroom filter for residential searches. Studio is supported for apartments and mixed-type searches. |
| `furnishing` | one of `any`, `furnished`, `unfurnished` | Furnished or unfurnished. Leave on Any furnishing to include both. |
| `completionStatus` | one of `any`, `completed`, `off_plan` | Ready or off-plan. Applies to residential for-sale searches; ignored for rentals and commercial searches. |
| `maxItems` | integer | Maximum number of listings or profiles to return. |
| `includeDetails` | boolean | Open each listing page to add the full photo gallery, permit validation link, licences, floor plans and agent ratings. Turn off for a faster, lighter dataset. |

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

```json
{
  "mode": "search",
  "country": "ae",
  "city": "dubai",
  "purpose": "buy",
  "propertyType": "apartment",
  "bedrooms": "any",
  "furnishing": "any",
  "completionStatus": "any",
  "maxItems": 2,
  "includeDetails": true
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~property-finder-mena-listings-and-agent-contact/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/dataspryva~property-finder-mena-listings-and-agent-contact/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: `title`, `purpose`, `price`, `priceCurrency`, `propertyType`, `bedrooms`, `bathrooms`, `city`, `community`, `brokerName`, `brokerPhone`, `isVerified`, `url`, `priceDuration`, `pricePerArea`, `pricePerAreaUnit`, `offeringType`, `size`, `sizeUnit`, `furnished`.

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