Google Maps Make integrationAutomate Google Maps with Make.
Can Make turn a plain address into coordinates, a route or a map without code? The Google Maps Make integration gives you 9 modules: 5 actions and 4 searches. This page shows how to link your API key, then walks you through a first scenario you can test right away.
Verified Trustpilot reviews · AI, automation & growth agency
What can you automate with the Google Maps Make integration?
The Google Maps Make integration lets a Make scenario (the automation you build, a chain of modules) ask Google Maps for location data and pass the answer to your other apps. You get coordinates, routes, travel times, places and map images inside your workflow, with no code to write.
Clean up addresses as they come in. A delivery team collects addresses from an order form. Get a Location turns each one into coordinates, and Get a Timezone tells dispatch which local time applies before anyone calls the customer.
Compare travel options for field staff. A service company with several technicians can feed their bases and the day's job sites into Get a Distance Matrix, then read the travel time for each pair to pick who goes where. Get Directions then returns the route for the chosen technician.
Build a list of local businesses. A sales rep can run Search For Places on a type of business, and send each result to a spreadsheet or a CRM. Add Get a Static Map Image to attach a map picture to a report or an email.
Google Maps in Make has no trigger: nothing in Google Maps starts a scenario on its own. The scenario starts from another app or from Make's schedule, and Google Maps answers questions along the way. Anything the listed modules skip can go through Make an API Call. Apps like this one often have an n8n node as well; the n8n vs Make comparison lays out the criteria, and the Make training helps if you build your first scenarios alone. Our Make pricing page explains how operations are counted.
How do you connect Google Maps to Make?
- 01
Get an API key in Google Cloud
Log in to the Google Cloud Platform and create a project. In APIs & Services > Library, open each Google Maps API you need and click Enable. Then go to APIs & Services > Credentials, click + Create Credentials > API key and copy the key somewhere safe.
- 02
Add a Google Maps module in Make
In your scenario, add any Google Maps module and click Create a Connection. A connection is your Google Maps access linked to Make once and reused by every Google Maps module. You can give it a name in Connection name if you plan to use several keys.
- 03
Paste the key and save
Paste the key you copied into the API Key field and click Save. If Google asks you to sign in and confirm access, do it. The module is now ready, and Make can use the key for every call your scenario makes.
Your first scenario with Google Maps and Make
GoalWhen a new address lands in the app where you store customers, Make finds its coordinates in Google Maps, then its time zone.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the +. The first module comes from the app that holds your addresses, such as a sheet or a CRM, since Google Maps has no trigger.
- 02
Add Get a Location
Click the + on the right of that first module, search for Google Maps and pick Get a Location. Create the connection with your API key, then map the address field from the previous module.
- 03
Chain Get a Timezone
Click the + again and add Get a Timezone. Map the coordinates that Get a Location returned. Each bundle, meaning one item passed from module to module, now carries its address, its position and its time zone.
- 04
Test with Run once
Click Run once to execute the scenario a single time. Then read the bundles each module received and check that the coordinates match the address you expected.
- 05
Schedule and switch it on
Set the schedule on the first module with the clock icon. A new scenario checks every 15 minutes by default. Switch the scenario on, and each run spends operations, one per module per bundle, on your Make plan.
What each Google Maps module does in Make
Google Maps gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Get a Location
ActionIn Make“Gets the details of a location by either input address or geocodes.”
You get the full details of a place from a written address, or the reverse, from coordinates you already have. It is the usual first Google Maps step, because Get an Elevation and Get a Timezone work from coordinates, not from text.
Get an Elevation
ActionIn Make“Provides elevation data for all locations on the surface of the earth, including depth locations on the ocean floor by input geographic coordinates”
Hand it geographic coordinates and it tells you how high that point sits, anywhere on the planet, including spots below sea level on the ocean floor. Pair it with Get a Location when your source data only holds addresses.
Get a Static Map Image
ActionIn Make“Returns an static image (PNG or JPG) of Google Map.”
This module produces a picture of a Google map, as a PNG or JPG file, that the next module can store or send. The image is a regular file in the scenario, so a storage app or an email module can pick it up directly.
Get a Timezone
ActionIn Make“Gets the details of a timezone by geographical coordinates.”
Give it coordinates and it returns the time zone details for that spot, which saves guessing from a country or a city name. It usually follows Get a Location in the same scenario.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
When none of the listed modules covers what you need, this one lets you call any endpoint of the Google Maps API from your scenario, with the same connection and the same key. You write the request yourself, so keep the Google Maps API documentation open.
Get a Distance Matrix
SearchIn Make“Provides travel distance and time for a matrix of origins and destinations.”
Feed it a list of starting points and a list of destinations, and you get the travel distance and time for every pairing in one go. That grid is what you need to compare options, rather than one route at a time.
Get Directions
SearchIn Make“Returns the most efficient routes when calculating directions.”
This search returns the most efficient routes between an origin and a destination, ready to be passed on to the rest of your scenario. Know both ends of the trip? Use this one. For comparing many pairs at once, the Distance Matrix fits better.
Get Roads
SearchIn Make“Identifies the roads a vehicle was traveling along and provides additional metadata about those roads, such as speed limits.”
From a trail of positions, it works out which roads a vehicle actually drove on and adds details about those roads, such as speed limits. Result: a readable road log.
Search For Places
SearchIn Make“Searches for place information using a variety of categories, including establishments, prominent points of interest, and geographic locations.”
Look up businesses, landmarks or geographic locations by category and get their details back as bundles your scenario can store. Each place becomes its own bundle, ready to become a row in a sheet or a record in a CRM.
Need help automating Google Maps with Make?
A person reads every message.
