Naver Map Business Listings with Menu & Hours Data: MCP config, n8n workflow and API

{
  "mode": "search",
  "searchKeywords": [
    "강남 맛집"
  ],
  "sortBy": "relevance",
  "maxResultsPerKeyword": 20,
  "includeDetails": true,
  "includeReviews": false,
  "maxReviewsPerPlace": 10,
  "openNow": false,
  "hasBooking": false,
  "hasNpay": false,
  "hasCoupon": false,
  "takeout": false,
  "newlyOpened": false,
  "wheelchairAccessible": false,
  "maxItems": 100,
  "monitoringMode": false,
  "emitUnchanged": false
}

---
name: naver-map-business-listings-with-menu-and-hours
description: "Naver Map business records with full menus and prices, weekly hours with breaks and closures, address, phone, amenities, transit, booking, Michelin/TV mentions, and review analysis (plus optional visitor-review records). Runs the Apify Actor dataspryva/naver-map-business-listings-with-menu-and-hours. Use when the user needs Naver data with fields such as name, category, roadAddress, businessHoursStatus, phone, visitorReviewScore 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/naver-map-business-listings-with-menu-and-hours"
  store-url: "https://apify.com/dataspryva/naver-map-business-listings-with-menu-and-hours"
---

# Naver Map Business Listings with Menu & Hours Data

Use this skill to fetch Naver data with the Apify Actor `dataspryva/naver-map-business-listings-with-menu-and-hours` 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`, `byUrls`, required | What to fetch. `search` discovers places by keyword; `byUrls` fetches places you already know (URLs or place IDs). |
| `searchKeywords` | array | Keywords to search on Naver Map, e.g. `강남 맛집` (Gangnam restaurants) or `이태원 카페` (Itaewon cafes). Include a region name for local results. |
| `placeUrls` | array | Naver Map places to fetch directly. Accepts full links (pcmap.place.naver.com, m.place.naver.com, map.naver.com/p/entry/place/...), `naver.me` short links, and bare numeric place IDs. |
| `sortBy` | one of `relevance`, `popular`, `tv`, `reviews`, `saved`, `distance` | How Naver orders search results. `distance` sorting needs Search coordinates. |
| `maxResultsPerKeyword` | integer | Cap on places emitted per keyword (before filters). First page gives up to 100 places; deeper Naver pages add up to ~300 total per map center, and an area sweep multiplies that per center. |
| `includeDetails` | boolean | Fetch each place's detail page for full weekly hours (breaks, last order, upcoming closures), full menus with prices, facilities, parking, photos, review breakdown and more. Slower but much richer data. |
| `includeReviews` | boolean | Emit real visitor reviews per place as separate `recordType: "review"` records (rating, text, dates, keywords, photos, owner replies). |
| `maxReviewsPerPlace` | integer | Cap on review records emitted per place when Include visitor reviews is on. Naver serves 50 reviews per request and does not expose a hard cap, so this can go high (e.g. 500); each 50 reviews costs one extra request. |
| `openNow` | boolean | Only keep places currently marked as open by Naver Map. |
| `hasBooking` | boolean | Only keep places that support online booking/reservations through Naver. |
| `hasNpay` | boolean | Only keep places that accept Naver Pay. |
| `hasCoupon` | boolean | Only keep places with an active coupon or promotion. |
| `takeout` | boolean | Only keep places marked as offering takeout (포장). |
| `newlyOpened` | boolean | Only keep places Naver marks as newly opened. |

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

```json
{
  "mode": "search",
  "searchKeywords": [
    "강남 맛집"
  ],
  "sortBy": "relevance",
  "maxResultsPerKeyword": 20,
  "includeDetails": true,
  "includeReviews": false,
  "maxReviewsPerPlace": 10,
  "openNow": false,
  "hasBooking": false,
  "hasNpay": false,
  "hasCoupon": false,
  "takeout": false,
  "newlyOpened": false,
  "wheelchairAccessible": false,
  "maxItems": 100,
  "monitoringMode": false,
  "emitUnchanged": false
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~naver-map-business-listings-with-menu-and-hours/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~naver-map-business-listings-with-menu-and-hours/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`, `category`, `roadAddress`, `businessHoursStatus`, `phone`, `visitorReviewScore`, `visitorReviewCount`, `placeUrl`.

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