Facebook Page Contact Scraper

Get phone numbers, emails and websites from any public Facebook page — in seconds, without a login or API key.

Paste one URL or a thousand. Each page returns a clean, structured contact record ready to export or push to your CRM.

---

Why use this scraper?

• No login required — works on any public page
• No API key, no app approval — zero setup, start immediately
• Fast — results in seconds, even for large batches
• Complete — phone, email, all websites, social links, Instagram handle, category, bio, followers in one row
• Bulk-ready — paste hundreds of URLs and run once

---

What you get

One row per Facebook page:

Field	Description	Example
pageName	Page display name	Africa Eco Race
phone	Phone number (if public)	06 40 62 86 03
email	Email address (if public)	contact@africarace.com
website	Primary website (if public)	africarace.com
websites	All websites listed on the page	["africarace.com", "africarace.fr"]
socialLinks	TikTok, LinkedIn, Instagram URLs	["https://tiktok.com/@..."]
instagramHandle	Instagram username	lloyddavisluxury
address	Physical address (if public)	12 rue de la Paix, Paris
priceRange	Price range for shops/restaurants	€€
category	Page category	Sports Event
bio	Short description	THE RACE TO DAKAR - THE ORIGINS
followers	Follower count	108945
pageId	Facebook numeric page ID	100064657362737
profileImageUrl	Profile picture URL	https://scontent-...
pageUrl	Canonical page URL	https://www.facebook.com/africaecorace/
status	ok, no_contact, or error:xxx	ok
scrapedAt	Timestamp	2026-04-06T10:00:00.000Z

---

How to use

Step 1 — Add your Facebook page URLs

In the Page URL(s) field, paste one or more Facebook page URLs:

https://www.facebook.com/africaecorace/
https://www.facebook.com/cocacola
https://www.facebook.com/pages/Some-Page/123456789

Vanity URLs, numeric IDs, and /pages/ format all work.

Step 2 — Run and export

Click Run. Results appear live in the dataset. Export to CSV, JSON, or XLSX directly from the Apify console.

---

Example output

{
  "pageName": "LLOYD & DAVIS",
  "phone": "01 87 37 55 69",
  "email": "contact@lloyd-davis.com",
  "website": "lloyd-davis.com",
  "websites": ["recrutement-lloyd-davis.com", "lloyd-davis-luxury.com", "lloyd-davis.com"],
  "socialLinks": ["https://www.instagram.com/lloyddavisluxury", "https://tiktok.com/@lloydanddavis", "https://www.linkedin.com/company/lloyd-davis/"],
  "instagramHandle": "lloyddavisluxury",
  "category": "Real Estate Agent",
  "bio": "Lloyd & Davis, réseau immobilier international, experts en résidentiel, luxe et en expatriation.",
  "followers": 1996,
  "pageId": "100057626180863",
  "pageUrl": "https://www.facebook.com/lloydanddavis/",
  "status": "ok",
  "scrapedAt": "2026-04-06T10:00:00.000Z"
}

---

What gets scraped — and what doesn't

Only publicly visible information is extracted — exactly what anyone would see visiting the page without an account. Contact details hidden behind a login will appear as empty fields (status: no_contact).

Data point	Available
Phone number	✅ If the page has made it public
Email address	✅ If the page has made it public
All websites	✅ If listed in the Intro section
Social links (TikTok, LinkedIn…)	✅ If listed in the Intro section
Instagram handle	✅ If listed in the Intro section
Category	✅ Always present
Bio / description	✅ Always present
Follower count	✅ Always present
Posts, comments, DMs	❌ Not scraped

---

Tips for best results

• Batch your URLs — group everything in one run rather than running pages one by one
• Private pages — personal profiles, private groups and deactivated pages return an error status
• Contact not showing — some pages only display contact info to logged-in users; those will return status: no_contact
• Apify cloud vs your laptop — Runs default to residential Apify Proxy (Console: URLs only). Use { "proxyConfiguration": { "useApifyProxy": false } } in raw JSON / input.json if you want a direct connection (e.g. local testing without proxy billing).
• Why only two pages worked in parallel — Two simultaneous requests from the same IP often look like automation; the Actor loads one page at a time on Apify, waits longer between pages, and reuses cookies across requests. User-Agent tweaks alone are not enough when the IP is heavily flagged.

---

Use cases

• B2B lead generation — build contact lists from Facebook business pages in your niche
• Market research — collect category and description data at scale
• CRM enrichment — complete existing records with phone, email, and social links
• Event & sponsorship outreach — find organiser contacts directly from event pages

---

Input (API / JSON only)

The Console form only asks for URLs. By default (no extra keys) the Actor uses residential Apify Proxy and 5 parallel workers — not shown in the form. To turn that off or tune it, pass raw JSON (API or input.json locally).

Key	Type	Default	Notes
parallelWorkers	integer	5 when proxy works, 1 if proxy is off	Cap 5. Each worker: own cookie jar + header variant + separate proxy session.
maxConcurrency	integer	(legacy)	Fallback if parallelWorkers is omitted.
delayBetweenRequestsMs	integer	4500 on Apify, 2000 locally	Per-worker pause after each page (ms).
loginWallCooldownMs	integer	18000 on Apify, 10000 locally	Global pause after a login-wall failure. Set 0 to disable.
proxyConfiguration	object	residential on	Set { "useApifyProxy": false } for direct connections (no proxy billing). Or change groups / country in the usual Apify shape.

Fingerprint limits: All workers still use Node.js + got (same TLS stack). True browser-grade fingerprints need Playwright/Puppeteer — heavier and slower. Multiple workers + residential proxy sessions is the practical way to scale throughput on Facebook.

---

Custom needs?

Contact corentin@outreacher.fr for custom builds, bulk runs, or integrations.