Facebook Public Follower & Following Snapshot Tool: MCP config, n8n workflow and API

{
  "startUrls": [
    {
      "url": "https://www.facebook.com/nike"
    }
  ],
  "mode": "followers",
  "maxItems": 8,
  "maxItemsPerTarget": 0,
  "includeProfileDetails": false,
  "deduplicateRows": false
}

---
name: facebook-public-follower-and-following-snapshot
description: "Facebook Page/Profile follower and following rows collected through public cursor pagination, plus per-target summaries with the actual collection name, reported list size, pagination completeness, access state, and follower/following counts. Optional includeProfileDetails enrichment adds row-level counts and About contact/category fields when Facebook exposes them. Runs the Apify Actor nimbryxo-studio/facebook-public-follower-and-following-snapshot. Use when the user needs Facebook data with fields such as recordType, name, profileId, profileTypename, position, collectionName and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "nimbryxo-studio/facebook-public-follower-and-following-snapshot"
  store-url: "https://apify.com/nimbryxo-studio/facebook-public-follower-and-following-snapshot"
---

# Facebook Public Follower & Following Snapshot Tool

Use this skill to fetch Facebook data with the Apify Actor `nimbryxo-studio/facebook-public-follower-and-following-snapshot` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `startUrls` | array, required | One or more Facebook Page or Profile targets. Accepts full URLs, profile.php?id=..., /people/name/id/ (plus /followers, /following, /friends, or /both suffixes), /p/..., and URLs already ending in /followers, /following, or ?sk=... . |
| `mode` | one of `followers`, `following`, `both`, `friends` | Which public list(s) to collect. 'both' collects Followers and Following. 'friends' is a legacy alias: Facebook does not expose Friends to logged-out visitors, so it returns the Followers collection with isFallback=true. |
| `maxItems` | integer | Hard cap on row records across all targets. The default is 50; the daily prefill uses 8. Set 8 to reproduce the old 8-row preview behavior. |
| `maxItemsPerTarget` | integer | Optional cap per target (0 = no per-target cap). Use it to stop one large account from using the whole maxItems budget. |
| `searchQuery` | string | Keep only accounts whose name contains this text (Facebook's own in-list search, case-insensitive substring). Empty means no filter; one-character queries are treated as no filter because Facebook ignores them. |
| `includeProfileDetails` | boolean | Adds row-level follower/following counts, category, email, phone, website, address, work, education, current city, and hometown when Facebook exposes them. |
| `deduplicateRows` | boolean | When enabled, each profileId/profileUrl is emitted once across all targets and modes (first occurrence wins). Per-target pagination duplicates are always removed. |

Example `input.json` (the Actor's published prefill):

```json
{
  "startUrls": [
    {
      "url": "https://www.facebook.com/nike"
    }
  ],
  "mode": "followers",
  "maxItems": 8,
  "maxItemsPerTarget": 0,
  "includeProfileDetails": false,
  "deduplicateRows": false
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~facebook-public-follower-and-following-snapshot/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/nimbryxo-studio~facebook-public-follower-and-following-snapshot/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `recordType`, `name`, `profileId`, `profileTypename`, `position`, `collectionName`, `profileUrl`, `isVerified`, `location`, `accessState`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.