Facebook Pages Scraper

Export public Facebook Page profiles, contact fields, visible audience counts, profile images and optional post links from Page URLs or handles. Facebook Pages Scraper returns structured records for directories, competitor research and reporting, without Facebook login credentials.

Only data exposed to logged-out visitors is available. Some Pages return no usable records, and post-link records do not contain full posts, comments or reactions.

Quick start

1. Add a public Page URL in Facebook Page URLs, or a handle in Facebook Page handles or URLs.
2. Start with one Page and turn off post links if you only need its profile.
3. Run the Actor, then open its dataset to download JSON, CSV or Excel.

{
  "pageUrls": ["NASA"],
  "includePosts": false,
  "maxPostsPerPage": 0
}

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:

• Scrape Restaurant Brand Facebook Pages
• Monitor Competitor Facebook Pages
• Scrape Public Facebook Page Post Links
• Scrape Facebook Page Profiles

What you get

Each available Page produces a profile row with its source identity and available descriptions, contacts, images and public counts. Optional visible-link collection adds post-link rows that repeat Page fields and include a source post URL. These extra rows contain links rather than full post content or engagement details.

Who is it for?

• Directory teams organizing known public Facebook Page records.
• CRM operations teams reviewing available public business-contact fields.
• Social-media researchers comparing public profile and audience-count observations.
• Data teams collecting visible post links for a separate source-review workflow.

How you can use the data

• Prepare a profile-only directory sheet. Use the existing NASA recipe with post links off or the per-Page link limit set to zero. Keep recordType, url, pageId, name and available public contact fields together before updating your own directory.
• Review visible post links separately. Enable post links with a small per-Page cap, then separate post rows from profile rows using recordType. Keep postUrl and available postId for manual review rather than treating them as a full, newest-first timeline.
• Compare public audience snapshots downstream. Store raw count text and parsed values with Page URLs and scrapedAt. Counts may be rounded, and null values do not establish zero audience or an absence of information on every public view.
• Check coverage before importing. Read RUN_SUMMARY for attempted inputs, saved profiles and links, and skip reasons. Review any PENDING_PAGES record before assuming every Page in a larger list was attempted.

Input settings

Provide at least one Page in startUrls or pageUrls. The lists are combined. Neither alternative is globally required. Form prefills are examples, not API defaults.

Setting	JSON key	Summary
Facebook Page URLs	startUrls	Full URLs using Apify's request-list editor
Facebook Page handles or URLs	pageUrls	Handles or full URLs. Defaults to an empty list
Include visible public post links	includePosts	Defaults to true. Profile rows are also saved
Maximum post links per Page	maxPostsPerPage	0–50, default 5. 0 gives profiles only
Proxy configuration	proxyConfiguration	Optional settings. Direct access by default. See field help for supported behavior

There is no keyword search, date filter or sorting input. Add the Page addresses you want to inspect.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

This abbreviated example illustrates the record shape only. It is not an observed Page result or a promise of current values.

{
  "recordType": "page",
  "input": "https://www.facebook.com/example-page",
  "url": "https://www.facebook.com/example-page",
  "handle": "example-page",
  "pageId": null,
  "name": "Example public Page",
  "description": null,
  "website": null,
  "followersCount": null,
  "profileImageUrl": null,
  "coverImageUrl": null,
  "postUrl": null,
  "scrapedAt": "2026-10-24T00:00:00.000Z"
}

Each available Page produces a page row. With post links enabled, additional post rows repeat the Page fields and add postUrl and, when parseable, postId.

More output fields

Fields	Meaning
recordType	page for a profile or post for a visible link
input	Normalized requested Facebook Page URL, not the original handle spelling
url, handle, pageId	Canonical URL and available Page identity
name, title, description, category	Public identity and descriptive fields
website, phone, email, address	Contact fields when exposed publicly
likesText, likesCount	Raw and parsed like counts
followersText, followersCount	Raw and parsed follower counts
talkingAboutText, talkingAboutCount	Raw and parsed talking-about counts
profileImageUrl	Profile image URL when available. Image files are not downloaded
postUrl, postId	Visible link and parsed ID on post-link rows. Null on profile rows
scrapedAt	ISO timestamp captured while processing the Page

coverImageUrl, text, timestampText, timestampIso, reactionCount, commentCount and shareCount are reserved and currently always null. mediaUrls is always an empty array. These are not extracted features.

The dataset provides Page overview, contacts, metrics, post links and complete-data views. The RUN_SUMMARY key-value record includes attempted inputs, saved profile/link counts and per-input skip reasons. If the run approaches its time limit, a PENDING_PAGES record can identify inputs not attempted. Do not assume every submitted Page was processed.

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

