How to Connect GraphHopper to Google Sheets (4 Methods Compared)

The Problem With Getting Sheet Data In and Out of GraphHopper

You have a Google Sheet full of delivery addresses, depot coordinates, or customer locations. GraphHopper can do something genuinely useful with that data — route optimization, drive-time isochrones, geocoding, distance matrices. But getting the data from your sheet into GraphHopper's APIs, and the results back out, requires enough engineering that most people never actually do it.

GraphHopper is purpose-built for spatial computation. But it exposes a developer API, not a spreadsheet plugin. The default path for anyone who isn't a developer is to export the addresses, describe what they need to a backend engineer, wait, and paste the results in by hand.

Below are the four approaches teams use. The first three all require something you probably don't want to spend time on.

Method 1: Manual Copy-Paste

The standard starting point. Export your address list, open the GraphHopper playground or a REST client, run one address at a time, copy the coordinates or distance values out of the JSON response, and paste them back into your sheet.

For a one-off request with five addresses, that takes ten minutes and you're done.

But fleet managers don't have five addresses. They have 80 stops, four times a week. The JSON response for a matrix call contains nested arrays — extracting the right row and column and mapping it back to your specific depot-customer pair is tedious the first time. By the third run you've invented your own color-coded paste ritual. By the tenth you've stopped updating the sheet and the route costs are three weeks stale.

Method 2: Zapier or Make

GraphHopper has API coverage in the major automation platforms. You can set up a trigger on a new sheet row, fire a Routing API call, and write a result back to a column.

Before you get into the setup: do you know what a webhook is? What a JSON path is? What it means to authenticate with a bearer token? If any of those are unfamiliar, this path isn't the right one for you right now. Jump to Method 3 or 4 — you'll get there faster.

If you're still reading, the setup is real. You pick your trigger — a new row, a cell change, a schedule — choose the GraphHopper action, map your address columns to the API fields, and handle the response payload. When it works, it works consistently.

The structural problem is that it fires per row.

A routing matrix for 25 stops is a single API call that returns a 25×25 grid. There's no clean way to model that inside a row-level Zap — you'd need to fire 625 individual calls, each returning one cell of data, and somehow stitch them back together into your sheet.

You probably just need the distance matrix for Tuesday's run. You probably have no idea how to model a matrix API response inside a row-level trigger. So you either spend two days building something fragile, or you ask whoever on your team handles automations — and now you're in a thread waiting for them to find bandwidth between other priorities.

Once the complexity grows — joining across multiple address lists, filtering by region, handling geocoding failures — the cost of maintaining the automation climbs fast.

Method 3: The Previous Generation — Connector Add-Ons

Until recently, the most usable option for repeatable spreadsheet ↔ mapping-API workflows was a category of add-ons that let you pre-configure an API call against a column range. You selected your address column, tagged the output columns, saved the config, and clicked Run.

That was a genuine improvement over copy-paste. The config was reusable, the output was consistent, and anyone on the team could run it without knowing what a REST endpoint was.

But you still had to configure the template yourself, map every field manually, handle authentication, and decide which rows to include or skip. The tool moved the data — the thinking was still entirely on you. And the moment someone added a column, renamed a header, or changed the sheet structure, the saved config broke and sat there silently until someone noticed the data was wrong.

This is the previous generation. It worked, but it asked a lot of the operator.

The Easy Way: Using SheetXAI in Google Sheets

There is a different way entirely. SheetXAI is an AI agent that lives inside your Google Sheet. It reads the sheet, understands the structure of what you're looking at, and through its built-in GraphHopper integration it can call the Routing, Matrix, Geocoding, Isochrone, or Optimization API on your behalf. No config template, no automation glue, no manually parsing JSON responses. You just describe what you need.

Example 1: Build a depot-to-customer distance matrix

Build a driving distance and duration matrix from the depot address in B1 to each customer address in column A and fill the results into columns B and C

SheetXAI reads the depot coordinate from B1, iterates through the addresses in column A, calls the GraphHopper Matrix API, and writes driving distance (km) and travel time (minutes) back into columns B and C — one row per customer.

Example 2: Cluster delivery stops into zones

Cluster the 80 customer locations in this sheet (lat in column B, lon in column C) into 5 groups using GraphHopper and write the assigned cluster number into column D

The pattern: instead of exporting coordinates, running a clustering job separately, and pasting assignments back, you describe both the computation and the destination in one prompt. SheetXAI handles the API call and the writeback inline.

Try It

Get the 7-day free trial of SheetXAI and open any Google Sheet with delivery addresses or store locations, then ask it to geocode, build a matrix, or optimize a route. The GraphHopper integration is included in every SheetXAI plan.