Google Maps

22 tools available

Integrate Google Maps to access location data, geocoding, directions, and mapping services in your application.

Connect Google Maps to Definable to triage issues, review pull requests, monitor builds. Personas call Google Maps's 22 tools directly from chat or scheduled flows. Wire it into a triage, review, or release-management persona — every action runs scoped, reviewable, and logged.

Common workflows with Google Maps

Triage incoming issues

Webhook fires on every new issue
Persona summarises and labels it
Assigns the right engineer

Auto-review PRs

Pull the diff
Run a code-review persona
Post structured feedback as PR comment

Failing-build alerts

CI sends a failure event
Agent inspects logs and stack trace
Drops a debug summary in Slack

Release notes from commits

Read commits since last tag
Group by type with the model
Post to a changelog channel

Google Maps actions 22

Every Google Maps action below is a callable tool any Definable persona can invoke.

Autocomplete Place Predictions

Returns place and query predictions for text input. Use when implementing as-you-type autocomplete functionality for place searches. Returns up to five predictions ordered by relevance.

Compute Route Matrix

Calculates travel distance and duration matrix between multiple origins and destinations using the modern Routes API; supports OAuth2 authentication and various travel modes. Matrix is capped at 625 elements (e.g., 25×25); chunk larger sets to avoid RESOURCE_EXHAUSTED errors. Response elements may be returned out of input order — always use originIndex and destinationIndex to map results. Only use elements where condition='ROUTE_EXISTS'; the matrix may be incomplete.

Distance Matrix (Legacy)

DEPRECATED: Legacy API that calculates travel distance and time for a matrix of origins and destinations. This API only works with API keys (no OAuth2 support). Use the modern 'Compute Route Matrix' action instead, which supports OAuth2 authentication. Supports different modes of transportation and options like departure/arrival times. Capped at 100 elements per request (elements = origins × destinations count); split large sets into batches.

Geocode Address

DEPRECATED: Legacy API to convert street addresses into geographic coordinates (latitude and longitude). This API works best with API key authentication. For OAuth connections without an API key, you may need to provide the 'key' parameter or use the newer 'Text Search' action instead. Use when you need to geocode an address or location to get its precise latitude/longitude coordinates.

Geocode Address With Query

Tool to map addresses to geographic coordinates with query parameter. Use when you need to convert a textual address into latitude/longitude coordinates using the modern v4beta API. Results may match multiple places — always verify `formattedAddress`, `region`, and `addressComponents` in the response before using returned coordinates.

Geocode Destinations

Tool to perform destination lookup and return detailed destination information including primary place, containing places, sub-destinations, landmarks, entrances, and navigation points. Use when you need comprehensive destination data for an address, place ID, or geographic coordinates.

Reverse Geocode Location

Tool to convert geographic coordinates (latitude and longitude) to human-readable addresses using reverse geocoding. Use when you need to find the address or place name for a given set of coordinates. A single coordinate pair may return multiple results; verify formattedAddress, region, and addressComponents before committing to a result.

Geocode Place by ID

Tool to perform geocode lookup using a place identifier to retrieve address and coordinates. Use when you need to get detailed geographic information for a specific Google Place ID.

Geocoding API

Convert addresses into geographic coordinates (latitude and longitude) and vice versa (reverse geocoding), or get an address for a Place ID. Uses the Geocoding API v4 (v4beta) which supports OAuth2 authentication. Exactly one of `address`, `latlng`, or `place_id` must be provided per request; omitting all three or mixing incompatible combinations yields no useful results.

Geolocate Device

Tool to determine location based on cell towers and WiFi access points. Use when you need to find the geographic location of a device using network infrastructure data.

Get 2D Map Tile

Tool to retrieve a 2D map tile image at specified coordinates for building custom map visualizations. Use when you need to download individual map tile images for roadmap, satellite, or terrain views. Requires a valid session token from the createSession endpoint.

Get 3D Tiles Root

Tool to retrieve the 3D Tiles tileset root configuration for photorealistic 3D map rendering. Use when you need to initialize a 3D renderer with Google's photorealistic tiles following the OGC 3D Tiles specification. The Map Tiles API is billable per request; cache the root response client-side and avoid repeated calls.

