Appearance
Google Maps
Access geocoding, directions, places, and distance data via Google Maps APIs.
| Detail | Value |
|---|---|
| Category | Productivity |
| Base URL | https://maps.googleapis.com/maps/api |
| Authentication | API Key (Query) |
| Endpoints | 5 |
| Connector key | google-maps |
Using Google Maps in a workflow
- Go to Connections and click New Connection.
- Pick Google Maps from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /geocode/json | Geocode an address |
GET /directions/json | Get directions |
GET /place/nearbysearch/json | Search nearby places |
GET /place/details/json | Get place details |
GET /distancematrix/json | Get distance matrix |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /geocode/json
Geocode an address
| Detail | Value |
|---|---|
| Operation ID | productivity.geocode |
| Method | GET |
| Path | /geocode/json |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
address | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google Maps connection from the Connection dropdown.
- In the Operation dropdown, select
productivity.geocode. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Maps API reference.
GET /directions/json
Get directions
| Detail | Value |
|---|---|
| Operation ID | productivity.getDirections |
| Method | GET |
| Path | /directions/json |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
origin | query | string | Yes |
destination | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google Maps connection from the Connection dropdown.
- In the Operation dropdown, select
productivity.getDirections. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Maps API reference.
GET /place/nearbysearch/json
Search nearby places
| Detail | Value |
|---|---|
| Operation ID | productivity.nearbySearch |
| Method | GET |
| Path | /place/nearbysearch/json |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
location | query | string | Yes |
radius | query | integer | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google Maps connection from the Connection dropdown.
- In the Operation dropdown, select
productivity.nearbySearch. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Maps API reference.
GET /place/details/json
Get place details
| Detail | Value |
|---|---|
| Operation ID | productivity.placeDetails |
| Method | GET |
| Path | /place/details/json |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
place_id | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google Maps connection from the Connection dropdown.
- In the Operation dropdown, select
productivity.placeDetails. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Maps API reference.
GET /distancematrix/json
Get distance matrix
| Detail | Value |
|---|---|
| Operation ID | productivity.distanceMatrix |
| Method | GET |
| Path | /distancematrix/json |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
origins | query | string | Yes |
destinations | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Google Maps connection from the Connection dropdown.
- In the Operation dropdown, select
productivity.distanceMatrix. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Maps API reference.