Bing Maps Local Business Finder: MCP config, n8n workflow and API

{
  "mode": "search",
  "searchQueries": [
    "coffee shops"
  ],
  "locations": [
    "London"
  ],
  "radius": 1000,
  "maxItems": 3,
  "market": "en-US",
  "minRating": "0",
  "openNow": false,
  "includeDetails": false,
  "maxReviews": 0,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

---
name: bing-maps-local-business-finder
description: "Bing Maps local businesses with contact details, category, coordinates, rating, weekly hours, description, amenities, reviews and photos. Runs the Apify Actor dataspryva/bing-maps-local-business-finder. Use when the user needs Bing Maps data with fields such as name, category, address, phone, rating, reviewCount 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/bing-maps-local-business-finder"
  store-url: "https://apify.com/dataspryva/bing-maps-local-business-finder"
---

# Bing Maps Local Business Finder

Use this skill to fetch Bing Maps data with the Apify Actor `dataspryva/bing-maps-local-business-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`, `nearbySearch`, `placeDetails` | Choose how to find businesses: by keyword and place, around a point, or by exact place IDs/links. |
| `searchQueries` | array | One or more business searches, e.g. 'coffee shops', 'dentist', 'hotel'. Each query is combined with every location. |
| `locations` | array | Cities, areas or full addresses to search in, e.g. 'London', 'Manhattan, New York', 'Paris, France'. |
| `radius` | integer | How far around the centre point to search, in metres. |
| `maxItems` | integer | Maximum number of businesses to save across all queries and locations. |
| `market` | string | Bing market (language and region) used for results, addresses and hours. |
| `minRating` | one of `0`, `2`, `3`, `4`, `4.5` | Only keep businesses at or above this rating. Businesses with no rating are left out when a minimum is set. |
| `openNow` | boolean | Keep only businesses Bing marks as open at the time of the run. |
| `includeDetails` | boolean | Fetch each place's detail panel for weekly hours, description, amenities, reviews, rating breakdown, photos, menu and booking links. Slower because it adds one request per business. |
| `maxReviews` | integer | How many recent reviews to include when detail fields are enabled. Set 0 for none. |
| `proxyConfiguration` | object | Optional proxy. Apify Proxy AUTO is enabled by default to reduce the chance of rate limiting on large runs. |

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

```json
{
  "mode": "search",
  "searchQueries": [
    "coffee shops"
  ],
  "locations": [
    "London"
  ],
  "radius": 1000,
  "maxItems": 3,
  "market": "en-US",
  "minRating": "0",
  "openNow": false,
  "includeDetails": false,
  "maxReviews": 0,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~bing-maps-local-business-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/dataspryva~bing-maps-local-business-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: `name`, `category`, `address`, `phone`, `rating`, `reviewCount`, `website`, `openStatus`, `url`, `description`, `hours`, `attributes`, `reviews`, `photos`.

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