Google Maps Address & Coordinate Geocoding Lookup: MCP config, n8n workflow and API

{
  "mode": "forward",
  "addresses": [
    "1600 Amphitheatre Parkway, Mountain View, CA"
  ],
  "language": "en"
}

---
name: google-maps-address-and-coordinate-geocoding
description: "One row per resolved input: coordinates, formatted address, structured address parts, Place ID, Plus Code, time zone and result level. Runs the Apify Actor vexaloom-labs/google-maps-address-and-coordinate-geocoding. Use when the user needs Google Maps data with fields such as recordType, mode, inputAddress, inputLocation, inputPlaceId, resolved 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-address-and-coordinate-geocoding"
  store-url: "https://apify.com/vexaloom-labs/google-maps-address-and-coordinate-geocoding"
---

# Google Maps Address & Coordinate Geocoding Lookup

Use this skill to fetch Google Maps data with the Apify Actor `vexaloom-labs/google-maps-address-and-coordinate-geocoding` 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 `forward`, `reverse`, `placeId`, `mixed` | Forward turns an address, place name or postal code into coordinates. Reverse turns a coordinate pair into the nearest address. Place ID resolves a Google Place ID or Maps URL. Mixed processes every list in one run. |
| `addresses` | array | One address, place name or postal code per line. Add a country bias for ambiguous postal codes. A lat,lng line is treated as reverse geocoding. |
| `language` | string | Language of the returned names, formatted address and country names. Google Maps translates the result; it does not translate the input. |

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

```json
{
  "mode": "forward",
  "addresses": [
    "1600 Amphitheatre Parkway, Mountain View, CA"
  ],
  "language": "en"
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/vexaloom-labs~google-maps-address-and-coordinate-geocoding/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-address-and-coordinate-geocoding/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`, `mode`, `inputAddress`, `inputLocation`, `inputPlaceId`, `resolved`, `name`, `formattedAddress`, `location`, `placeId`, `featureId`, `plusCode`, `addressComponents`, `categoryName`, `timezone`, `countryCode`, `resultLevel`, `distanceMeters`, `googleMapsUrl`, `sourceUrl`.

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