Switching from Trip.com & Ctrip Reviews Scraper (knagymate/trip-com-reviews-scraper) to Agoda and Trip.com Reviews Scraper
Agoda and Trip.com Reviews Scraper (arcadium/agoda-tripcom-reviews) reads input written for knagymate/trip-com-reviews-scraper: 4 of its 4 input fields work as they are. Field list from its public input schema (build 0.0.31, 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 |
|---|---|---|
hotelUrl | string | As is |
maxReviews | integer | As is |
sortBy | string | As is |
cutoffDate | string | As is |
Side by side: their input, our rows
Input written for knagymate/trip-com-reviews-scraper, pasted unchanged:
{
"hotelUrl": "https://www.trip.com/hotels/shanghai-hotel-detail-346403/grand-hyatt-shanghai/",
"maxReviews": 250,
"sortBy": "mostRelevant",
"cutoffDate": "2026-01-01"
}One row from arcadium/agoda-tripcom-reviews (README example; long text shortened):
{
"platform": "agoda",
"reviewId": "Agoda___1190000001",
"date": "2026-10-08",
"title": "また泊まりたいホテル",
"text": "スタッフの対応がとても良く、部屋も清潔でした。川沿いの景色も最高です。",
"ratingOverall": 5,
"language": "ja",
"country": "TH",
"vendorResponse": "Dear Guest, thank you for staying with us...",
"extras": {
"score10": 10,
"textTranslated": "The staff were very helpful and the room was clean. The river view is great too.",
"travelerType": "Couple",
"roomType": "Superior Room",
"nights": 3,
"checkIn": "2026-10-05"
},
"entityId": "230691",
"productName": "Ibis Bangkok Riverside"
}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/agoda-tripcom-reviews | Pay per event | Agoda review | $5.40 | $2.70 |
| knagymate/trip-com-reviews-scraper | Pay per event | Result | $4.00 | $3.00 |
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
- Trip.com & Ctrip Reviews Scraper timed out: 0.0% of 93,037 runs timed out.
- Trip.com & Ctrip Reviews Scraper failed: 6.4% of 93,037 runs ended as failed.
| Actor | Runs, last 30 days | Failed | Timed out |
|---|---|---|---|
| arcadium/agoda-tripcom-reviews | under 50 runs | - | - |
| knagymate/trip-com-reviews-scraper | 93,037 | 6.4% | 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/agoda-tripcom-reviews and sign in to Apify.
- On the Input tab, switch the editor to JSON and paste the input you used for knagymate/trip-com-reviews-scraper.
- 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 knagymate~trip-com-reviews-scraper to arcadium~agoda-tripcom-reviews; the body stays the same.
curl -X POST "https://api.apify.com/v2/acts/arcadium~agoda-tripcom-reviews/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"hotelUrl":"https://www.trip.com/hotels/shanghai-hotel-detail-346403/grand-hyatt-shanghai/","maxReviews":250,"sortBy":"mostRelevant","cutoffDate":"2026-01-01"}'
In n8n
In the Apify node, change the actor to arcadium/agoda-tripcom-reviews and keep the input JSON. With an HTTP Request node:
{
"nodes": [
{
"name": "Run arcadium/agoda-tripcom-reviews",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4,
"position": [
0,
0
],
"parameters": {
"method": "POST",
"url": "https://api.apify.com/v2/acts/arcadium~agoda-tripcom-reviews/run-sync-get-dataset-items",
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"sendBody": true,
"specifyBody": "json",
"jsonBody": "{\"hotelUrl\":\"https://www.trip.com/hotels/shanghai-hotel-detail-346403/grand-hyatt-shanghai/\",\"maxReviews\":250,\"sortBy\":\"mostRelevant\",\"cutoffDate\":\"2026-01-01\"}",
"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/agoda-tripcom-reviews",
"headers": {
"Authorization": "Bearer <APIFY_TOKEN>"
}
}
}
}