Vivino Wine Ratings & Tasting Profile Scraper: MCP config, n8n workflow and API

{
  "mode": "search",
  "searchQueries": [
    "barolo"
  ],
  "wineIds": [
    "171525306"
  ],
  "orderBy": "ratings_count",
  "order": "desc",
  "includeReviews": false,
  "maxReviewsPerWine": 10,
  "maxItems": 2
}

---
name: vivino-wine-ratings-and-tasting-profile-scraper
description: "Vivino wine records with ratings, taste profiles, alcohol, descriptions, critic scores, awards, rankings, prices, merchant offers and optional reviews. Runs the Apify Actor dataspryva/vivino-wine-ratings-and-tasting-profile-scraper. Use when the user needs Vivino data with fields such as name, winery, vintage, country, displayRating, ratingsCount 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/vivino-wine-ratings-and-tasting-profile-scraper"
  store-url: "https://apify.com/dataspryva/vivino-wine-ratings-and-tasting-profile-scraper"
---

# Vivino Wine Ratings & Tasting Profile Scraper

Use this skill to fetch Vivino data with the Apify Actor `dataspryva/vivino-wine-ratings-and-tasting-profile-scraper` 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 `search`, `explore`, `byWineId`, `winery`, required | What to fetch. `search` runs one or more free-text queries; `explore` browses with filters; `byWineId` resolves wine/vintage URLs or IDs; `winery` pages through a producer's catalogue. |
| `searchQueries` | array | One or more free-text wine searches (mode=search). Searches match wine, winery, region and grape names. Example: `barolo`, `chateau petrus`, `napa valley cabernet`. |
| `wineIds` | array | Vivino wine/vintage IDs or URLs (mode=byWineId). Accepts 171525306, https://www.vivino.com/w/1167880?year=2022, /vintages/171525306 and /wines/171525306. |
| `wineType` | one of `1`, `2`, `3`, `4`, `7`, `24` | Filter by wine type. Applies to search, explore and winery. |
| `country` | string | Filter wines by country of origin (ISO 2-letter code). Leave empty for all countries. |
| `orderBy` | one of `ratings_count`, `ratings_average`, `price`, `relevance` | How Vivino orders search and explore results. |
| `order` | one of `desc`, `asc` | Descending (highest first) or ascending (lowest first). |
| `includeReviews` | boolean | Attach the latest wine-level Vivino reviews to each record. Reviews span all vintages; each review keeps its own year. |
| `maxReviewsPerWine` | integer | How many latest reviews to attach when Include reviews is on (1-50). |
| `maxItems` | integer | Maximum wine records to emit. Vivino exposes at most 2,500 rows per search/explore query; split broad queries into narrower filters for more. |

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

```json
{
  "mode": "search",
  "searchQueries": [
    "barolo"
  ],
  "wineIds": [
    "171525306"
  ],
  "orderBy": "ratings_count",
  "order": "desc",
  "includeReviews": false,
  "maxReviewsPerWine": 10,
  "maxItems": 2
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~vivino-wine-ratings-and-tasting-profile-scraper/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~vivino-wine-ratings-and-tasting-profile-scraper/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`, `winery`, `vintage`, `country`, `displayRating`, `ratingsCount`, `price`, `wineUrl`.

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