FlowRunner
PricingContact
Theme
Start Free

Google Maps

Utilities & Personal

Give AI agents the Google Maps Platform. Agents geocode and validate addresses, search and autocomplete places, pull place details and photos, compute routes and distance matrices, look up elevation and time zones, and generate static map images.

14 actions API key available
A new order arrives with a customer-typed shipping address
Validate Address standardizes it and returns a verdict with per-component confirmation levels
Addresses the verdict marks complete flow on; inferred or replaced components get flagged
Geocode Address attaches coordinates to the order record for routing and territory logic
Compute Route Matrix finds the nearest fulfillment location and the delivery ETA
An operations coordinator reviews the flagged addresses, where the API had to guess, and confirms or corrects each before the label prints
The order system gets the standardized address, coordinates, and assigned location written back

What This Integration Enables

Address and location data is where operational reality enters your systems, and it enters dirty: typed by customers, abbreviated by reps, copied across tools. This connector puts the full Google Maps Platform behind FlowRunner agents so location data gets cleaned, enriched, and computed on at intake instead of discovered broken at shipping time. Geocoding in all three directions, Places search and details, route and matrix computation, address validation with optional USPS CASS, elevation, time zones, and rendered map imagery saved to FlowRunner file storage. - Standardize and validate addresses before they reach labels, invoices, or field crews - Turn addresses into coordinates and coordinates into addresses for enrichment - Resolve partial place names into place IDs, then pull phone, website, hours, and ratings - Compute routes, ETAs, and up to 625-element distance matrices for assignment decisions - Attach time zone and elevation context to any coordinate - Render labeled static maps and place photos into reports and notifications Each Maps Platform product bills per request against your own key, which makes call volume a real cost surface. FlowRunner workflows batch deliberately, and the [human-in-the-loop](/concepts/human-in-the-loop) step lands where the API's confidence runs out.

Without FlowRunner

Addresses are stored as typed Whatever the customer entered ships as entered, and the carrier's surcharge or return is the error report
Distance logic is a guess Nearest store, service territory, and drive-time decisions run on straight-line math or gut feel
Location context lives in someone's head Which time zone a site is in, what is near it, whether the address even exists, all tribal knowledge

With FlowRunner

Every address is validated before it matters Standardization with component-level confidence runs at intake, and only the uncertain cases reach a person
Routes and matrices are computed facts ETAs, distances, and origin-destination grids come from the Routes API, traffic-aware when requested
Coordinates enrich every record Geocodes, time zones, place details, and map images attach to CRM and order data automatically

Use Case Scenarios

Shipping addresses that survive contact with carriers

Every new order from the storefront runs through Validate Address with USPS CASS processing for US destinations. Complete verdicts pass straight to fulfillment; addresses with inferred or replaced components queue for a coordinator with the original and standardized versions side by side. Corrections write back to the order and the customer record in [HubSpot](/integrations/hubspot), so the fix happens once, not per order.

Territory assignment by drive time, not straight lines

When a service request comes in, the agent geocodes the site, runs Compute Route Matrix against every technician's start location, and assigns by actual drive duration rather than radius. Get Time Zone stamps the site's local timezone so scheduling and notifications land in the customer's morning, not the dispatcher's. The assignment posts to [Slack](/integrations/slack) with a Generate Static Map image showing the site and route.

Lead enrichment from a business name

Sales drops a business name into the intake form. Autocomplete Places resolves it to a place ID, Get Place Details pulls the phone number, website, address, and hours, and Get Place Photo stores an image of the location. The enriched record lands in the CRM and a row in [Google Sheets](/integrations/google-sheets) logs what was found. A rep starts the first call knowing the business is real, open, and reachable.

Human-in-Loop Highlight

Validate Address returns a verdict that admits uncertainty: components can come back inferred or replaced, meaning the API changed what the customer wrote to make the address parse. Shipping against a replaced component is a small bet placed with real goods, and across thousands of orders the losing bets are silent until the returns arrive. So the workflow honors the confidence signal. Complete, confirmed addresses flow through untouched; any verdict where the API guessed routes to a coordinator who sees the customer's original next to the standardized result and picks. There is a second, quieter gate on cost: every action here bills per request against your key, so an agent proposing a 625-element Compute Route Matrix sweep across the whole customer base states the request count first and waits for a yes.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

14 actions

Geocoding

3
  • Geocode Address Converts a street address or place name into coordinates and structured address data: latitude and longitude, formatted address, components, place ID, and location precision. Supports component filters to restrict matches.
  • Reverse Geocode Converts coordinates into human-readable addresses, ordered most to least specific, each with components and a place ID. Optionally filtered by result type or precision.
  • Geocode by Place ID Retrieves the full geocoding result for a known place ID. The bridge from Places search or Autocomplete to a structured postal address.

Places

5
  • Search Places by Text Searches places with a free-text query via Places API Text Search, up to 20 per page and 60 across pages, with type, open-now, rating, and price filters plus a location bias.
  • Search Nearby Places Finds places within a circular area around a coordinate, filtered by included or excluded types and ranked by popularity or distance.
  • Get Place Details Retrieves detailed information for a place by ID, with the field mask selecting contact data, opening hours, ratings, reviews, photos, and price level.
  • Autocomplete Places Returns up to five place and query predictions for partial text input, restrictable by place type and country. The resolver from user-typed names to place IDs.
  • Get Place Photo Downloads a place photo by its photo resource name and saves it to FlowRunner file storage, returning the stored file URL. Scaled to fit requested dimensions.

Routes

2
  • Compute Route Calculates a route between origin and destination with optional intermediate stops, returning duration, distance, and an encoded polyline, extendable to turn-by-turn steps, tolls, and traffic-aware durations. Waypoints accept addresses, coordinate pairs, or place IDs.
  • Compute Route Matrix Calculates duration and distance for every origin-destination combination, up to 625 elements per request, returning one element per pair with indexes, duration, distance, and route condition.

Address Validation

1
  • Validate Address Validates and standardizes a postal address, returning a verdict with inferred and replaced components, per-component confirmation levels, and a geocode. Optional USPS CASS processing for US and Puerto Rico adds delivery-point validation. The action this page's human gate is built around.

Geo Data

2
  • Get Elevation Returns elevation above sea level in meters for one or more coordinates, with a resolution value indicating sample accuracy.
  • Get Time Zone Returns the IANA time zone ID, localized name, UTC offset, and daylight-saving offset in effect for a coordinate at a given time.

Static Maps

1
  • Generate Static Map Renders a PNG map image with center and zoom framing, roadmap, satellite, terrain, or hybrid types, markers, and path overlays, saved to FlowRunner file storage. Auto-frames to fit markers or a path when no center is given.

Frequently Asked Questions

What can FlowRunner do with Google Maps?

FlowRunner agents can run Geocode Address, Reverse Geocode, and Geocode by Place ID in Google Maps, plus 11 more actions.

Does connecting Google Maps to FlowRunner require OAuth?

No. Google Maps connects to FlowRunner with an API key, no OAuth flow required.

Can Google Maps trigger a FlowRunner workflow automatically?

Google Maps doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Google Maps

$100 in credits. No card required. Connect in minutes.