# Google Maps Platform integrations

> Call the Google Maps Platform API from any Tray.ai workflow with the HTTP Connector.

**Canonical page:** https://tray.ai/connectors/google-maps-integrations/
**Categories:** Developer tools
**Connects through:** HTTP Connector

## Overview

Google Maps Platform provides Google's location APIs for geocoding addresses, searching places, calculating routes and travel times, and drawing maps. Tray.ai connects to Google Maps Platform through the HTTP Connector, so your workflows can call the Google Maps Platform API alongside the rest of your stack.

## Use cases

### Geocoding

Work with geocoding in Google Maps Platform from any Tray.ai workflow. The Google Maps Platform API covers calls such as geocode an address and reverse geocode coordinates.

- Geocode an address
- Reverse geocode coordinates

### Places

Read places in Google Maps Platform from any Tray.ai workflow. The Google Maps Platform API covers calls such as search places by text and search nearby places.

- Search places by text
- Search nearby places
- Get place details

### Routes

Work with routes in Google Maps Platform from any Tray.ai workflow. The Google Maps Platform API covers calls such as compute routes and compute a route matrix.

- Compute routes
- Compute a route matrix

## Challenges Tray.ai solves

### Keeping Google Maps Platform credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Google Maps Platform credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Google Maps Platform API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Google Maps Platform API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Google Maps Platform?

Yes. Tray.ai connects to Google Maps Platform through the HTTP Connector, which calls the Google Maps Platform API directly. Any call the Google Maps Platform API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Google Maps Platform?

The Google Maps Platform API uses an API key in the query string and an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Google Maps Platform connector?

Google Maps Platform runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Google Maps Platform connector from the Google Maps Platform API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/