Google Maps Timezone & Local Time Lookup: one-request API, MCP and n8n

{
  "mode": "coordinates",
  "location": {
    "lat": 40.7128,
    "lng": -74.006
  },
  "language": "en"
}

---
name: google-maps-timezone-and-local-time-lookup
description: "One record per resolved place, address, Place ID or coordinate, with the IANA timezone, current local and UTC time, UTC offset, daylight-saving detail and the matched Google Maps place. Runs the Apify Actor dataspryva/google-maps-timezone-and-local-time-lookup. Use when the user needs Google Maps data with fields such as recordType, mode, inputAddress, inputLocation, placeName, formattedAddress 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-timezone-and-local-time-lookup"
  store-url: "https://apify.com/dataspryva/google-maps-timezone-and-local-time-lookup"
---

# Google Maps Timezone & Local Time Lookup

Use this skill to fetch Google Maps data with the Apify Actor `dataspryva/google-maps-timezone-and-local-time-lookup` 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 `coordinates`, `place`, `placeId`, `mixed` | Coordinates resolves latitude/longitude pairs. Place looks up an address, landmark or business name. Place ID resolves a Google Place ID or Maps URL. Mixed processes every filled list in one run. |
| `location` | object | One coordinate as {"lat": 40.7128, "lng": -74.006}. Decimal degrees, WGS84. |
| `language` | string | Language Google Maps uses for returned place names, addresses and country names. It does not translate the query itself. |

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

```json
{
  "mode": "coordinates",
  "location": {
    "lat": 40.7128,
    "lng": -74.006
  },
  "language": "en"
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~google-maps-timezone-and-local-time-lookup/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-timezone-and-local-time-lookup/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`, `placeName`, `formattedAddress`, `timezone`, `timezoneAbbreviation`, `utcOffset`, `currentLocalTime`, `currentUtcTime`, `dayOfWeek`, `isDaylightSavingTime`, `googleMapsUrl`, `scrapedAt`, `resolved`, `inputPlaceId`, `location`, `placeId`, `featureId`.

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