Les Porteclés agents

For sales teams, recruiters, and analysts who need a structured export of Les Porteclés negotiators across France: names, role lines, cities, post codes, regions, map coordinates, and profile URLs — ready for CRM or enrichment workflows.

What it extracts

Category	Fields
Identity	agentId, slug, profileUrl, displayName
Role	jobTitle (line shown on the listing / profile)
Geography	city, postCode, region, country, lat, lng
Media	photoUrl

Note: Email and phone are not exposed as plain text on public profile pages; they are not included in the dataset.

Important

• Public data only — Use results in line with GDPR, e-marketing rules, and Les Porteclés’ terms of use.
• Field gaps — Some fields may be empty if the site omits them.
• Full runs — The directory spans many pages; allow enough run time and memory for a full export.
• Apify Cloud — The Actor uses Apify Proxy by default on the platform for reliable access (same pattern as other directory Actors in this workspace).

Quick start (Apify Console)

1. Create a task from this Actor.
2. Choose Full directory or URLs (see below).
3. Start the run and open Dataset for JSON or CSV export.

Modes

• Full directory — Collects all agents from the paginated public listing (optionally cap with maxResults).
• URLs — Paste profile URLs like https://www.lesportecles.com/agents/2486-…. The Actor opens each page and extracts structured fields.

Input

Field	Description
mode	list (full directory) or urls (profile URLs only).
startUrls	Profile URLs — URLs mode only.
maxResults	0 = no cap. Use a small number for tests.
concurrency	Parallelism for writing dataset rows.
listConcurrency	Parallelism for HTTP requests (listing or profiles).
fetchTimeout	Per-request timeout in milliseconds.

JSON example (full directory, capped)

{
  "mode": "list",
  "maxResults": 100
}

JSON example (URLs)

{
  "mode": "urls",
  "startUrls": [
    { "url": "https://www.lesportecles.com/agents/2486-jose-manuel-esteves-46260-varaire-france" }
  ]
}

How it works

1. List mode — Fetches each directory page and parses structured cards from the HTML.
2. URLs mode — Fetches each profile page and parses the same fields from the public layout.
3. Normalizes rows and pushes one dataset item per agent.

Output sample

{
  "agentId": 2486,
  "slug": "jose-manuel-esteves-46260-varaire-france",
  "profileUrl": "https://www.lesportecles.com/agents/2486-jose-manuel-esteves-46260-varaire-france",
  "displayName": "José-Manuel Esteves",
  "jobTitle": "Agent commercial indépendant de SAS IMMOBILIER EMAIL - EI",
  "city": "Varaire",
  "postCode": "46260",
  "region": "Lot",
  "country": "France",
  "lat": 44.363951,
  "lng": 1.719144,
  "photoUrl": "https://cdn.lesportecles.com/..."
}

Local development

npm install
npm test
apify run

• Local runs use input.json when you are not on the Apify platform; task input from the platform still overrides when deployed.
• Dataset is stored under storage/datasets/default/. A UTF-8 output.csv may be written at the project root on successful local runs.

Support

Contact corentin@outreacher.fr if you need a custom scraper, extra fields, or automation around this data.