Google Shopping Price Comparison & Deal Finder: MCP config, n8n workflow and API

{
  "mode": "search",
  "queries": [
    "iPhone 15 Pro Max"
  ],
  "countryCode": "us",
  "languageCode": "en",
  "onSale": false,
  "freeShipping": false,
  "maxResultsPerQuery": 1,
  "includePriceHistory": false,
  "includeProductDetails": false
}

---
name: google-shopping-price-comparison-and-deal-finder
description: "Product listings and product-viewer records with real product IDs, viewer URLs, seller offers, shipping and totals, price ranges, specifications and 12-month price history where Google exposes it. Runs the Apify Actor vexaloom-labs/google-shopping-price-comparison-and-deal-finder. Use when the user needs Google Shopping data with fields such as query, position, recordType, title, brand, description 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: "vexaloom-labs/google-shopping-price-comparison-and-deal-finder"
  store-url: "https://apify.com/vexaloom-labs/google-shopping-price-comparison-and-deal-finder"
---

# Google Shopping Price Comparison & Deal Finder

Use this skill to fetch Google Shopping data with the Apify Actor `vexaloom-labs/google-shopping-price-comparison-and-deal-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 `search`, `product`, `deals`, `category` | What to collect: keyword search, product lookup by ID/viewer URL, deals, or a department category. |
| `queries` | array | Product keywords for search/deals mode. Ignored in product mode; optional in category mode. |
| `countryCode` | string | Country used for the Google domain, UULE location and price hint. The actual currency is always detected from the response, never relabelled. |
| `languageCode` | string | Interface and result language (hl parameter). |
| `onSale` | boolean | Ask Google for discounted products and keep rows with an observed original price or discount. |
| `freeShipping` | boolean | Ask Google for free-shipping products and keep rows whose delivery text says free. |
| `maxResultsPerQuery` | integer | Maximum records per query (search/deals/category) or products (product mode). |
| `includePriceHistory` | boolean | Include per-seller daily price history when Google exposes it (product mode and search detail enrichment). |
| `includeProductDetails` | boolean | Fetch the product viewer for each search result to add brand, description, images, specifications and offers. Costs one extra request per result. |

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

```json
{
  "mode": "search",
  "queries": [
    "iPhone 15 Pro Max"
  ],
  "countryCode": "us",
  "languageCode": "en",
  "onSale": false,
  "freeShipping": false,
  "maxResultsPerQuery": 1,
  "includePriceHistory": false,
  "includeProductDetails": false
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/vexaloom-labs~google-shopping-price-comparison-and-deal-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/vexaloom-labs~google-shopping-price-comparison-and-deal-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: `query`, `position`, `recordType`, `title`, `brand`, `description`, `price`, `priceValue`, `originalPrice`, `originalPriceValue`, `discountPercent`, `currency`, `merchant`, `merchantUrl`, `sellerDomain`, `rating`, `reviewCount`, `ratingValue`, `reviewCountValue`, `imageUrl`.

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