Switching from All-in-One Review Scraper to Software Reviews Scraper

Software Reviews Scraper (arcadium/software-reviews) reads input written for zen-studio/software-review-scraper: 4 of its 6 input fields work as they are. Field list from its public input schema (build 0.0.118, 2026-10-31); prices and run results from the public Apify API, 2026-10-31.

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

feedback. Leave them out of the input; the actor’s own options are in the guide.

Side by side: their input, our rows

{
  "query": "Slack",
  "platforms": [
    "capterra"
  ],
  "maxResults": 200,
  "sort": "most_helpful"
}

{
  "rowType": "review",
  "platform": "googleplay",
  "reviewId": "GooglePlay___a1b2c3d4-0000-0000-0000-000000000000",
  "productName": "Slack",
  "date": "2026-10-14",
  "title": null,
  "text": "Notifications are finally reliable on my phone.",
  "ratingOverall": 4,
  "reviewerCompanySize": null,
  "extras": {
    "inputProduct": "Slack"
  }
}

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, inputType, vendor, matchConfidence, sources. The rows use these names, not the other actor’s.

Price

Live Apify prices on 2026-10-31, 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

• All-in-One Review Scraper timed out: 0.1% of 2,403 runs timed out.
• All-in-One Review Scraper failed: 7.9% of 2,403 runs ended as failed.

Apify’s public run statistics for each actor, last 30 days to 2026-10-31: 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/software-reviews and sign in to Apify.
2. On the Input tab, switch the editor to JSON and paste the input you used for zen-studio/software-review-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 zen-studio~software-review-scraper to arcadium~software-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~software-reviews/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"query":"Slack","platforms":["capterra"],"maxResults":200,"sort":"most_helpful"}'

In n8n

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

{
  "nodes": [
    {
      "name": "Run arcadium/software-reviews",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4,
      "position": [
        0,
        0
      ],
      "parameters": {
        "method": "POST",
        "url": "https://api.apify.com/v2/acts/arcadium~software-reviews/run-sync-get-dataset-items",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpHeaderAuth",
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "{\"query\":\"Slack\",\"platforms\":[\"capterra\"],\"maxResults\":200,\"sort\":\"most_helpful\"}",
        "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/software-reviews",
      "headers": {
        "Authorization": "Bearer <APIFY_TOKEN>"
      }
    }
  }
}

All switching guides