Google Maps Restaurant Menu & Popular Dish Extractor: MCP config, n8n workflow and API

{
  "mode": "byPlace",
  "placeUrls": [
    "https://www.google.com/maps/place/Sicily+Osteria/@40.7601601,-73.9891863,17z/data=!3m1!4b1!4m6!3m5!1s0x89c25932322b79d3:0x7c085aeae6751161!8m2!3d40.7601601!4d-73.9891863"
  ],
  "maxPlacesPerQuery": 1,
  "maxItemsPerPlace": 3,
  "language": "en",
  "includePlacesWithoutMenu": true,
  "includePopularDishes": false
}

---
name: google-maps-restaurant-menu-and-popular-dish
description: "Restaurant menu rows with dish name, section, description, price, currency, photo, menu provenance and full Google Maps place context. Runs the Apify Actor dataspryva/google-maps-restaurant-menu-and-popular-dish. Use when the user needs Google Maps data with fields such as recordType, businessName, placeId, featureId, placeUrl, menuFound 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/google-maps-restaurant-menu-and-popular-dish"
  store-url: "https://apify.com/dataspryva/google-maps-restaurant-menu-and-popular-dish"
---

# Google Maps Restaurant Menu & Popular Dish Extractor

Use this skill to fetch Google Maps data with the Apify Actor `dataspryva/google-maps-restaurant-menu-and-popular-dish` 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 `byPlace`, `bySearch` | How to choose restaurants: paste place URLs/IDs or run a Google Maps search query. |
| `placeUrls` | array | One restaurant per line (mode=byPlace). Accepts Google Maps place URLs, short maps.app.goo.gl links, canonical ChIJ Place IDs, and 0x…:0x… feature IDs. |
| `maxPlacesPerQuery` | integer | Maximum restaurants to process from each search query (mode=bySearch). |
| `maxItemsPerPlace` | integer | Maximum menu rows to return for each restaurant. |
| `language` | string | Language used for Google Maps place lookups and search results. |
| `includePlacesWithoutMenu` | boolean | Return one summary row for a restaurant whose menu cannot be read, so every input place is accounted for. |
| `includePopularDishes` | boolean | Also check Google's own inline menu when it is available and mark dishes Google labels Popular. This uses a browser and is slower. |

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

```json
{
  "mode": "byPlace",
  "placeUrls": [
    "https://www.google.com/maps/place/Sicily+Osteria/@40.7601601,-73.9891863,17z/data=!3m1!4b1!4m6!3m5!1s0x89c25932322b79d3:0x7c085aeae6751161!8m2!3d40.7601601!4d-73.9891863"
  ],
  "maxPlacesPerQuery": 1,
  "maxItemsPerPlace": 3,
  "language": "en",
  "includePlacesWithoutMenu": true,
  "includePopularDishes": false
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~google-maps-restaurant-menu-and-popular-dish/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~google-maps-restaurant-menu-and-popular-dish/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: `recordType`, `businessName`, `placeId`, `featureId`, `placeUrl`, `menuFound`, `menuSource`, `menuProvider`, `menuSurfaceRendered`, `itemCount`, `totalItems`, `itemName`, `menuSection`, `itemDescription`, `priceText`, `price`, `currency`, `isPopular`, `itemImage`, `rank`.

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