Property24 Price-Drop & New Listing Monitor

Watch any Property24 search and get alerted the moment something changes. Point this monitor at a South African property search — for sale or to rent, any city, suburb or filtered search — put it on a schedule, and each run returns only what changed since the last run: brand-new listings, price drops, price increases and delistings. Quiet runs return nothing, so you can watch a search every few minutes, all day, and only ever see real movement.

Built for automation: drop it into Apify Schedules, n8n, Make or Zapier and turn every change into an email, a Slack message, a Google Sheet row or a webhook.

Why a monitor instead of a scraper?

A scraper gives you everything every time — and you then have to figure out what's new. This monitor remembers what it saw last time and hands you a clean feed of just the changes:

• 🆕 New listings — the moment a property matching your search goes live.
• 📉 Price drops — with the old price, new price, amount and percentage dropped.
• 📈 Price increases — optional, on by default.
• 🗑️ Delistings — listings that were sold, withdrawn or expired.

Perfect for buyers hunting a specific area, agents tracking the competition, investors watching price movements, and anyone building property alerts.

How it works

1. Give it a search — a location path like cape-town/western-cape/432, or paste one or more Property24 results-page Start URLs from your browser.
2. Put it on a schedule (e.g. every 15 minutes) in Apify or your automation tool.
3. First run quietly records the current listings as a baseline and returns nothing — so a fresh schedule doesn't dump the whole search at you. (Prefer the full list up front? Turn on Emit all listings on the first run.)
4. Every run after that returns only the changes since the previous run.

Each monitor keeps its own separate memory, so you can run several different searches side by side without them interfering — just give each one a Monitor name.

What you get

One row per detected change:

Example change row

{
  "changeType": "price_drop",
  "listingNumber": "117588912",
  "title": "3 Bedroom Apartment for sale in Marina Da Gama",
  "price": 3100000,
  "oldPrice": 3300000,
  "newPrice": 3100000,
  "dropAmount": 200000,
  "dropPercent": 6.06,
  "suburb": "Marina Da Gama",
  "bedrooms": 3,
  "bathrooms": 2,
  "url": "https://www.property24.com/for-sale/marina-da-gama/cape-town/western-cape/10213/117588912",
  "detectedAt": "2026-09-05T12:34:56.000Z"
}

How to use it

1. Add Property24 Price-Drop & New Listing Monitor to your Apify account and open its input.
2. Choose the Listing intent — For sale or To rent — and enter a Location path like cape-town/western-cape/432 (copy it from a Property24 results URL), or paste one or more Start URLs from your browser.
3. Optionally set a Monitor name so this search keeps its own memory.
4. Save it, then create a Schedule (e.g. every 15 or 30 minutes) — or trigger it from n8n, Make or Zapier.
5. Connect the output to email, Slack, a spreadsheet or a webhook and let the alerts come to you.

Input

{
  "intent": "for-sale",
  "locationUrlPath": "cape-town/western-cape/432",
  "maxItems": 200,
  "monitorName": "cape-town-houses",
  "emitBaselineOnFirstRun": false,
  "detectPriceIncrease": true,
  "detectRemovals": true
}

FAQ

How often should I run it? As often as you like — every 15 or 30 minutes works well. Runs with no changes return nothing, so frequent checks stay cheap.

Will the first run flood me with results? No. By default the first run silently records a baseline and returns nothing; you only start getting rows from the second run onward. Turn on Emit all listings on the first run if you'd rather get the full list up front.

Can I watch several searches at once? Yes. Give each one a different Monitor name and each keeps its own independent memory of what it has seen.

Does it work for rentals too? Yes — set Listing intent to To rent, or paste a to-rent results URL.

What export and integration options are there? JSON, CSV, Excel and XML, plus the Apify API, webhooks and native integrations with n8n, Make, Zapier and more.

You pay only for what the run returns. Set a maximum cost per run and it stops cleanly at that limit.