Google Maps Business Finder with Hours, Ratings & Location: MCP config, n8n workflow and API

{
  "mode": "search",
  "searchQuery": "coffee shops in New York",
  "maxResults": 3,
  "includeDetails": false,
  "openNow": false,
  "hasWebsite": false,
  "hasPhone": false,
  "includeClosed": true
}

---
name: google-maps-business-finder-with-hours-ratings
description: "Dataset of public Google Maps places with name, address, category, rating, review count, hours, price, attributes, coordinates and place identifiers. Runs the Apify Actor vexaloom-labs/google-maps-business-finder-with-hours-ratings. Use when the user needs Google Maps data with fields such as recordType, searchTerm, rankInSearch, name, categoryName, categories 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-maps-business-finder-with-hours-ratings"
  store-url: "https://apify.com/vexaloom-labs/google-maps-business-finder-with-hours-ratings"
---

# Google Maps Business Finder with Hours, Ratings & Location

Use this skill to fetch Google Maps data with the Apify Actor `vexaloom-labs/google-maps-business-finder-with-hours-ratings` 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`, `placeUrls`, `placeIds` | Search mode uses a text query; placeUrls mode reads specific Maps URLs; placeIds mode resolves canonical ChIJ Place IDs. |
| `searchQuery` | string | What to search for on Google Maps. Include a location for best results, for example 'coffee shops in New York'. Used when mode is search. |
| `maxResults` | integer | Places to collect per search in search mode, or in total in the direct modes. Google returns a ranked window of roughly 160-230 places for a typical query; split broad searches by neighborhood or category for wider coverage. |
| `includeDetails` | boolean | Read the place panel for Plus Code, price range, hotel and fuel details, attributes, photo count and rating histogram. Adds one request per place; the basic listing fields and weekly hours are always included. |
| `searchTerms` | array | Several search terms in one run, for example ["coffee shops", "dentists"]. Each term is searched in every location. |
| `locations` | array | Several locations in one run, for example ["New York, NY", "Austin, TX"]. Each term is searched in each location. |
| `openNow` | boolean | Only keep businesses Google currently shows as open. |
| `hasWebsite` | boolean | Only keep businesses that publish a website on their Google Maps listing. |
| `hasPhone` | boolean | Only keep businesses that publish a phone number on their Google Maps listing. |
| `includeClosed` | boolean | When off, businesses Google marks as permanently closed are skipped. |
| `excludeCategories` | array | Skip businesses whose category contains any of these words, for example ["hotel", "casino"]. |

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

```json
{
  "mode": "search",
  "searchQuery": "coffee shops in New York",
  "maxResults": 3,
  "includeDetails": false,
  "openNow": false,
  "hasWebsite": false,
  "hasPhone": false,
  "includeClosed": true
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/vexaloom-labs~google-maps-business-finder-with-hours-ratings/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-maps-business-finder-with-hours-ratings/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`, `searchTerm`, `rankInSearch`, `name`, `categoryName`, `categories`, `totalScore`, `reviewsCount`, `address`, `phone`, `website`, `priceLevel`, `isOpenNow`, `latitude`, `longitude`, `placeId`, `googleMapsUrl`, `description`, `ratingHistogram`, `priceOfferAmount`.

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