Pige Immobiliere: French Real Estate CRM Leads

Four portals, every morning, by hand. This Actor does the pige immobilière once: it aggregates annonces immobilières from PAP, Bien'ici, Leboncoin and SeLoger, merges the same property listed on several portals into a single lead, and flags the ones that are new since your last run. What comes out is a CRM-ready feed with price, surface, rooms, €/m², DPE and every source URL. It is built for agents immobiliers, chasseurs d'appartements, marchands de biens and acquisition teams.

Use cases: agents immobiliers, chasseurs, marchands de biens

• Agents immobiliers: daily pige by city or department without copy-pasting four portals.
• Chasseurs d'appart / marchands: fresh owner listings and under-the-radar stock pushed into a CRM.
• Market monitors: track available stock, prices, and €/m² by zone every morning.
• Lead enrichment workflows: send deduplicated property leads to Google Sheets, Airtable, HubSpot or a webhook via Apify integrations.

What this pige immobilière scraper does

• Multi-source French pige: run one search across PAP, Bien'ici, Leboncoin and SeLoger through the upstream French real-estate scraper.
• Deduplication across portals: the same property listed on several sites becomes one CRM lead with all source URLs preserved.
• CRM-ready export: stable crmLeadId, firstSeenAt, price, surface, rooms, €/m², DPE/GES, owner-vs-agency signal, source portals and URLs.
• First-seen tracking: scheduled runs remember previous listings and flag isNewSinceLastRun so your CRM only imports fresh leads.
• Safe input caps: maximum 5 sources, 20 cities, 50 postal codes, and 200 results per source to prevent runaway runs.
• Runs with defaults: PAP + Bien'ici in Lyon works without a residential proxy; enable Leboncoin/SeLoger when you provide a French residential proxy through the upstream actor.

Input example

{
  "sources": ["pap", "bienici", "leboncoin", "seloger"],
  "transaction": "buy",
  "cities": ["lyon"],
  "propertyTypes": ["appartement"],
  "priceMax": 350000,
  "maxResultsPerSource": 20,
  "publishedWithinHours": 72
}

Output example

One dataset item per deduplicated CRM lead:

{
  "crmLeadId": "fr-immo-7e2e4b...",
  "monitorKey": "lyon-buy-apartments",
  "firstSeenAt": "2026-07-06T06:00:00.000Z",
  "isNewSinceLastRun": true,
  "title": "Studio neuf Lyon 7",
  "city": "Lyon",
  "postalCode": "69007",
  "priceEur": 168000,
  "surfaceM2": 28,
  "rooms": 1,
  "pricePerM2": 6000,
  "sourcePortals": ["pap"],
  "sourceUrls": ["https://www.pap.fr/annonces/..."],
  "ownerType": "owner"
}

Data in each CRM lead

Field	What it holds
crmLeadId	Stable ID of the deduplicated property
firstSeenAt	First run that saw this listing
isNewSinceLastRun	True when the lead did not exist on the previous run
title	Listing title from the source portal
city / postalCode	Where the property is
priceEur	Listing price in euros
surfaceM2 / rooms	Living surface and number of rooms
pricePerM2	Price per square meter
ownerType	Owner or agency signal
sourcePortals / sourceUrls	Every portal the property was found on
monitorKey	The zone or search this lead belongs to

Pricing

Pay per event: you are charged per CRM-ready dataset item returned by this actor, plus the upstream scraper cost for the portals scanned. Start with maxResultsPerSource: 20 to validate your zone before scaling. The source scraper currently advertises $5 / 1,000 listings; this wrapper is calibrated for the same low-volume daily pige use case.

Personal data

The output schema documented above carries no seller name, no phone number and no email address: it holds property data and the public URL of each listing. Deciding what you do next with those leads is on you. If you import them into a CRM and contact anyone, you are the data controller for that processing, and the source portals' terms of use plus GDPR and CNIL rules apply to you.

FAQ

Does it scrape Leboncoin and SeLoger directly? No. It calls the existing Apify actor dltik/pige-immo-fr-scraper, which already handles the French portal-specific scraping and proxy requirements. This actor adds CRM export, first-seen tracking, stricter input caps, and a stable deduplicated lead schema.

Why do PAP and Bien'ici run by default? They are the safer default because the upstream actor says they work without residential proxy. Leboncoin and SeLoger are available, but require French residential proxy through the upstream actor.

How does deduplication work? Listings are grouped by postal code, city, price, surface, rooms, property type and title fingerprint. The most complete record is kept, while all source portals and URLs are preserved.

Can I schedule it daily? Yes. Use one scheduled task per zone. The actor stores a baseline per monitor and flags isNewSinceLastRun on later runs.