Get Directions

Fetches detailed directions between an origin and a destination, supporting intermediate waypoints and various travel modes. Automatically uses the modern Routes API with OAuth2 when available, falling back to legacy API with API key if provided.

Get Place Details

Retrieves comprehensive details for a place using its resource name (places/{place_id} format). Use when you need detailed information about a specific place.

Get Route

Calculates one or more routes between two specified locations. Uses various travel modes and preferences; addresses must be resolvable by Google Maps. Response `duration` is a string with 's' suffix (e.g., `"4557s"`); parse before displaying.

Lookup Aerial Video

Tool to look up an aerial view video by address or video ID. Returns video metadata including state and URIs for playback. Use when you need to retrieve a previously rendered aerial video or check the status of a video render request. Note that receiving a video is a billable event.

Embed Google Map

Tool to generate an embeddable Google Map URL and HTML iframe code. Use when you need to display a map (place, view, directions, street view, search) on a webpage without JavaScript. Note: This API only works with API keys (no OAuth2 support). It generates embed URLs and does not make direct API calls. Generated embed URLs are publicly accessible; avoid passing sensitive or internal location queries.

Nearby search

Searches for places (e.g., restaurants, parks) within a specified circular area, with options to filter by place types and customize the returned fields and number of results.

Get Place Photo

Retrieves high quality photographic content from the Google Maps Places database. Use when you need to download a place photo using a photo_reference obtained from Place Details, Nearby Search, or Text Search requests. Images are scaled proportionally to fit within specified dimensions.

Render Aerial Video

Starts rendering an aerial view video for a US postal address. Returns a video ID that can be used with lookupVideo to retrieve the video once rendering completes. Rendering typically takes up to a few hours.

Text Search

Searches for places on Google Maps using a textual query (e.g., "restaurants in London", "Eiffel Tower"). Results may include CLOSED_PERMANENTLY or TEMPORARILY_CLOSED places — filter by businessStatus=OPERATIONAL. Include city/region and business type in textQuery to avoid empty or irrelevant results. Deduplicate using id or formattedAddress, not name alone. Throttle to ~1 req/s; OVER_QUERY_LIMIT (HTTP 429) requires exponential backoff.

Create Tiles Session

Tool to create a session token required for accessing 2D Tiles and Street View imagery. Use when you need to initialize tile-based map rendering or street view display. The session token is valid for approximately two weeks and must be included in all subsequent tile requests. Each call consumes quota — cache and reuse the returned token across all tile requests within its validity window rather than creating a new session per request.

Frequently asked questions

What can I automate with Google Maps on Definable?

Anything Google Maps exposes through its API. Common developer tools workflows on Definable include triage issues, review pull requests, monitor builds. Personas can call any of the 22 Google Maps tools directly, then chain the result into another integration without you writing code.

How does Google Maps authentication work?

Google Maps uses OAUTH2, API_KEY on Definable. You connect once from the integrations page, scoped to the permissions you choose, and from then on any persona that has the integration enabled can act on your behalf. Tokens are encrypted at rest and rotated automatically.

Is the Google Maps integration included in my Definable plan?

Yes — every Definable plan, including Starter, includes access to all 22 Google Maps tools. You only need a separate Google Maps subscription if Google Maps itself charges per seat or per API call.

Is using Google Maps through Definable secure?

Every call from a persona to Google Maps is logged with the user, persona, prompt, and response. Tokens never leave Definable's secrets vault, scopes are configurable per persona, and you can revoke access at any time from the integration page.

How do I get started with Google Maps on Definable?

Sign up for Definable, open the integrations page, find Google Maps, and connect via OAuth or API key. You can immediately attach Google Maps to any persona and start running workflows. The free Starter plan includes 5,000 credits/month.

What Google Maps actions does Definable expose?

Definable exposes all 22 Google Maps actions as callable tools — including `Autocomplete Place Predictions`, `Compute Route Matrix`, `Distance Matrix (Legacy)`, plus 19 more. Each tool gets a typed parameter schema so personas know exactly how to call it.

Ready to automate with Google Maps?

Wire it up in minutes. No coding required.

Start for free Schedule a demo

← All integrations