Trip.com Hotel Search & Nightly Price Finder: MCP config, n8n workflow and API

{
  "mode": "searchHotels",
  "cityName": "London",
  "adults": 2,
  "rooms": 1,
  "breakfastIncluded": false,
  "freeCancellation": false,
  "payAtHotel": false,
  "sortBy": "recommended",
  "currency": "USD",
  "includeDetails": false,
  "maxItems": 5,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

---
name: trip-com-hotel-search-and-nightly-price-finder
description: "Hotel records with nightly prices, star class, guest scores, location, amenities and booking links. Runs the Apify Actor dataspryva/trip-com-hotel-search-and-nightly-price-finder. Use when the user needs Trip.com data with fields such as name, address, starRating, rating, pricePerNight, currency and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "dataspryva/trip-com-hotel-search-and-nightly-price-finder"
  store-url: "https://apify.com/dataspryva/trip-com-hotel-search-and-nightly-price-finder"
---

# Trip.com Hotel Search & Nightly Price Finder

Use this skill to fetch Trip.com data with the Apify Actor `dataspryva/trip-com-hotel-search-and-nightly-price-finder` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `searchHotels`, `hotelDetail` | Choose 'Search hotels' to browse a city, or 'Hotel details by ID' to fetch specific properties. |
| `cityName` | string | City to search, e.g. London, Paris, Tokyo, Bangkok, Dubai. Country names also work: 'Paris, France'. |
| `checkIn` | string | YYYY-MM-DD. Leave blank for tomorrow. |
| `checkOut` | string | YYYY-MM-DD. Leave blank for the night after check-in. |
| `adults` | integer | Number of adults per room (1-8). |
| `rooms` | integer | Number of rooms (1-5). |
| `breakfastIncluded` | boolean | Only return rooms whose rate includes breakfast. |
| `freeCancellation` | boolean | Only return rooms with a free-cancellation policy. |
| `payAtHotel` | boolean | Only return rooms that can be paid for at the property. |
| `sortBy` | one of `recommended`, `priceLow`, `priceHigh`, `rating`, `stars` | Order of the returned hotels. Price and rating sorts scan extra result slices before trimming. |
| `currency` | string | Currency for all price fields. |
| `includeDetails` | boolean | Fetch each hotel's detail page for its full address, facilities, description, phone and check-in times. Adds one request per hotel. |
| `maxItems` | integer | Maximum records to return (1-200). |
| `proxyConfiguration` | object | Optional. Leave unchanged for a direct connection; the actor uses Apify Proxy automatically if Trip.com blocks the datacenter IP. |

Example `input.json` (the Actor's published prefill):

```json
{
  "mode": "searchHotels",
  "cityName": "London",
  "adults": 2,
  "rooms": 1,
  "breakfastIncluded": false,
  "freeCancellation": false,
  "payAtHotel": false,
  "sortBy": "recommended",
  "currency": "USD",
  "includeDetails": false,
  "maxItems": 5,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~trip-com-hotel-search-and-nightly-price-finder/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/dataspryva~trip-com-hotel-search-and-nightly-price-finder/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `name`, `address`, `starRating`, `rating`, `pricePerNight`, `currency`, `url`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.