Commercial Property AU

Extract Australian commercial property listings with full detail-page data — descriptions, highlights, detailed attributes, coordinates, nearby places, and rich metadata per listing.

Key Features

• Detailed output: Description, highlights, detailed attributes, nearby places, documents, tours, demographics
• All listing types: for-sale, for-lease, sold, and leased
• Commercial filters: Industrial, retail, offices, land/development, medical, hotel/leisure, and more
• Automatic pagination: Pages through search results until the limits are reached
• Deduplication: No duplicate listings across pages or search URLs

How to Use

Search by Location

Set mode to location and add locations with state required and optional suburb/postcode/region.

Direct URLs

Set mode to url and provide commercial search result page URLs directly.

Filters

• Listing Type: for-sale, for-lease, sold, leased
• Property Types: industrial-warehouse, retail, offices, land-development, showrooms-bulky-goods, hotel-motel-leisure, medical-consulting, commercial-farming, other
• Sort Order: featured, date-desc, date-asc, price-desc, price-asc
• Price Range: minimum and maximum price
• Area Range: minimum and maximum area

Quick Start

{
  "mode": "location",
  "locations": [
    { "suburb": "Melbourne", "state": "VIC" },
    { "suburb": "Sydney", "state": "NSW", "postcode": "2000" }
  ],
  "listingType": "for-sale",
  "maxListings": 100,
  "maxPages": 5
}

Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step after the scrape — the Apify dataset is never changed.

What gets written to the connector: a condensed, human-readable summary of each record — not the full JSON. Each item becomes one entry with a title (the listing's name / address) and its key fields flattened to plain text (price, beds/baths, agent, URL, …). Nested objects are collapsed to their main value (e.g. an address object → its full-address text) and long lists are trimmed to the first few names. The complete, full-fidelity record always stays in the Apify dataset — the connector copy is a readable digest for browsing in your app.

• Notion → one page per item (title + a summary body), created under the page you set in notionParentPageUrl.
• Linear / Airtable / other → one record/issue per item with the same title + fields.

How to enable:

1. Authorize a connector once under Apify → Settings → Integrations (Notion, Linear, Airtable, or Apify).
2. Select it in the "Pipe results into your apps" input field. (If the picker is empty, you haven't authorized a connector yet.)
3. For Notion, also set notionParentPageUrl to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip — the export only runs when a connector is selected.

Proxy

An Apify residential proxy is required. Free Apify accounts cannot use residential proxies — runs without one log a warning and return no results. Set the proxy to RESIDENTIAL + AU country in Proxy Configuration (requires a paid Apify plan with residential proxy access).

Limits

• Maximum Listings: controls how many listings are pushed in one run
• Maximum Pages: limits search result pages per location or URL
• Empty arrays and objects are omitted from dataset output