Switching from Yelp Reviews Scraper to Yelp Reviews Scraper

Yelp Reviews Scraper (arcadium/yelp-reviews) reads input written for web_wanderer/yelp-reviews-scraper: 8 of its 17 input fields work as they are. Field list from its public input schema (build 0.4.37, 2026-10-31); prices and run results from the public Apify API, 2026-11-01.

Their fields that work as they are

Accepted without effect

These fields do not stop the run, but they change nothing here.

Their fields this actor does not read

reviews_translate, domain, search_urls, search_location, search_limit, search_sort, search_price, search_features. Leave them out of the input; the actor’s own options are in the guide.

Side by side: their input, our rows

{
  "biz_urls": [
    "https://www.yelp.com/biz/bor%C3%A9al-coffee-shop-z%C3%BCrich"
  ],
  "reviews_limit": 200,
  "reviews_sort": "oldest",
  "date_from": "2026-01-01",
  "reviews_rating": [
    "1",
    "2"
  ],
  "reviews_language": "de",
  "reviews_keywords": [
    "service"
  ]
}

{
  "reviewId": "Yelp___abc123",
  "platform": "yelp",
  "productName": "Katz's Delicatessen",
  "date": "2026-10-09",
  "text": "Great pastrami, long line, worth it.",
  "ratingOverall": 4,
  "language": "en",
  "helpfulVotes": 2,
  "vendorResponse": "Hi [name], thank you for the kind words.",
  "extras": {
    "reactions": {
      "helpful": 2,
      "thanks": 0,
      "loveThis": 1,
      "ohNo": 0
    },
    "vendorResponseDate": "2026-10-10"
  }
}

Output fields: rowType, platform, productName, productUrl, entityId, reviewId, reviewIdSource, reviewUrl, title, text, pros, cons, ratingOverall, ratings, date, reviewerRole, reviewerIndustry, reviewerCompanySize, reviewerTimeUsed, switchedFrom, alternativesConsidered, reasonForChoosing, reasonForSwitching, adviceToOthers, incentivized, incentive, reviewerVerified, vendorResponse, helpfulVotes, language, country, product, extras, scrapedAt, stated, delivered, skippedSeen, duplicates, stopReason, capSource, shortfall, input, code, message. The rows use these names, not the other actor’s.

Price

Live Apify prices on 2026-11-01, in USD, for each actor’s main charged event. Start fees and platform usage are not included. Units differ: compare what one charged row contains. The Store page of each actor is the current source.

Common issues: failed or timed-out runs

• Yelp Reviews Scraper timed out: 0.0% of 1,439,450 runs timed out.
• Yelp Reviews Scraper failed: 0.1% of 1,439,450 runs ended as failed.

Apify’s public run statistics for each actor, last 30 days to 2026-11-01: FAILED and TIMED-OUT runs as a share of all runs. Shown from 50 runs. A failed run can also come from a bad input. Here an input that cannot be read comes back as a free error row with a code, and the other inputs still arrive.

How to switch

In the Apify Store

1. Open arcadium/yelp-reviews and sign in to Apify.
2. On the Input tab, switch the editor to JSON and paste the input you used for web_wanderer/yelp-reviews-scraper, without the fields listed above as not read.
3. Start the run. Set a maximum cost per run in the run options if you want a hard cap.

Over the API

Change the actor ID in the URL from web_wanderer~yelp-reviews-scraper to arcadium~yelp-reviews; the body stays the same apart from the fields this actor does not read.

curl -X POST "https://api.apify.com/v2/acts/arcadium~yelp-reviews/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"biz_urls":["https://www.yelp.com/biz/bor%C3%A9al-coffee-shop-z%C3%BCrich"],"reviews_limit":200,"reviews_sort":"oldest","date_from":"2026-01-01","reviews_rating":["1","2"],"reviews_language":"de","reviews_keywords":["service"]}'

In n8n

In the Apify node, change the actor to arcadium/yelp-reviews and keep the input JSON. With an HTTP Request node:

{
  "nodes": [
    {
      "name": "Run arcadium/yelp-reviews",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4,
      "position": [
        0,
        0
      ],
      "parameters": {
        "method": "POST",
        "url": "https://api.apify.com/v2/acts/arcadium~yelp-reviews/run-sync-get-dataset-items",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpHeaderAuth",
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "{\"biz_urls\":[\"https://www.yelp.com/biz/bor%C3%A9al-coffee-shop-z%C3%BCrich\"],\"reviews_limit\":200,\"reviews_sort\":\"oldest\",\"date_from\":\"2026-01-01\",\"reviews_rating\":[\"1\",\"2\"],\"reviews_language\":\"de\",\"reviews_keywords\":[\"service\"]}",
        "options": {
          "timeout": 300000
        }
      }
    }
  ],
  "connections": {}
}

From an AI assistant (MCP)

Add the actor as a tool on Apify’s MCP server; an agent can pass the same input fields.

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?tools=arcadium/yelp-reviews",
      "headers": {
        "Authorization": "Bearer <APIFY_TOKEN>"
      }
    }
  }
}

All switching guides