Facebook Business Page Finder by Keyword & City: MCP config, n8n workflow and API

{
  "startUrls": [
    {
      "url": "https://www.facebook.com/nike"
    }
  ],
  "strictLocation": false,
  "minFollowers": 0,
  "verifiedOnly": false,
  "contactFilter": "any",
  "includeReviews": false,
  "includeFailedPages": true,
  "failOnEmpty": false,
  "maxItems": 1,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}

---
name: facebook-business-page-finder-by-keyword-and-city
description: "One record per Facebook business Page with identity, public contact details, social links, followers, recommendation metrics, open status, business details, Page Transparency data, images, and reviews. Runs the Apify Actor nimbryxo-studio/facebook-business-page-finder-by-keyword-and-city. Use when the user needs Facebook data with fields such as pageName, category, address, followers, recommendPercentage, facebookUrl 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-business-page-finder-by-keyword-and-city"
  store-url: "https://apify.com/nimbryxo-studio/facebook-business-page-finder-by-keyword-and-city"
---

# Facebook Business Page Finder by Keyword & City

Use this skill to fetch Facebook data with the Apify Actor `nimbryxo-studio/facebook-business-page-finder-by-keyword-and-city` 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 | Direct Facebook page URLs to enrich, for example https://www.facebook.com/ozonecoffeeuk. Can be combined with pageIds and searchTerms. |
| `pageIds` | array | Facebook numeric Page IDs, usernames, or page URLs. Numeric IDs are fetched through https://www.facebook.com/id. |
| `searchTerms` | array | Keywords for Facebook page discovery, for example Coffee Shop or Dentist. Each term is combined with each location as a text query. Facebook keyword search requires a cookie containing both c_user and xs. |
| `locations` | array | City or region names added to the search query as a soft hint. Facebook does not expose a reliable city filter, so always verify the enriched address. Use strictLocation to drop rows whose address does not contain the location. |
| `strictLocation` | boolean | Drop pages whose enriched address does not contain the search location. This is a best-effort post-filter, not an exact city boundary. |
| `categoryFilter` | array | Keep pages whose enriched category contains any of these terms (case-insensitive). Filtering happens after enrichment. |
| `minFollowers` | integer | Keep pages with at least this many followers. Pages with no follower count are dropped when this is above 0. |
| `verifiedOnly` | boolean | Keep only pages whose public payload explicitly marks them as verified. |
| `contactFilter` | one of `any`, `email`, `phone`, `website` | Keep only lead-ready pages that expose the selected contact field. |
| `includeReviews` | boolean | Fetch the public reviews tab and include reviews when Facebook exposes them. Adds one request per page. Review coverage is partial. |
| `includeFailedPages` | boolean | Emit diagnostic rows with errorCode, detailsError, and fieldsFound for pages that cannot be enriched. This prevents silent empty runs. |
| `failOnEmpty` | boolean | Fail the run when zero page rows are produced. Leave off to finish successfully with diagnostic rows explaining why nothing was found. |
| `maxItems` | integer | Maximum number of successful page rows. Failed rows do not consume this limit. |
| `cookies` | string | Optional. Needed only for keyword discovery. c_user and xs are enough. Accepts a JSON array of cookie objects or a raw name=value; name2=value2 Cookie header. Page enrichment works without cookies. |

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

```json
{
  "startUrls": [
    {
      "url": "https://www.facebook.com/nike"
    }
  ],
  "strictLocation": false,
  "minFollowers": 0,
  "verifiedOnly": false,
  "contactFilter": "any",
  "includeReviews": false,
  "includeFailedPages": true,
  "failOnEmpty": false,
  "maxItems": 1,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~facebook-business-page-finder-by-keyword-and-city/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-business-page-finder-by-keyword-and-city/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: `pageName`, `category`, `address`, `followers`, `recommendPercentage`, `facebookUrl`, `pageUrl`, `pageId`, `city`, `phone`, `email`, `website`, `messenger`, `reviewCount`, `openStatus`, `priceRange`, `services`, `isVerified`, `creationDate`, `adStatus`.

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