Switching from Tripadvisor Reviews Scraper to Tripadvisor Reviews Scraper
Tripadvisor Reviews Scraper (arcadium/tripadvisor-reviews) reads input written for maxcopell/tripadvisor-reviews: 6 of its 8 input fields work as they are. Field list from its public input schema (build 0.0.237, 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 |
|---|---|---|
startUrls | array | As is |
maxItemsPerQuery | integer | As is |
lastReviewDate | string | As is |
disableMachineTranslations | boolean | As is |
reviewRatings | array | As is |
reviewsLanguages | array | As is |
Their fields this actor does not read
sourceDatasetId, scrapeReviewerInfo. 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 maxcopell/tripadvisor-reviews, pasted unchanged:
{
"startUrls": [
{
"url": "https://www.tripadvisor.com/Hotel_Review-g60763-d208453-Reviews-Hilton_New_York_Times_Square-New_York_City_New_York.html"
}
],
"maxItemsPerQuery": 50,
"lastReviewDate": "2026-01-01",
"disableMachineTranslations": false,
"reviewRatings": [
"5",
"4"
],
"reviewsLanguages": [
"en"
]
}One row from arcadium/tripadvisor-reviews (README example; long text shortened):
{
"reviewId": "Tripadvisor___123456789",
"platform": "tripadvisor",
"productName": "Example Grand Hotel",
"date": "2026-09-27",
"title": "Great stay",
"text": "Quiet room, friendly staff.",
"ratingOverall": 5,
"ratings": {
"value": 5,
"cleanliness": 5
},
"language": "en",
"vendorResponse": "Dear [name], thank you for staying with us.",
"extras": {
"tripType": "COUPLES",
"visitDate": "2026-08",
"placeType": "ACCOMMODATION"
}
}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, 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/tripadvisor-reviews | Pay per event | Review | $4.50 | $0.80 |
| maxcopell/tripadvisor-reviews | Pay per event | Review | $5.00 | $0.30 |
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
- Tripadvisor Reviews Scraper timed out: 0.0% of 559,360 runs timed out.
- Tripadvisor Reviews Scraper failed: 0.3% of 559,360 runs ended as failed.
| Actor | Runs, last 30 days | Failed | Timed out |
|---|---|---|---|
| arcadium/tripadvisor-reviews | under 50 runs (9 runs) | - | - |
| maxcopell/tripadvisor-reviews | 559,360 | 0.3% | 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/tripadvisor-reviews and sign in to Apify.
- On the Input tab, switch the editor to JSON and paste the input you used for maxcopell/tripadvisor-reviews, 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 maxcopell~tripadvisor-reviews to arcadium~tripadvisor-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~tripadvisor-reviews/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"startUrls":[{"url":"https://www.tripadvisor.com/Hotel_Review-g60763-d208453-Reviews-Hilton_New_York_Times_Square-New_York_City_New_York.html"}],"maxItemsPerQuery":50,"lastReviewDate":"2026-01-01","disableMachineTranslations":false,"reviewRatings":["5","4"],"reviewsLanguages":["en"]}'
In n8n
In the Apify node, change the actor to arcadium/tripadvisor-reviews and keep the input JSON. With an HTTP Request node:
{
"nodes": [
{
"name": "Run arcadium/tripadvisor-reviews",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4,
"position": [
0,
0
],
"parameters": {
"method": "POST",
"url": "https://api.apify.com/v2/acts/arcadium~tripadvisor-reviews/run-sync-get-dataset-items",
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"sendBody": true,
"specifyBody": "json",
"jsonBody": "{\"startUrls\":[{\"url\":\"https://www.tripadvisor.com/Hotel_Review-g60763-d208453-Reviews-Hilton_New_York_Times_Square-New_York_City_New_York.html\"}],\"maxItemsPerQuery\":50,\"lastReviewDate\":\"2026-01-01\",\"disableMachineTranslations\":false,\"reviewRatings\":[\"5\",\"4\"],\"reviewsLanguages\":[\"en\"]}",
"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/tripadvisor-reviews",
"headers": {
"Authorization": "Bearer <APIFY_TOKEN>"
}
}
}
}