Facebook Page Following Scraper – Profile Export

See which profiles a public Facebook Page visibly follows. Facebook Page Following Scraper collects the accessible outgoing following list, with profile names, IDs, URLs and source-Page context in each result.

Use Page usernames or URLs to build a record of visible connections across selected Pages. Pagination follows the collection Facebook exposes; it does not guarantee a complete relationship graph. No Facebook login or cookies are required.

At a glance	Details
📥 Input	Page usernames, numeric IDs as strings, or Page URLs
📤 Output	Visible followed profiles, their public labels and the Page that follows them
🔐 Login required	No Facebook credentials or cookies
📄 Collection	Pagination; pagesPerProfile defaults to 1
💾 Delivery	One row per distinct followed-profile returned for each source Page; JSON, CSV, Excel or API

What the Facebook Page Following Scraper extracts 🔎

The Actor separates each publicly listed followed profile into its own row, while retaining the Page that supplied the relationship.

• Followed profile ID, username, name, URL and profile picture
• Available profile subtitle, type and verification flag
• Source Page identifiers, username, name, URL and picture
• Public following-collection total and any supplied notice
• Further pages of the visible Following collection when available

How to scrape Facebook Page following 🚀

1. Add Page usernames or URLs to inspect the public profiles listed in their Following sections.
2. Set pagesPerProfile; start with 1 to inspect the available collection.
3. Start the Actor and inspect the dataset’s status column.
4. Export successful rows or connect the results to your workflow.

{
  "inputList": [
    "Meta"
  ],
  "pagesPerProfile": 1
}

Facebook Page following data fields and output 📦

Field group	Included data
Followed profile	ID, username, name, URL and profile picture
Public labels	Subtitle, profile type and verification
Source Page	source_profile.* identity and profile columns
Collection summary	Source total and any notice
Result status	Submitted input and success or failed status

Complete representative success item. All names, counts and media addresses below are illustrative, not a live result; every current output field is included.

{
  "input": "HarborCoffee",
  "status": "success",
  "id": "104567890123789",
  "username": "CityRoasters",
  "name": "City Roasters",
  "url": "https://www.facebook.com/CityRoasters/",
  "profile_picture_url": "https://media.example.com/city-roasters.jpg",
  "subtitle": "Coffee roaster",
  "type": "page",
  "is_verified": false,
  "source_profile.id": "100091234567890",
  "source_profile.page_id": "104567890123456",
  "source_profile.username": "HarborCoffee",
  "source_profile.name": "Harbor Coffee",
  "source_profile.url": "https://www.facebook.com/HarborCoffee/",
  "source_profile.profile_picture_url": "https://media.example.com/harbor-coffee-profile.jpg",
  "source_profile.is_verified": false,
  "source_total": 34,
  "notice": ""
}

The table and JSON use the same flat keys and values, with one row per result. Dots in keys such as source_profile.name are literal parts of the field name.

The source_profile.* fields describe the Page you submitted; the ordinary id, name and url fields describe a profile that Page follows. source_total is the source’s collection figure, not a promised row count.

Successful rows may contain empty strings, zeroes, false flags, empty lists or nulls when optional information is unavailable. Do not interpret a default count or flag as a confirmed source fact. Failed rows retain input, set status to failed, and use null result fields.

Input requirements and coverage ⚙️

Parameter	Type	Required	Rules
inputList	array of strings	Yes	At least one Page username, numeric ID as a string, or supported Page URL; no default target.
pagesPerProfile	integer	No	Default 1; minimum 1, maximum 100. Maximum result pages to attempt per input.

Accepted inputs include Page usernames, numeric IDs as strings, standard Facebook Page URLs, profile.php?id=... links and legacy /pages/NAME/ID links. This actor reads outgoing following relationships; it does not read the Page’s Followers collection.

The initial results count as page 1. Further pages are requested only while Facebook supplies a usable continuation. Page size is controlled by the source, so this is not an exact record limit.

Provide an array of strings, not URL objects. An invalid overall input structure stops processing without dataset rows; an invalid target within a valid list is recorded as a failed result. The input schema does not set a maximum list length; choose batch sizes appropriate to your run limits.

Facebook Page following use cases 🎯

Public connection mapping

Build a source-to-followed-profile table for selected Pages using stable IDs and public URLs.

Brand ecosystem research

Inspect visible connections to partner organizations, local businesses and other public profiles without inferring a formal business relationship.

Following-list monitoring

Compare scheduled snapshots of the accessible Following collection to identify visible changes.

Pricing and billable followed-profile rows 💰

Check the Actor’s Pricing tab for the current model and rate. That configuration is authoritative.

Under dataset-item pricing, saved success and failed rows can count toward charges. Each distinct returned followed-profile saves a success row. Invalid inputs, an empty first collection or a persistently unavailable result page can save failed rows; a later failure does not remove earlier results. Retries do not independently add dataset rows. All details remain in their result row.

Facebook Page Following Scraper API and integrations 🔌

Replace $ACTOR_ID with the ID shown in the Actor’s API tab and $APIFY_TOKEN with your Apify token.

curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"inputList":["Meta"],"pagesPerProfile":1}'

Start runs through the Apify API, schedules or client libraries. Use webhooks for completion events and export the dataset to spreadsheets, Make, Zapier, storage or your own application.

Reliability and limits ⚠️

Following lists can be hidden, limited or unavailable to public requests. A visible connection indicates only that the profile appears in that Page’s public Following collection; it does not establish ownership, endorsement or a commercial relationship.

Available rows are saved page by page, and repeated IDs within one source collection are skipped. Pagination stops when the source provides no further accessible results. An empty initial collection or persistent request failure can produce a failed row.

Frequently asked questions ❓

Is this the same as collecting a Page’s followers?

No. Following is the outgoing list of profiles the Page follows. Followers are the people or Pages that follow it.

Will the result contain every followed profile?

Only profiles exposed in the accessible public collection can be returned. Visibility and pagination may limit the result.

How do I identify the source Page?

Use the source_profile.* columns. The unprefixed profile fields describe the followed profile.

Can I request an exact number of profiles?

No. pagesPerProfile limits pages to attempt, and Facebook controls how many profiles each page exposes.

Does the Actor require Facebook credentials?

No. It uses publicly accessible responses without asking for a Facebook login or cookies.

Support, responsible use, and related actors 🛟

For help with missing or unexpected results, open an Issue on this Actor’s Apify page with the run link, a public example input and the fields you expected. Keep tokens and credentials out of support messages.

Use public data only for purposes you are authorized to pursue, respecting privacy, platform terms and content rights.