Facebook Page Details Scraper

Extract public Facebook Page details from URLs or handles into records you can export to CSV, Excel or JSON. Facebook Page Details Scraper returns available Page identity, descriptions, engagement counts, images and contact fields for lead research and CRM enrichment.

Only logged-out public information is supported. Fields can be missing, and inaccessible Pages may return no record. This is not a Facebook posts or comments scraper.

Quick start

1. Paste public Page URLs or handles into Facebook Page URLs or handles.
2. Set Maximum Pages to a small limit, such as 2, and run the Actor.
3. Open the dataset to inspect available fields, then export your results.

{
  "pageUrls": ["NASA", "Meta"],
  "maxItems": 2
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Export Facebook Brand Page Details

What you get

• Input: Facebook Page URLs or handles such as NASA or https://www.facebook.com/Meta.
• Output: One detail record per public Page.
• Key data: Page ID, name, description, public contact data, likes, followers, talking-about counts, image, rating, categories, and social links.
• Exports: JSON, CSV, Excel, XML, RSS, API, webhooks, and MCP through Apify datasets.
• Access: Public logged-out Page information only. No Facebook credentials are requested.

Who is it for?

This Actor is designed for sales and lead-generation teams, CRM operators, market researchers, social-media analysts, agencies and developers who need repeatable public Facebook Page records.

How you can use the data

• Enrich a known-Page CRM list. Supply a small set of canonical Page URLs or handles. Keep pageId, url, name, categories and available website, phone or email fields together, then inspect the source before importing contact details.
• Review public brand profiles. Use the existing NASA and Meta sample with a two-Page cap. Compare available descriptions, profile images and displayed audience counts without treating null values as zero counts or absent contact methods.
• Compare separate Page snapshots downstream. Join your own dated exports by pageId when present, falling back to canonical url. Recurring collection requires your own schedule or integration, and comparison is a separate step rather than built-in change detection.
• Check coverage before updating records. Inspect optional fields and sourceStatus against the Page link. A complete status does not guarantee every field, and missing contact values mean unavailable or unextracted in this response rather than proof that no public contact exists anywhere.

Input settings

Setting	JSON key	Description
Facebook Pages	pageUrls	Public Page URLs or handles. Accepts up to 500 entries.
Start URLs	startUrls	Additional or alternative full Page URLs. Combined with pageUrls.
Maximum Pages	maxItems	Up to 500 unique Pages to attempt. API default is 10, form prefill is 2.
Proxy configuration	proxyConfiguration	Optional proxy settings applied from the first request. Omit for direct access. No automatic proxy fallback.

Duplicate normalized Page URLs are processed once. Invalid hosts and URLs without a Page path are rejected before any network request.

Collect local-business leads

{
  "pageUrls": [
    "https://www.facebook.com/example-business-one",
    "https://www.facebook.com/example-business-two"
  ],
  "maxItems": 10
}

Monitor known Pages

{
  "startUrls": [
    { "url": "https://www.facebook.com/NASA" },
    { "url": "https://www.facebook.com/Meta" }
  ],
  "maxItems": 2
}

Compare records from separate runs by pageId or url. Recurring execution requires your own Apify schedule or integration. It is not built-in change detection.

Output data

Illustrative record shape only, not a fresh extraction or a claim about current Page values. Actual records contain the fields listed below, with unavailable values left null or as empty arrays.

{
  "input": "https://www.facebook.com/NASA",
  "url": "https://www.facebook.com/NASA/",
  "handle": "NASA",
  "pageId": null,
  "name": "Example Page",
  "title": "Example Page",
  "description": null,
  "bio": null,
  "categories": [],
  "website": null,
  "email": null,
  "phone": null,
  "address": null,
  "profileImageUrl": null,
  "likesCount": null,
  "likesDisplay": null,
  "followersCount": null,
  "followersDisplay": null,
  "talkingAboutCount": null,
  "talkingAboutDisplay": null,
  "isVerified": null,
  "rating": null,
  "ratingCount": null,
  "socialLinks": [],
  "scrapedAt": "2026-09-06T00:00:00.000Z",
  "sourceStatus": "partial"
}

Values are returned only when they are visible on the public Page. Nullable fields are not inferred from unrelated viewer or proxy data.

More output fields

Field	Description
input	Original URL or handle supplied by the user.
url	Canonical public Facebook Page URL.
handle	Page handle parsed from the canonical URL.
pageId	Public Facebook Page/profile ID when visible.
name, title	Normalized Page name and full public title.
description, bio	Public Page description or intro text.
categories	Public Page categories when available.
website	Public external website shown by the Page.
email, phone, address	Public lead contact information when visible.
profileImageUrl	Public profile image URL.
likesCount, likesDisplay	Numeric and display versions of public Page likes.
followersCount, followersDisplay	Numeric and display versions of public followers.
talkingAboutCount, talkingAboutDisplay	Numeric and display versions of the public talking-about metric.
isVerified	true when an explicit public verification marker is visible. Otherwise null.
rating, ratingCount	Public rating/review summary when visible.
socialLinks	Explicit public Instagram, LinkedIn, X, YouTube, Pinterest, or Telegram links.
scrapedAt	ISO timestamp for the record.
sourceStatus	complete or partial, based on field availability. complete does not guarantee every field is present.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

A one-time start event is charged when a valid run begins. A result event is charged for each Facebook Page record saved. Inputs that produce no records do not produce result events, but a start charge can still apply when a valid run later fails.

Volume discounts depend on your Apify plan. See the live Pricing tab for current rates and discounts.

Tips for best results

• Start with two or three known Pages. Review field availability before expanding your list.
• Use current canonical Page URLs when available. Invalid hosts and URLs without a Page path are rejected before requests.
• Keep identity and capture times with each export. Join by Page ID when present and fall back to canonical URL for your own comparisons.
• Review nullable contacts at source. A missing value does not prove that a business has no contact method or that no public contact exists elsewhere.
• Check the final outcome when records are missing. The current Actor fails if no requested Page yields details, rather than reporting an empty success.

Limits and caveats

• Only public Facebook Pages visible without logging in are supported.
• Private profiles, private groups, comments, reactions, and login-only details are out of scope.
• Age-gated, region-restricted, removed, or temporarily challenged Pages may not return a record. If none of the requested Pages yields details, the current Actor fails the run rather than returning an empty success.
• Results follow the submitted Page order after duplicate removal, not a popularity sort. Fields vary by the available public response. Contact information should be checked before outreach.
• Facebook can vary public fields by Page and can change its public presentation.
• Contact details and ratings are returned only when explicitly present in public Page information.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~facebook-page-details-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "pageUrls": [
    "NASA",
    "Meta"
  ],
  "maxItems": 2
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/facebook-page-details-scraper').call({
  "pageUrls": [
    "NASA",
    "Meta"
  ],
  "maxItems": 2
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/facebook-page-details-scraper').call(run_input={'pageUrls': ['NASA', 'Meta'], 'maxItems': 2})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Facebook Page Details Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Facebook Page Details Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/facebook-page-details-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Facebook Page Details Scraper by Fetch Cat, or give it the identifier fetch_cat/facebook-page-details-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Facebook Page Details Scraper to retrieve up to 2 Page records for NASA and Meta. Show source links, names, descriptions and available follower counts, marking missing fields.”
• “Collect details for the 3 known public business Page URLs I provide, with a three-Page cap. Show available websites, phones and emails beside their source links for manual CRM review.”
• “Retrieve up to 2 Page records from my supplied handles. Keep Page IDs, canonical URLs and collection times so I can compare them with my own earlier export without treating missing contacts or counts as absent everywhere.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Does this require Facebook cookies, login, or an access token?

No. Do not provide Facebook credentials. The Actor works with information available on public Pages.

Can I export Facebook Page leads to CSV or Excel?

Yes. Open the run dataset and select JSON, CSV, Excel, XML, RSS, or another Apify export format.

Can I run it through an API or MCP?

Yes. Use the Apify REST API, JavaScript/Python clients, webhooks, schedules, or the focused MCP endpoint above.

Why are some fields null?

Facebook does not expose every field on every logged-out Page. The Actor keeps unavailable values null instead of guessing.

Why did a URL return no record?

The URL may not identify a public Page, or the Page may be removed, private, restricted, or unavailable to logged-out visitors.

Is this the same as a Facebook posts scraper?

No. This Actor intentionally returns one Page-detail record per input. Use a dedicated post scraper when you need posts or comments.

Related Actors

• Facebook Pages Scraper — Collect public Page profile and contact fields, visible audience counts and optional post links.
• Facebook Post Search Scraper — Find public posts by keyword, phrase or hashtag and collect their available text, dates and engagement.
• Facebook Groups Search Scraper — Discover public group URLs, names and visible community details by topic or location.
• Facebook Ads Library Scraper — Collect public Meta ad copy, advertiser details and available creative links for advertising research.
• Facebook URL to ID Scraper — Resolve supported Facebook URLs to numeric IDs and typed canonical links for downstream joins.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