# Facebook Page Contact Info Scraper (`scrapeflux/facebook-page-contact-info-scraper`) Actor Facebook Page Contact Info Scraper extracts publicly available contact details from Facebook business pages. Collect emails, phone numbers, websites, addresses, page information, and business details for lead generation, outreach, market research, competitor analysis, and business prospecting. - **URL**: https://apify.com/scrapeflux/facebook-page-contact-info-scraper.md - **Developed by:** [ScrapeFlux](https://apify.com/scrapeflux) (community) - **Categories:** Lead generation, Social media, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $3.99 / 1,000 results This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ### Facebook Page Contact Info & Email Scraper ⚡ Finding emails and contact details for Facebook Pages is slower than it should be—copying bios and hunting for phone numbers one by one wastes hours. **Facebook Page Contact Info & Email Scraper** automates scraping of bio text, emails, phone numbers, addresses, and other contact fields from a list of public Facebook Page URLs. This facebook page contact scraper (and facebook page email extractor) is built for lead research and outreach teams that need clean, structured results fast. Use it when you have a batch of target pages and want contact info & emails ready to analyze or export. In a single run, you can process multiple pages and get results into your Apify dataset within seconds of each page finishing. --- ### See the Data: Sample Output Here's a real record from a single run: ```json { "url": "https://www.facebook.com/humansofnewyork/", "page_name": "Humans of New York", "bio": "Stories from around the world. Contact: team@honyexample.org", "emails_from_bio": ["team@honyexample.org"], "EMAIL": "team@honyexample.org", "PHONE": "+1 212-555-0199", "MOBILE_PHONE": "+1 917-555-0123", "ADDRESS": "New York, NY", "WEBSITE": "https://example.org", "DISPLAY_SUBTEXT": "Community", "scraped_at": "2026-06-07T10:14:22.123456", "success": true } ```` **Output Fields** | Field | Type | What It Tells You | |---|---|---| | `page_name` | string | null | The Facebook Page name extracted from the page content (useful for deduping and matching to your CRM records). | | `url` | string | The normalized Facebook Page URL that was processed for this record. | | `bio` | string | null | The Page bio/description text, which can be useful for context and additional manual verification. | | `emails_from_bio` | array | All email addresses detected inside the bio text (great as a first pass for a facebook business page email scraper workflow). | | `EMAIL` | string | null | A single email value extracted from the About contact fields (when available). | | `PHONE` | string | null | The phone number listed in the Page contact fields (useful for “scrape facebook page phone and email” style research). | | `MOBILE_PHONE` | string | null | A mobile phone value from the contact fields, if present. | | `ADDRESS` | string | null | The address text extracted from the Page contact information. | | `WEBSITE` | string | null | The website URL text captured from the contact fields. | | `DISPLAY_SUBTEXT` | string | null | Category/subtext information pulled from the contact fields (helpful for segmentation). | | `scraped_at` | string | Timestamp (ISO format) showing when the actor captured the data. | | `success` | boolean | Indicates whether the actor marked the scrape as successful for that page. | Export your full dataset as JSON, CSV, or Excel from the Apify dashboard. *** ### Setting It Up Drop this into your `input.json` and you're ready to go: ```json { "facebookPageUrls": [ { "url": "https://www.facebook.com/humansofnewyork/" }, { "url": "https://www.facebook.com/BlueSpringsSidingandWindows" } ] } ``` | Parameter | Required | What It Does | |---|---|---| | `facebookPageUrls` | ✅ | A list of Facebook Page URLs to scrape for contact info & email extraction. Each item is provided as a source with a `url`. | | ↳ `facebookPageUrls[].url` | ✅ | The Facebook Page URL (public page) you want the facebook page contact info & email tool to process. | *** ### What It Does This actor scrapes contact information from the public pages you provide. #### Extract emails and contact fields from Facebook Pages It collects bio/description content and extracts emails found in the bio text, making it a practical facebook page inbox email finder workflow. It also reads the Page About contact fields to pull additional items like phone numbers and addresses when they’re available. #### Turn a list of URLs into structured lead records Feed multiple Facebook Page URLs and get consistent, integration-ready records in your dataset. This makes it easy to build a facebook page email list scraper pipeline for outreach, enrichment, or research. #### Captures both “bio emails” and contact-field emails The output includes `emails_from_bio` (emails detected within the bio) plus separate fields like `EMAIL` when the actor extracts email from contact fields. That combination is what you want when your goal is “find email from facebook page” reliably across different Page layouts. #### Works with public pages in bulk You can run it across a batch of pages and capture what’s available per Page without manually opening each profile. The process is designed for scalable facebook page contact scraper use cases, where you care about results more than manual copy/paste. #### Includes success signaling per page Each record contains `success: true` or `success: false`, so you can quickly separate usable contacts from pages that didn’t yield enough data. If something goes wrong for a page, the actor still outputs an error field (when applicable) along with the `url`. Overall, **Facebook Page Contact Info & Email Scraper** helps you extract contact details from Facebook pages at scale and turn them into clean rows you can act on. *** ### Why Facebook Page Contact Info & Email Scraper? There are plenty of ways to pull data from Facebook Pages—here's why **Facebook Page Contact Info & Email Scraper** stands out. #### Built for real lead-research outputs The actor focuses on contact-relevant fields (bio, emails, phone numbers, addresses, and website), not just raw page text. That makes it a better facebook business page email scraper for teams that need usable leads, not clutter. #### Structured results written per page You get a dedicated dataset record per processed page, with `url`, `scraped_at`, and `success` to support downstream filtering. This is helpful when you’re trying to build a repeatable scrape facebook page contact info workflow. #### Designed for resilience and clean failure handling It uses retry logic and records per-page outcomes so you can keep your run moving and identify which pages failed. When you’re running a facebook page email extractor for outreach, this reduces manual cleanup work after the run completes. *** ### Real-World Use Cases Here's how different teams put Facebook Page Contact Info & Email Scraper to work: **Sales Teams**\ A sales development rep has a spreadsheet of target Facebook Pages for local service providers. They run Facebook Page Contact Info & Email Scraper to pull emails, phone numbers, and addresses into a dataset, then export it into their workflow for faster follow-up. The result is less time spent copying contact details and more time qualifying leads. **Marketing Agencies**\ An agency needs contact info for multiple client industries and wants consistent fields for segmentation. They scrape facebook page contact info & email tool results for each public Page URL, then use `DISPLAY_SUBTEXT` and contact fields to group prospects by category and route them to the right campaign. **Freelance Researchers**\ A researcher collecting public-facing organizational contacts wants auditable, structured records. They use the facebook page email extractor outputs like `bio`, `emails_from_bio`, and `scraped_at` so they can review context alongside extracted emails when validating sources. **Data Analysts & Enrichment Specialists**\ An analyst combines multiple datasets and needs Facebook Page contact details as enrichment signals. They run the actor, then join on `url` or `page_name` to create a unified contact table—making it simpler to analyze how contact info is presented across pages. **Automation & Developer Workflows**\ A developer triggers runs and stores results into their pipeline for downstream processing. They consume the dataset records (including `success` and contact fields like `EMAIL`, `PHONE`, and `ADDRESS`) to automatically enrich leads and trigger alerts when certain fields are missing. *** ### How to Run It No code required. Here's how to get your first results in under 5 minutes: 1. **Open the actor on Apify**\ Go to the actor page on Apify (visit https://console.apify.com) and open **Facebook Page Contact Info & Email Scraper**. 2. **Enter your inputs**\ Add your public Facebook Page URLs in `facebookPageUrls` (each entry should provide a `url`). 3. **Configure proxy settings (recommended)**\ If you want better reliability for larger batches, enable proxy support in the run settings. 4. **Start the run and watch the live log**\ The actor will process each Page and log progress, including attempts for fetching. 5. **Open the Dataset tab to see live results**\ Records appear as each page finishes, including `page_name`, `EMAIL`, phone/address fields, `scraped_at`, and `success`. 6. **Export your results in your preferred format**\ Download JSON, CSV, or Excel from the Apify dashboard for further analysis or CRM import. The whole setup takes under 5 minutes — results start appearing within seconds of launch. *** ### Export & Integration Options Once your data is collected, Facebook Page Contact Info & Email Scraper fits directly into your existing workflow. Export formats are available directly from the dataset tab in the Apify dashboard, including JSON, CSV, and Excel. If you’re pushing results into a tool like Sheets or Airtable, you can use Apify’s native integrations or connect via Zapier / Make. You can also access results programmatically via the Apify API and trigger downstream actions with webhooks when your run completes. For scheduled runs, set the actor to run automatically on a schedule so your lead lists stay fresh. *** ### Pricing Facebook Page Contact Info & Email Scraper runs on Apify, which includes a **free tier** — no credit card needed to start. You’ll typically begin with $5 platform credits on sign-up, which is enough for several real test runs. After that, scaling works on a pay-as-you-go basis based on Actor compute unit (CU) usage. For heavier workloads and ongoing pipelines, check Apify’s plans for the best fit. Start free at [apify.com](https://apify.com) — scale up when you need to. *** ### Reliability & Limitations | What We Handle | How | |---|---| | Retries for failed requests | Up to 3 retry attempts with back-off for page fetching. | | Proxy support | Built-in proxy support for reliable scraping. | | Per-page outcomes | Each page includes `success` so you can filter failures quickly. | | Partial data collection | Records are created per page with whatever fields were found. | | Email extraction from bio | Extracts email addresses from the bio text into `emails_from_bio`. | | Dataset saving during the run | Each page result is written immediately as it’s processed. | Limitations: the actor only works with **publicly available data** visible on the pages you provide. If a Page has no email or contact fields published, those fields may be empty in the output. For enterprise-scale needs or custom configurations, reach out and we’ll help. *** ### Frequently Asked Questions #### Is there a free plan? Yes, Apify offers a free tier with monthly usage credits on sign-up. You can use it to test Facebook Page contact scraping on a small batch before scaling up. #### Do I need to log in or create an account on Facebook? No. This facebook page contact info scraper works with public web data from Facebook Pages, so you don’t need a Facebook login or credentials. #### How accurate is the extracted data? Accuracy depends on what the Page owner has published. The actor extracts bio text and finds email addresses in that bio text, plus contact-field values like `EMAIL`, `PHONE`, `ADDRESS`, and `WEBSITE` when available. #### How many results can I get per run? You can include multiple entries in `facebookPageUrls`, and the actor processes them one by one while saving results per page. The exact number you should expect depends on how many URLs you provide and how much data each Page exposes publicly. #### How fresh is the data? The actor stamps each record with `scraped_at` when it processes that Page. If you rerun later, you’ll capture new `scraped_at` values and any changes the Page made since the previous run. #### Is this legal and does it comply with GDPR / CCPA? This actor accesses **publicly available data** only. It’s your responsibility to comply with GDPR, CCPA, platform Terms of Service, and any applicable local regulations when storing or using the extracted information. #### Can I export to Google Sheets or Excel? Yes. You can export your dataset as JSON, CSV, or Excel from the Apify dashboard, and then import it into tools like Google Sheets. If you prefer automation, you can also connect using Zapier / Make. #### Can I schedule this to run automatically? Yes. You can set the actor to run on a schedule in Apify so your facebook page email extractor runs automatically at the cadence you choose. #### Can I access results via the API? Yes. Since the actor writes results to an Apify dataset, you can retrieve them programmatically via the Apify API. #### What happens when the actor encounters an error? If an error occurs for a specific page, the actor will still output a record with `success: false` and an error field (when applicable) along with the `url` and `scraped_at`. You can filter failed pages quickly using `success` after the run. *** ### Get Help & Use Responsibly Got a question about Facebook Page Contact Info & Email Scraper or a feature you'd like added? Reach out at —we welcome feedback and can help troubleshoot scraping output. If you want ideas, we can extend filtering and export-friendly formatting for facebook page contact scraper workflows. **This actor collects data only from publicly available data.** It does not access private accounts, login-gated pages, or password-protected content. You are responsible for GDPR, CCPA, and Facebook’s Terms of Service compliance when using the results; for data removal requests, contact . Use responsibly, ethically, and only for lawful purposes. # Actor input Schema ## `facebookPageUrls` (type: `array`): List of Facebook Page URLs to scrape for contact info. ## Actor input object example ```json { "facebookPageUrls": [ { "url": "https://www.facebook.com/humansofnewyork/" }, { "url": "https://www.facebook.com/BlueSpringsSidingandWindows" } ] } ``` # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "facebookPageUrls": [ { "url": "https://www.facebook.com/humansofnewyork/" }, { "url": "https://www.facebook.com/BlueSpringsSidingandWindows" } ] }; // Run the Actor and wait for it to finish const run = await client.actor("scrapeflux/facebook-page-contact-info-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "facebookPageUrls": [ { "url": "https://www.facebook.com/humansofnewyork/" }, { "url": "https://www.facebook.com/BlueSpringsSidingandWindows" }, ] } # Run the Actor and wait for it to finish run = client.actor("scrapeflux/facebook-page-contact-info-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "facebookPageUrls": [ { "url": "https://www.facebook.com/humansofnewyork/" }, { "url": "https://www.facebook.com/BlueSpringsSidingandWindows" } ] }' | apify call scrapeflux/facebook-page-contact-info-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=scrapeflux/facebook-page-contact-info-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Facebook Page Contact Info Scraper", "description": "Facebook Page Contact Info Scraper extracts publicly available contact details from Facebook business pages. Collect emails, phone numbers, websites, addresses, page information, and business details for lead generation, outreach, market research, competitor analysis, and business prospecting.", "version": "1.0", "x-build-id": "BVDZKNgouHoCp2hGu" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/scrapeflux~facebook-page-contact-info-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-scrapeflux-facebook-page-contact-info-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/scrapeflux~facebook-page-contact-info-scraper/runs": { "post": { "operationId": "runs-sync-scrapeflux-facebook-page-contact-info-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/scrapeflux~facebook-page-contact-info-scraper/run-sync": { "post": { "operationId": "run-sync-scrapeflux-facebook-page-contact-info-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "required": [ "facebookPageUrls" ], "properties": { "facebookPageUrls": { "title": "Facebook Page Contact Scraper URLs", "type": "array", "description": "List of Facebook Page URLs to scrape for contact info.", "items": { "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "title": "URL of a web page", "format": "uri" } } } } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```