French Real Estate Pige CRM Export

French real estate pige CRM export aggregates French property listings from Leboncoin, SeLoger, PAP and Bien'ici, deduplicates the same property across portals, and outputs a CRM-ready lead feed with first-seen dates. It is built for agents immobiliers, chasseurs, marchands de biens, and acquisition teams who do a daily pige manually.

Features

• 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.

Use cases

• 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.

Input / Output

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"
}

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.

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.