Rent the Runway Designer Rental Catalog Extractor: MCP config, n8n workflow and API

{
  "mode": "category",
  "category": "cocktail-dresses",
  "searchQuery": "floral dress",
  "designer": "any",
  "rentalType": "oneTime",
  "rentalDuration": "4",
  "zipCode": "10001",
  "sortBy": "recommended",
  "includeDetails": true,
  "includeAvailability": true,
  "includeReviews": false,
  "includePriceTiers": false,
  "maxReviewsPerProduct": 200,
  "onlyNew": false,
  "maxItems": 3
}

---
name: rent-the-runway-designer-rental-catalog-extractor
description: "Rent the Runway items with designer, category, rental, retail and member prices, 4/8-day tiers, size availability, rating source, full product details, gallery images and paginated reviews. Runs the Apify Actor dataspryva/rent-the-runway-designer-rental-catalog-extractor. Use when the user needs Rent the Runway data with fields such as itemName, designer, rentalPrice, retailPrice, category, rating 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/rent-the-runway-designer-rental-catalog-extractor"
  store-url: "https://apify.com/dataspryva/rent-the-runway-designer-rental-catalog-extractor"
---

# Rent the Runway Designer Rental Catalog Extractor

Use this skill to fetch Rent the Runway data with the Apify Actor `dataspryva/rent-the-runway-designer-rental-catalog-extractor` 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 `category`, `search`, `designer`, `productUrls`, required | What to fetch. Browse a category, search by keyword and filters, pull one or more designers, or enrich specific product URLs/IDs. |
| `category` | string | Category to browse in mode=category. In mode=search, set it to limit a keyword search to that category. "All categories" browses the full catalog. |
| `searchQuery` | string | Free-text search in mode=search, e.g. "floral dress". Optional: leave blank and use filters to browse. Site-wide search is used when no category is selected. |
| `designer` | string | Filter a category/search run to one designer. Use Custom designer for anyone outside this curated list. |
| `rentalType` | one of `oneTime`, `subscription`, `subscriptionAll` | One-off rental uses a date, duration and shipping zip. Subscription modes use the membership closet; Subscription (include sold out) includes unavailable styles. |
| `rentalDuration` | one of `4`, `8` | Rental length in days. The site supports 4 and 8 days. |
| `zipCode` | string | US ZIP code used for availability and delivery-window pricing. |
| `sortBy` | one of `recommended`, `newest`, `msrpLowToHigh`, `msrpHighToLow`, `priceLowToHigh`, `priceHighToLow`, `ratingHighToLow`, `relevance` | Order of results. Price sorts by retail (MSRP) value are server-side; rental-price and rating sorts use the fetched candidate window. |
| `includeDetails` | boolean | Fetch descriptions, fabric, fit notes, attributes, sizes and images from each product page. |
| `includeAvailability` | boolean | Check which sizes are actually available for the selected date/scope instead of listing every size the item was made in. |
| `includeReviews` | boolean | Add up to 40 recent reviews per item, including fit feedback and reviewer measurements when available. |
| `includePriceTiers` | boolean | Add both rental price tiers for one-off rentals. Uses one extra request per item. |
| `maxReviewsPerProduct` | integer | Upper bound when Include reviews is on. The actor fetches review pages until this bound or exhaustion. Default 200; max 1000. |
| `onlyNew` | boolean | Emit only product IDs not seen in a previous run with onlyNew enabled. Uses a persistent key-value store; useful for scheduled price/stock monitors. |

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

```json
{
  "mode": "category",
  "category": "cocktail-dresses",
  "searchQuery": "floral dress",
  "designer": "any",
  "rentalType": "oneTime",
  "rentalDuration": "4",
  "zipCode": "10001",
  "sortBy": "recommended",
  "includeDetails": true,
  "includeAvailability": true,
  "includeReviews": false,
  "includePriceTiers": false,
  "maxReviewsPerProduct": 200,
  "onlyNew": false,
  "maxItems": 3
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~rent-the-runway-designer-rental-catalog-extractor/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~rent-the-runway-designer-rental-catalog-extractor/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: `itemName`, `designer`, `rentalPrice`, `retailPrice`, `category`, `rating`, `sizesAvailable`, `inStock`, `detailUrl`.

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