Integrate Google Maps to access location data, geocoding, directions, and mapping services in your application.
Integrate Google Maps to access location data, geocoding, directions, and mapping services in your application. On Nagent, Google Maps is exposed as a fully-configurable developer tools integration that any agent can call — 22 actions, and OAUTH2, API_KEY authentication. No code is required to wire Google Maps into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Google Maps to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Google Maps into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Google Maps, with input parameters and output schema. Drop these into any step of an agent built in Helix.
GOOGLE_MAPS_AUTOCOMPLETEReturns 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.
Input parameters
Text string to search for place predictions. Can be full words, substrings, place names, addresses, or plus codes. Must be non-empty.
Latitude/longitude point for distance calculations.
Region code in ccTLD format for formatting responses (e.g., 'us', 'br').
Zero-based Unicode character offset of cursor position in the input string.
Preferred language for results using IETF BCP-47 language codes (e.g., 'en-US', 'es-ES').
Area to bias search results toward.
User-generated string grouping calls into sessions for billing purposes.
Up to 15 two-character country codes (ISO 3166-1 Alpha-2) to restrict results. Query predictions unavailable when this is set.
Area to restrict search results within.
Restricts results to up to five specified primary types (e.g., 'restaurant', 'cafe').
Includes query predictions in response for text searches (default: false).
Includes businesses without physical locations (default: false).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_COMPUTE_ROUTE_MATRIXCalculates 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.
Input parameters
Unit system (e.g., 'METRIC' for kilometers, 'IMPERIAL' for miles) for displaying distances. Note: distanceMeters in responses is always in meters regardless of this setting; units affects only human-readable text output.
List of origin locations. Each can be specified as an address or latitude/longitude coordinates.
Comma-separated list of response fields to include (e.g., 'originIndex,destinationIndex,duration,distanceMeters'). Use '*' for all fields.
Mode of transportation for the route matrix calculation.
List of destination locations. Each can be specified as an address or latitude/longitude coordinates.
BCP-47 language code (e.g., 'en-US', 'es') for textual information.
Specifies factors to consider when calculating the route.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_DISTANCE_MATRIX_APIDEPRECATED: 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.
Input parameters
Your application's API key. This key identifies your application for purposes of quota management.
Specifies the mode of transport to use.
Indicates that the calculated route should avoid the specified features. Multiple values can be pipe-separated e.g. 'tolls\\ | highways'.
Specifies the unit system to use when displaying results. The default is metric.
The region code, specified as a ccTLD ('top-level domain') two-character value. This helps influence results based on the region.
The starting point for calculating travel distance and time. You can supply one or more locations separated by the pipe character (\\|), in the form of a place ID (prefixed with place_id:), an address, latitude/longitude coordinates (e.g., '40.7128,-74.0060'), a plus code, or an encoded polyline (prefixed with enc: and a colon).
The language in which to return results. See the list of supported languages: https://developers.google.com/maps/faq#languagesupport
Specifies the desired time of arrival for transit directions, in seconds since midnight, January 1, 1970 UTC. You can specify either departure_time or arrival_time, but not both.
One or more locations to use as the finishing point for calculating travel distance and time. Accepts the same formats as origins.
Specifies one or more preferred modes of transit. This parameter may only be specified for transit directions. Multiple values can be pipe-separated e.g. 'bus\\ | train'.
Specifies the assumptions to use when calculating time in traffic. This parameter is only used if the request includes a departure_time and mode is 'driving'.
Specifies the desired time of departure. You can specify the time as an integer in seconds since midnight, January 1, 1970 UTC, or as the string 'now'. Required for duration_in_traffic.
Specifies preferences for transit routes. This parameter may only be specified for transit directions.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_GEOCODE_ADDRESSDEPRECATED: 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.
Input parameters
Your application's API key. This parameter is required when using API key authentication. If not provided, will attempt to use OAuth authentication (requires X-Goog-User-Project header with project ID).
Bounding box of the viewport within which to bias geocode results more prominently. Format: southwest_lat,southwest_lng\\ | northeast_lat,northeast_lng. This parameter will only influence, not fully restrict, results from the geocoder.
Region code specified as a ccTLD (country code top-level domain) two-character value. This parameter will only influence, not fully restrict, results from the geocoder.
The street address that you want to geocode, in the format used by the national postal service of the country concerned. Additional address elements such as business names and unit, suite or floor numbers should be avoided. Street address elements should be delimited by spaces (shown here as url-escaped to %20). If both address and components are provided, address takes precedence.
Language in which to return results. If not supplied, the geocoder attempts to use the preferred language as specified in the Accept-Language header, or the native language of the domain from which the request is sent.
Component filters separated by a pipe (\\|). Each component filter consists of component:value pair and fully restricts results from the geocoder. Examples: components=country:US or components=postal_code:94043\\ | country:US. If both address and components are provided, address takes precedence.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_GEOCODE_ADDRESS_WITH_QUERYTool 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.
Input parameters
Region code, specified as a ccTLD two-character value (e.g., 'US', 'FR'). This parameter affects results based on applicable law.
The unstructured address to geocode. This should be a single string containing the full address (e.g., '1600 Amphitheatre Parkway Mountain View CA'). Include city, state/region, and country where possible — incomplete or ambiguous strings may return zero results or incorrect matches.
Language in which the results should be returned (e.g., 'en', 'es', 'fr').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_GEOCODE_DESTINATIONSTool 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.
Input parameters
Resource name in format 'places/{placeId}' to retrieve destination by Place ID
Two-character ccTLD region code for formatting/filtering (e.g., 'US', 'UK')
Filter navigation points by travel mode. Supported values: DRIVE, WALK
Address query in unstructured or structured format
Preferred language code for results (e.g., 'en', 'es', 'fr')
Location query using geographic coordinates
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_GEOCODE_LOCATIONTool 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.
Input parameters
Set of type tags to restrict results; results without specified types are removed
Latitude coordinate in degrees, range \[-90.0, +90.0\]
Longitude coordinate in degrees, range \[-180.0, +180.0\]
Region code specified as a ccTLD two-character value, affecting results based on applicable law
Language code in which the results should be returned (BCP-47 format)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_GEOCODE_PLACETool 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.
Input parameters
Place identifier to geocode. Must be in the format 'places/{placeId}' or just the place ID (e.g., 'ChIJj61dQgK6j4AR4GeTYWZsKWw'). The unique identifier for a place in the Google Places database.
Region code specified as a ccTLD two-character value, affecting results based on applicable law and address formatting.
Language code in which the results should be returned (BCP-47 format). Defaults to 'en' if not specified.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_GEOCODING_APIConvert 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.
Input parameters
Your application's API key. If not provided, will be extracted from connection metadata.
The bounding box of the viewport within which to bias geocode results more prominently (e.g., '34.172684,-118.604794\\|34.236144,-118.500938'). This parameter will only influence, not fully restrict, results.
The latitude and longitude coordinates specifying the location for which you want the closest, human-readable address (e.g., '40.714224,-73.961452'). Provide for reverse geocoding.
The region code, specified as a ccTLD ('top-level domain') two-character value. This parameter will only influence, not fully restrict, results from the geocoder.
The street address or plus code that you want to geocode. Provide for geocoding (address to coordinates).
The language in which to return results. If language is not supplied, the geocoder attempts to use the preferred language as specified in the Accept-Language header, or the native language of the domain from which the request is sent.
The place ID of the place for which you wish to obtain the human-readable address. Provide for place ID geocoding.
A components filter with elements separated by a pipe (\\|). E.g., 'postal_code:94043\\ | country:US'. Used for geocoding, can be restrictive or biasing. Supplying only `components` without `address` may return ZERO_RESULTS for some queries.
A filter of one or more address types, separated by a pipe (\\|) (e.g., 'street_address\\|locality'). Used for reverse geocoding and place ID geocoding.
A filter of one or more location types, separated by a pipe (\\|) (e.g., 'ROOFTOP\\|RANGE_INTERPOLATED'). Used for reverse geocoding and place ID geocoding.
Use this parameter to specify additional features in the response. Can select multiple values.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_GEOLOCATETool 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.
Input parameters
Carrier name.
Radio type. Defaults to 'gsm'.
Array of cell tower objects.
Whether to fall back to IP geolocation if WiFi and cell tower signals are missing. Defaults to true.
Array of WiFi access point objects (minimum 2 required for success).
Mobile country code for device's home network. Range: 0-999.
MNC for GSM/WCDMA/LTE/NR (0-999); SID for CDMA (0-32767).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_GET2D_TILETool 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.
Input parameters
Tile column coordinate. Valid range: \[0, (2^zoom)-1\].
Tile row coordinate. Valid range: \[0, (2^(zoom-1))-1\]. Valid range: \[0, (2^zoom)-1\], same as `x`.
Zoom level ranging from 0 (entire world) to 22 (highly detailed).
Google API key for authentication. If not provided, will be extracted from connection metadata. Required if not using Bearer token authentication.
Session token UUID obtained from /v1/createSession endpoint. Valid for approximately two weeks. Required for all 2D tile requests. Reuse across multiple tile requests; each createSession call consumes quota.
Rotation parameter in degrees counter-clockwise. Valid values: 0, 90, 180, or 270.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_GET3D_TILES_ROOTTool 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.
Input parameters
Your Google Maps API key with Map Tiles API enabled. If not provided, will be extracted from connection metadata.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_GET_DIRECTIONFetches 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.
Input parameters
The mode of transportation for which to calculate directions.
Specifies features to avoid in the generated route. Multiple values can be combined using a pipe delimiter (e.g., 'tolls\\|highways'). Valid options include 'tolls', 'highways', and 'ferries'.
The unit system for displaying distances. Defaults to 'imperial'.
The starting point for the directions. This can be a textual address (e.g., '123 Main St, Los Angeles, CA'), a place name (e.g., 'Disneyland'), or latitude/longitude coordinates (e.g., '34.0522,-118.2437').
The language code for returning results, e.g., 'en' for English, 'es' for Spanish. Defaults to 'en'.
A pipe-separated (\\|) string of intermediate locations (addresses, place names, or coordinates) to visit between the origin and destination. For example: 'Anaheim, CA\\ | Long Beach, CA' or 'Hollywood Bowl\\ | Getty Center'.
The ending point for the directions. This can be a textual address (e.g., '456 Park Ave, New York, NY'), a place name (e.g., 'Universal Studios Hollywood'), or latitude/longitude coordinates (e.g., '40.7128,-74.0060').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_GET_PLACE_DETAILSRetrieves comprehensive details for a place using its resource name (places/{place_id} format). Use when you need detailed information about a specific place.
Input parameters
Google Place ID ONLY - an alphanumeric code (NOT a business name, address, or search query). Accepts 'places/{place_id}' or just the place_id. Place IDs typically start with 'ChIJ' followed by alphanumeric characters. To find a place ID from a business name, first use TEXT_SEARCH or NEARBY_SEARCH.
Comma-separated list of place fields to return (no spaces allowed). Use '*' for all fields (not recommended for performance/cost). Common fields: id, displayName, formattedAddress, location, types, rating, photos, reviews, regularOpeningHours, nationalPhoneNumber, internationalPhoneNumber, websiteUri, googleMapsUri. Note: 'emailAddress' and 'phoneNumber' are NOT valid fields - use 'nationalPhoneNumber' or 'internationalPhoneNumber' instead.
Unicode country/region code (CLDR format) for region-specific display names. Examples: 'US', 'GB', 'FR', 'JP'. This affects how place names and addresses are formatted.
Preferred language code for place details (BCP-47 format). Examples: 'en' (English), 'es' (Spanish), 'fr' (French), 'ja' (Japanese). If not specified, defaults to the language of the request location.
URL-safe base64 string (max 36 characters) for Autocomplete session billing. Used to group this request with previous Autocomplete requests for billing purposes.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_GET_ROUTECalculates 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.
Input parameters
Unit system (e.g., 'METRIC' for kilometers, 'IMPERIAL' for miles) for displaying distances. Note: `routes.distanceMeters` in the response is always in meters regardless of this setting; `units` only affects human-readable distance formatting in other fields.
Comma-separated list of `Route` object fields to include in the response (e.g., 'routes.distanceMeters,routes.duration'). If not specified, a default fieldMask is used based on travelMode: for TRANSIT mode, transit-specific fields (transitDetails, steps, etc.) are included; for other modes, basic route fields (distanceMeters, duration, polyline) are included. Fields not listed are absent from the response; explicitly include all needed fields such as `routes.legs.steps` and `routes.polyline.encodedPolyline`.
Mode of transportation for the route.
BCP-47 language code (e.g., 'en-US', 'es') for textual information like navigation instructions.
Starting point for the route calculation. Can be an address (e.g., '1600 Amphitheatre Parkway, Mountain View, CA') or coordinates as 'latitude,longitude' (e.g., '48.8566,2.3522').
Specifies routing preference: `TRAFFIC_UNAWARE` (fastest, ignores traffic), `TRAFFIC_AWARE` (considers traffic, optimized), `TRAFFIC_AWARE_OPTIMAL` (most accurate traffic-based routing), or `ROUTING_PREFERENCE_UNSPECIFIED` (behavior similar to `TRAFFIC_UNAWARE`). Cannot be set when travelMode is WALK, BICYCLE, or TRANSIT - must be omitted for these modes.
Destination point for the route calculation. Can be an address (e.g., '85 10th Ave, New York, NY') or coordinates as 'latitude,longitude' (e.g., '40.7484,-73.9967').
Computes and returns alternative routes if true.
Attempts to avoid toll roads if true.
Attempts to avoid ferries if true.
Attempts to avoid highways if true.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_LOOKUP_AERIAL_VIDEOTool 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.
Input parameters
A US postal address. Either videoId or address must be provided, but not both.
An ID returned from videos.renderVideo. Either videoId or address must be provided, but not both.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_MAPS_EMBED_APITool 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.
Input parameters
The mode of the embedded map.
Google Maps API key. Required if not provided via connection metadata. The Maps Embed API only supports API key authentication, not OAuth.
Parameters for 'view' mode.
Parameters for 'place' mode.
Parameters for 'search' mode.
Parameters for 'directions' mode.
Parameters for 'streetview' mode.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_NEARBY_SEARCHSearches 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.
Input parameters
Radius of the circular search area in meters.
Latitude coordinate of the search center in decimal degrees.
Comma-separated list of place fields for the response. Fields are automatically prefixed with 'places.' if missing. Common fields: displayName, formattedAddress, id, types, rating, userRatingCount, location, businessStatus, regularOpeningHours, photos, reviews. Use '*' for all fields (not recommended for production). Valid field names include: displayName, formattedAddress, shortFormattedAddress, id, types, primaryType, primaryTypeDisplayName, location, viewport, plusCode, rating, userRatingCount, reviews, regularOpeningHours, currentOpeningHours, photos, websiteUri, googleMapsUri, businessStatus, priceLevel, priceRange, addressComponents, utcOffsetMinutes, internationalPhoneNumber, nationalPhoneNumber, editorialSummary, accessibilityOptions, parkingOptions, paymentOptions, delivery, dineIn, takeout, reservable, servesBreakfast, servesLunch, servesDinner, servesBeer, servesWine, allowsDogs, outdoorSeating, liveMusic, goodForChildren, goodForGroups.
Longitude coordinate of the search center in decimal degrees.
List of place types to exclude from Table A. Results matching any of these types are omitted. Up to 50 types allowed. Must be provided as a list, e.g., \['cafe'\] for a single type or \['cafe', 'store'\] for multiple types. Must use valid Table A types only.
List of place types to include from Table A. Results will match at least one of these types. Up to 50 types allowed. Must be provided as a list, e.g., \['restaurant'\] for a single type or \['atm', 'bank'\] for multiple types. Common types: restaurant, cafe, bank, atm, hospital, pharmacy, school, park, gym, hotel, airport, gas_station. IMPORTANT: 'food' is NOT a valid type (it's in Table B); use specific types like restaurant, cafe, bakery, fast_food_restaurant instead. Note: 'locality' is valid, but 'city', 'town', 'sublocality', 'landmark', and 'point_of_interest' are NOT valid for filtering.
Maximum number of search results to return. Valid range: 1-20. The actual count may be lower based on available places.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_PLACE_PHOTORetrieves 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.
Input parameters
Maximum desired width of the image in pixels (1-1600). Image will be scaled proportionally. You must specify either maxwidth, maxheight, or both.
Maximum desired height of the image in pixels (1-1600). Image will be scaled proportionally. You must specify either maxwidth, maxheight, or both.
A string identifier that uniquely identifies a photo. Can be either: (1) A full photo resource name in format 'places/{place_id}/photos/{photo}' from the new Places API, or (2) Just the photo reference string from legacy API. Obtained from Place Details, Nearby Search, or Text Search requests. Note: Photo references cannot be cached and may expire over time.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_RENDER_AERIAL_VIDEOStarts 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.
Input parameters
US postal address for which to render aerial video. Must be a valid US address with street, city, state, and postal code.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_TEXT_SEARCHSearches 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.
Input parameters
Comma-separated list of place fields to return. Common fields include: displayName, formattedAddress, types, rating, userRatingCount, priceLevel, websiteUri, nationalPhoneNumber, internationalPhoneNumber, regularOpeningHours, location, photos, googleMapsUri, businessStatus, id. The 'places.' prefix is optional and will be added automatically. Use '*' for all fields (not recommended for performance/cost). Common aliases are supported: 'name'->displayName, 'address'->formattedAddress, 'url'/'website'->websiteUri, 'type'->types, 'phone'->nationalPhoneNumber. Invalid field names (e.g., places.phoneNumber instead of places.nationalPhoneNumber) cause errors. Many fields (rating, websiteUri, regularOpeningHours, nationalPhoneNumber) may be absent even when requested — handle nulls.
Text query for searching places. Matched against place name, address, and category. Underspecified queries (missing city, region, or business type) yield empty or irrelevant results. Brand-name-only queries return multiple franchise branches — validate formattedAddress against the intended location.
Maximum number of place results to return (must be 1-20). Note: Google prefers `pageSize`, but this action uses `maxResultCount`.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLE_MAPS_TILES_CREATE_SESSIONTool 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.
Input parameters
Label scaling factor for high-resolution displays. Valid values: 'scaleFactor1x' (standard), 'scaleFactor2x' (2x resolution), or 'scaleFactor4x' (4x resolution).
Two-letter CLDR region code representing the user's location (e.g., 'US', 'GB', 'FR'). This helps Google Maps provide region-specific content.
JSON style objects for customizing map appearance (roadmap only). Allows custom styling of map features like roads, buildings, and landmarks.
Enable high-resolution tiles for high DPI displays. Works only with 2x or 4x scale factors. Set to true for sharper images on high-resolution screens.
Base map type. Valid values: 'roadmap' for standard road map, 'satellite' for satellite imagery, 'terrain' for terrain maps, or 'streetview' for street view imagery.
Render map layers separately (true) or combined into a single image (false). Set to true if you want individual overlay layers.
IETF language tag specifying the display language for map labels and information (e.g., 'en-US', 'es-ES', 'fr-FR').
Overlay options for the map. Valid values: 'layerRoadmap' (road overlay), 'layerStreetview' (street view overlay), 'layerTraffic' (traffic layer). Note: terrain mapType requires layerRoadmap.
Output format for tile images. Valid values: 'jpeg' or 'png'. If omitted, the format will be auto-selected by the API.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 63 agents privately built on Nagent that already use Google Maps.
Build on Nagent
Connect Google Maps to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Google Maps, and click "Connect Now." You'll authenticate with OAUTH2, API_KEY — Nagent handles credential storage and refresh automatically. Once connected, Google Maps is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Google Maps is connected, you configure its 22 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Google Maps steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Google Maps event fires, the agent kicks off automatically.
Every Google Maps action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Google Maps ships with 22 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Google Maps together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Google Maps-based workflows tailored to your business.