Switching from TrustRadius Review Scraper to TrustRadius Reviews Scraper
TrustRadius Reviews Scraper (arcadium/trustradius-reviews) reads input written for zen-studio/trustradius-review-scraper: 5 of its 6 input fields work as they are. Field list from its public input schema (build 0.2.25, 2026-10-31); prices and run results from the public Apify API, 2026-10-31.
Their fields that work as they are
| Their field | Type | Note |
|---|---|---|
productUrl | string | As is |
maxResults | integer | As is |
sort | string | relevant falls back to newest first. |
starRating | array | As is |
companySize | array | The site filters one size group at a time; the first one in the list is used. |
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
Input written for zen-studio/trustradius-review-scraper, pasted unchanged:
{
"productUrl": "https://www.trustradius.com/products/zendesk-support-suite/reviews",
"maxResults": 250,
"sort": "critical",
"starRating": [
"5",
"4"
],
"companySize": [
"large"
]
}One row from arcadium/trustradius-reviews (README example; long text shortened):
{
"reviewId": "TrustRadius___638fcc80649f691b7696d9c6",
"platform": "trustradius",
"productName": "Asana",
"date": "2022-12-15",
"title": "Great task management tool",
"text": "Asana is used to manage all the internal activities at my company...",
"pros": "Receive requests\nDocument information\nManage tasks across departments",
"cons": "More free/not-premium features\nSmall navigation bugs\nTask templates",
"ratingOverall": 5,
"ratings": {
"likelihoodToRecommend": 10
},
"reviewerRole": null,
"reviewerCompanySize": null,
"reviewerTimeUsed": null,
"incentive": "TrustRadius",
"incentivized": true,
"extras": {
"jobType": "Manager",
"department": "Marketing",
"ratingRaw10": 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
| Actor | Pricing model | Charged per | Per 1,000, Free plan | Per 1,000, lowest plan |
|---|---|---|---|---|
| arcadium/trustradius-reviews | Pay per event | Review | $3.59 | $2.24 |
| zen-studio/trustradius-review-scraper | Pay per event | Review | $3.99 | $2.49 |
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
- TrustRadius Review Scraper failed: 10.6% of 1,490 runs ended as failed.
| Actor | Runs, last 30 days | Failed | Timed out |
|---|---|---|---|
| arcadium/trustradius-reviews | under 50 runs (8 runs) | - | - |
| zen-studio/trustradius-review-scraper | 1,490 | 10.6% | 0.0% |
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
- Open arcadium/trustradius-reviews and sign in to Apify.
- On the Input tab, switch the editor to JSON and paste the input you used for zen-studio/trustradius-review-scraper, without the fields listed above as not read.
- 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~trustradius-review-scraper to arcadium~trustradius-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~trustradius-reviews/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"productUrl":"https://www.trustradius.com/products/zendesk-support-suite/reviews","maxResults":250,"sort":"critical","starRating":["5","4"],"companySize":["large"]}'
In n8n
In the Apify node, change the actor to arcadium/trustradius-reviews and keep the input JSON. With an HTTP Request node:
{
"nodes": [
{
"name": "Run arcadium/trustradius-reviews",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4,
"position": [
0,
0
],
"parameters": {
"method": "POST",
"url": "https://api.apify.com/v2/acts/arcadium~trustradius-reviews/run-sync-get-dataset-items",
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"sendBody": true,
"specifyBody": "json",
"jsonBody": "{\"productUrl\":\"https://www.trustradius.com/products/zendesk-support-suite/reviews\",\"maxResults\":250,\"sort\":\"critical\",\"starRating\":[\"5\",\"4\"],\"companySize\":[\"large\"]}",
"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/trustradius-reviews",
"headers": {
"Authorization": "Bearer <APIFY_TOKEN>"
}
}
}
}