Property Finder Broker & Agent Email Scraper

Extract public broker and real-estate agent contact data from Property Finder’s broker directories across the UAE, Egypt, Bahrain, Qatar, and Saudi Arabia markets. The actor discovers public broker profile URLs from directory pages, then parses server-rendered broker pages and their embedded public agent data. Property Finder Group’s Turkish property portal is Zingat and is intentionally outside this Property Finder-directory actor.

What it returns

• Brokerage name and public profile URL
• Agent name, public email, public phone, and brokerage URL
• One structured record per broker or agent email
• Country code, source URL, and scrape timestamp

Leave countries empty to search all five active Property Finder directory markets. Use searchUrls when you already have specific public /en/find-broker directory URLs. includeAgents is enabled by default because agent emails are the main enrichment value.

The actor only extracts contact information that is publicly embedded in the requested Property Finder pages. It does not log in, bypass access controls, infer private emails, or validate email deliverability. Use the output in accordance with Property Finder terms, applicable privacy and marketing laws, and any required authorization.

Input example

{"countries":["ae","eg"],"maxResults":100,"maxPagesPerCountry":5,"includeAgents":true}

Output example

{"recordType":"agent","country":"ae","brokerName":"Example Realty","brokerUrl":"https://www.propertyfinder.ae/en/broker/example-123","agentName":"Jane Doe","email":"jane@example.com","allEmails":["jane@example.com"],"phone":"+971501234567","website":null,"sourceUrl":"https://www.propertyfinder.ae/en/broker/example-123","scrapedAt":"2026-07-16T12:00:00.000Z"}

Use cases

• Build public prospect lists and qualify organizations or professionals before responsible outreach.
• Compare listings, locations, availability, and market signals for property research.
• Run a one-off research job and export the structured result as JSON, CSV, Excel, XML, or RSS from Apify.
• Schedule the same input to monitor changes over time and send completed datasets to a webhook or integration.
• Feed schema-shaped records into a database, spreadsheet, BI tool, or AI workflow with the source URL retained for verification.

Run Property Finder Broker & Agent Email Scraper with the Apify API

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('muhammadafzal/propertyfinder-brokers-emails').call({
  "countries": [],
  "searchUrls": [],
  "maxResults": 50,
  "maxPagesPerCountry": 3,
  "includeAgents": true,
  "maxConcurrency": 2
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

You can also run the Actor from Apify Console, schedules, webhooks, the REST API, Make, Zapier, n8n, or the hosted Apify MCP server.

Pricing and cost control

This Actor uses pay-per-event pricing. Charges follow the live event definitions shown below.

Event	Price (USD)	When it is charged
apify-actor-start	$0.00005	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
broker-email-result	$0.005	One public broker or agent record saved to the dataset, including email and source profile fields.

For example, 100 broker-email-result events cost $0.5, plus any enabled Actor-start event. Empty or failed work should be checked in the run log and dataset before reuse.

Reliability and limitations

Public websites and upstream APIs change over time. Start with a small result limit, inspect the dataset and run log, and keep a known-good input for scheduled canary runs. A valid query can return no records when the source has no matches. If a run is blocked, rate-limited, or missing an expected field, reduce concurrency or scope where the input supports it and include the run ID in a support report.

The Actor does not guarantee that every optional field is present on every record. Treat absent values as unavailable from that source response, not as proof that the real-world value does not exist.

Frequently asked questions

Can I schedule Property Finder Broker & Agent Email Scraper?

Yes. Use an Apify schedule to run the same saved input at a chosen interval, then connect a webhook or integration to process the dataset when the run finishes.

How should I test a new input?

Begin with the prefilled example or a small limit. Confirm that the output fields, source coverage, runtime, and live charges match your workflow before increasing the scope.

How do I export the results?

Open the run's default dataset in Apify Console and export JSON, CSV, Excel, XML, or RSS. Applications can retrieve the same records through the Apify API client or REST dataset endpoint.

Can an AI agent call this Actor?

Yes. Add muhammadafzal/propertyfinder-brokers-emails through the hosted Apify MCP server or call it through the API. The Actor's input and dataset schemas help agents construct valid requests and interpret returned records.