Connect Google Maps for places and maps

Google Maps Platform provides map and location services. The Google Maps connector in Mythos uses Places API (New) to find places, autocomplete a search, and retrieve details or photo links. An optional second key lets your app display a map in the browser.

Google Maps is an App + chat connector, available in project chat and in your published app through the same saved connection.

Use it for a local directory, store finder, venue guide, or another app that needs place information. Geocoding, directions, route optimization, and other Google Maps APIs are not included in this connector.

Examples to build

App idea	Prompt to try	What it adds
Local directory	“Build a directory that searches nearby cafés with Google Places and displays their opening hours.”	Search for businesses and show the selected place details.
Store finder	“Show our stores on a Google map, using these saved place IDs.”	Put known locations on a map with useful store information.
Venue shortlist	“Build a tool for saving event venues found with Google Places, with photos and addresses.”	Help users compare places in a saved list.
Neighborhood guide	“Create a map of parks and attractions around these neighborhoods using Google Places.”	Organize local places by category and area.
Trip shortlist	“Let visitors find places with autocomplete and save them to a trip shortlist.”	Collect places to visit without promising route or travel-time calculations.

Ask for only the place details the app needs. The fields requested from Google can affect the price of a lookup.

The two keys

The connection can use two different keys:

Places API key: a private key for retrieving place information. It stays out of your app’s browser code.
Browser API key: an optional public key for displaying a map. It is included in your published app, so restrict it to the websites where your app runs.

You only need the browser key if the app displays a map. Keep it separate from the private Places key.

Connect Google Maps to Mythos

Mythos uses keys from your own Google Cloud project. Google bills that project for Maps Platform usage. There is no managed Google Maps allowance included with the connection.

Before you start

You will need a Google Cloud project with billing enabled, permission to enable APIs and create keys, and permission to create an App + chat connection in Mythos. If you will display maps, have the app’s published domain and any custom domains ready for the browser key’s restrictions.

See Google’s Places API setup guide and pricing for current requirements.

1. Enable the APIs

In the Google Cloud console, select your project and open APIs & Services.

Enable Places API (New) for the private key. If the app will show an interactive map, also enable Maps JavaScript API for the browser key. Enable additional browser map APIs only when your app actually uses them.

2. Create the Places key

Open APIs & Services → Credentials.
Choose Create credentials → API key.
Give it a recognizable name, such as Mythos Places.
Under API restrictions, restrict the key to Places API (New).
Keep its application restrictions compatible with server requests. A Websites restriction will reject these requests because they do not come from your app’s browser.
Save and copy the key securely.

Follow Google’s API security guidance for key restrictions and usage monitoring. Do not paste the private key into chat or public code.

3. Create a browser key if you need a map

Create a second API key in the same project. Under Application restrictions, choose Websites and add the exact domains on which your app will run, including custom domains. Under API restrictions, allow the browser map APIs your app uses, such as Maps JavaScript API.

This key is public by design. Its website and API restrictions are essential. Do not reuse the private Places key as the browser key.

4. Save the connection

Open Connectors in Mythos and select Google Maps. If a connection already exists, select Add connection to open a new form.
Enter a Display name, such as Local directory.
Paste the private key into Places API key.
If needed, paste the restricted public key into Browser API key.
Keep Sharing set to Private, or use Share with others or Share with workspace.
Click Connect Google Maps. The setup checks place-ID access; it does not test every field or a browser map.

In your project, open Chat actions (+) → Project connectors, select the connection, and click Use in this project.

Ask Mythos to find one known place and, if you supplied a browser key, display one map. Test the map on its published domain as well as in Preview.

Limitations

Only Places API (New) requests are supported by the connector. Directions, geocoding, weather, and route optimization are not included.
Search results, details, photos, and map loads can incur Google charges. A place-ID-only setup check does not establish that later requests are free.
Linked projects use your keys and Google billing account. App visitors do not connect their own Google accounts through it.

If places or maps do not load

Places requests fail: check billing, that Places API (New) is enabled, and that the private key permits that API. A website restriction on the private key can also cause rejection.

The map fails on one domain: add that exact domain to the browser key’s website restrictions. Check the protocol and subdomain, including www if used.

Google reports a quota error: check the project’s quotas and usage in Google Cloud. Reduce unnecessary repeated searches or request frequency.

Manage the connection

Use Unlink projects or Disconnect from the saved Google Maps connection. To rotate keys, create the replacement keys in Google Cloud, disconnect the old Mythos connection, and create a new connection. Link it to the affected projects and ask Mythos to set up their map features again.

If you replace or remove a browser key, ask Mythos to update the app and publish the change. Previously published browser code can still contain the old public key until you replace that version.