Facebook Marketplace Listing & Price Extractor: MCP config, n8n workflow and API

{
  "mode": "urls",
  "startUrls": [
    {
      "url": "https://www.facebook.com/marketplace/nyc/search/?query=laptop"
    }
  ],
  "searchQueries": [
    "laptop"
  ],
  "location": "nyc",
  "country": "US",
  "radiusKm": 65,
  "category": "all",
  "sortBy": "relevance",
  "condition": "any",
  "deliveryMethod": "all",
  "availability": "all",
  "exactMatch": false,
  "maxItems": 3,
  "maxItemsPerUrl": 3,
  "maxPagesPerUrl": 1,
  "scrapeMode": "fast",
  "includeListingDetails": false,
  "includeAllPhotos": false,
  "rehostImages": false,
  "deduplicateAcrossInputs": true
}

---
name: facebook-marketplace-listing-and-price-extractor
description: "One JSON object per Facebook Marketplace listing. Canonical groups: identity and provenance (id, listingUrl, sourceUrl, sourceType, inputIndex, searchQuery, locationQueried, recordType, scrapedAt), core fields (title, description, price, strikethroughPrice, condition, conditionLabel, attributes, categoryId, categoryName, categorySlug, categoryPath), location (locationText, city, state, latitude… Runs the Apify Actor nimbryxo-studio/facebook-marketplace-listing-and-price-extractor. Use when the user needs Facebook data with fields such as title, price, city, state, locationText, condition 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-marketplace-listing-and-price-extractor"
  store-url: "https://apify.com/nimbryxo-studio/facebook-marketplace-listing-and-price-extractor"
---

# Facebook Marketplace Listing & Price Extractor

Use this skill to fetch Facebook data with the Apify Actor `nimbryxo-studio/facebook-marketplace-listing-and-price-extractor` 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 |
| --- | --- | --- |
| `mode` | one of `auto`, `search`, `urls`, `items` | What to scrape. auto uses startUrls when present and otherwise builds a keyword search. search builds a search from searchQueries plus location. urls scrapes the given Marketplace search, category, or city-feed URLs. |
| `startUrls` | array | Marketplace search, city-category, global-category, city-feed, or /marketplace/item/ URLs. In mode=items, a bare numeric listing ID is also accepted. |
| `searchQueries` | array | One to 20 keywords or phrases (mode=search or mode=auto without URLs). Each query becomes one source. |
| `location` | string | Marketplace location slug, city, postal code, or address used by keyword search (mode=search or mode=auto without URLs). Examples: nyc, Austin, Texas, 90210, London. |
| `country` | string | ISO 3166-1 alpha-2 country used when resolving a human location. Use GB for London, CA for Toronto, and so on. |
| `radiusKm` | integer | Search radius in kilometres for keyword or category search. URL mode keeps the radius in the URL unless you set this explicitly. |
| `category` | string | Marketplace category. If searchQueries is empty, the actor opens the city category feed (or the global category feed for a human location). |
| `sortBy` | one of `relevance`, `newest`, `oldest`, `price_asc`, `price_desc`, `distance` | Server-side sort where Marketplace supports it, plus a client-side re-sort by price or posting time. Rows without a price sort last. |
| `condition` | one of `any`, `new`, `used_like_new`, `used_good`, `used_fair` | Server-side condition filter in search/category modes. In deep mode the detail condition is checked too; fast URL rows without condition data are kept. |
| `deliveryMethod` | one of `all`, `shipping`, `local` | Client-side filter over the listing's delivery types. Listings without delivery data are dropped when this filter is active. Legacy local_pickup is accepted as local. |
| `availability` | one of `all`, `available`, `sold`, `pending` | Client-side status filter. Search feeds are mostly available; sold and pending are more common on direct item pages. |
| `exactMatch` | boolean | Keep only rows whose title (and description in deep mode) contains every query word. |
| `maxItems` | integer | Global output limit across all sources. |
| `maxItemsPerUrl` | integer | Per-source output limit. |

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

```json
{
  "mode": "urls",
  "startUrls": [
    {
      "url": "https://www.facebook.com/marketplace/nyc/search/?query=laptop"
    }
  ],
  "searchQueries": [
    "laptop"
  ],
  "location": "nyc",
  "country": "US",
  "radiusKm": 65,
  "category": "all",
  "sortBy": "relevance",
  "condition": "any",
  "deliveryMethod": "all",
  "availability": "all",
  "exactMatch": false,
  "maxItems": 3,
  "maxItemsPerUrl": 3,
  "maxPagesPerUrl": 1,
  "scrapeMode": "fast",
  "includeListingDetails": false,
  "includeAllPhotos": false,
  "rehostImages": false,
  "deduplicateAcrossInputs": true
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~facebook-marketplace-listing-and-price-extractor/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-marketplace-listing-and-price-extractor/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: `title`, `price`, `city`, `state`, `locationText`, `condition`, `deliveryTypes`, `seller`, `primaryPhotoUrl`, `sourceUrl`, `sourceType`, `qualityStatus`, `accessState`, `marketplace_listing_title`, `listing_price`, `location`, `is_sold`, `is_pending`, `marketplace_listing_seller`, `listingUrl`.

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