The one-time start event is charged after at least one valid Page input has been accepted. A result event is charged for every saved Page profile or visible post-link row. One Page can therefore produce several charged rows when post links are enabled.

Skipped inputs produce no result rows, but the start event still applies if accepted inputs produce no usable records. Use a short Page list and disable or reduce post links when profiles alone meet your needs. See the live Pricing tab for current rates and discounts.

Tips for best results

• Choose profile-only or visible-link output deliberately. Turn links off or use a zero link cap when you only need Page profiles.
• Start with one known Page. Inspect public identity and optional fields before expanding the input list.
• Separate profile and post rows. Filter recordType so repeated Page fields on post-link rows do not inflate your directory counts.
• Keep original count text with parsed values. Rounded and missing public metrics need cautious interpretation.
• Read per-input outcomes before retrying. A canonical current Page URL can help review a skipped target, but an empty success does not prove that an inaccessible Page can be extracted.

Limits and caveats

Only public Pages exposed to logged-out visitors are supported. Facebook login credentials are not inputs, and there is no login bypass, private content, group, comment or full-post extraction. There are no keyword, date-filter or sorting inputs.

Facebook can omit contacts, images or counts. Null values do not establish that a Page has no such information. Missing public identity or a login shell does not prove privacy or deletion. An empty success is not evidence that inaccessible Page data has become available.

Completed extraction with no usable records succeeds with an empty dataset and reasons in RUN_SUMMARY. Mixed batches preserve useful records. Fatal configuration, essential dataset-storage and billing failures still fail the run, as does an acquisition exception on every attempted target.

Visible post links are neither exhaustive nor guaranteed newest-first. Full text, dates, media and engagement details are not collected. Reserved cover-image, text, timestamp and engagement fields remain null, while mediaUrls stays empty, as specified in Output data. Image files are not downloaded.

Near the time limit, PENDING_PAGES can identify unattempted inputs. Compare saved profiles and links with summary counts rather than assuming complete processing. Separate runs and saved examples do not create automatic schedules or monitoring history. Compare exports by URL and collection time in your own workflow.

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-pages-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "pageUrls": [
    "NASA"
  ],
  "includePosts": false,
  "maxPostsPerPage": 0
}
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-pages-scraper').call({
  "pageUrls": [
    "NASA"
  ],
  "includePosts": false,
  "maxPostsPerPage": 0
});
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-pages-scraper').call(run_input={'pageUrls': ['NASA'], 'includePosts': False, 'maxPostsPerPage': 0})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API usage notes

The cURL request starts an asynchronous run. Wait for it to finish, then retrieve records from the Dataset API using the run's defaultDatasetId.

MCP and AI agents

You can ask your AI assistant to collect data with Facebook Pages 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 Pages 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-pages-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 Pages Scraper by Fetch Cat, or give it the identifier fetch_cat/facebook-pages-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 Pages Scraper to retrieve the NASA Page profile with post links off. Show available names, descriptions, public contacts and audience counts with the source URL.”
• “Collect profiles for the 2 known Page URLs I provide and up to 3 visible post links per Page. Separate profile rows from post-link rows and show the source links without claiming full post text or a complete timeline.”
• “Retrieve profile records for my 2 supplied Page handles with post links disabled. Keep raw and parsed follower counts and collection times for my own comparison, and explain any skipped or pending targets.”

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

Is this a Facebook Pages API alternative?

It offers an Apify API for the public Page fields listed above, not Meta's official Graph API, Page management or authenticated content.

Can I export Facebook Page data to CSV or JSON?

Yes. Download the dataset as CSV, Excel, JSON and other supported formats, or consume it through the Dataset API.

Does it need Facebook cookies or login?

No. It uses only information available to logged-out visitors.

Why did a Page return no data?

The response may be limited, login-gated, unavailable or missing usable Page identity. Check RUN_SUMMARY.skippedInputs. The observation alone does not prove the Page is private or deleted.

Can it return full posts or cover images?

No. Optional post rows contain visible links and IDs only. Cover images and the reserved detail fields are not extracted.

Why are the numbers different from Facebook?

Public visibility and rounded display counts vary. These are snapshots of available data, not guaranteed exact live totals.

Related Actors

• Facebook Events Scraper — public event information.
• Facebook Ads Library Scraper — ad-library research.
• Facebook Comments Scraper — Collect visible public post comments with text, displayed dates and available author and engagement fields.
• Facebook Marketplace Scraper — marketplace listings.
• Facebook Reels Scraper — Collect public Reel URLs, IDs and available owner and play-count metadata from known Reels or profile tabs.

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