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

The Problem With Getting Sheet Data In and Out of TomTom

You have a Google Sheet full of data — depot addresses, customer stops, GPS coordinates from a fleet tracker, candidate site locations. You need those locations geocoded, routed, or enriched with TomTom traffic and POI data, and the results written back into the sheet where the rest of your analysis lives.

TomTom is good at the hard geographic work: geocoding, routing, matrix calculations, live traffic, point-of-interest search. But the gap between your spreadsheet and the TomTom API is a workflow problem that nobody has cleanly solved. The default approach is to export a CSV, write a script or use a tool to call the API, wrangle the JSON response, and then manually paste the results back into the right columns.

Below are the four ways teams handle this. Only the last one doesn't require a second job.

Method 1: Manual Copy-Paste

You copy a block of addresses from the sheet, paste them into a geocoding tool or TomTom's developer playground, get back a blob of coordinates, and hand-paste those back into the right cells. One by one. If you have 20 rows it's annoying. If you have 300 it's the kind of task that makes people leave their desks for a very long coffee.

The particular grind with TomTom data is that the outputs are structured — latitude, longitude, confidence score, formatted address — and landing them into the right columns, for the right rows, without a single transposition, requires the kind of attention that degrades fast. By row 50 you're making mistakes you won't catch until the GIS tool imports the file and the points land in the ocean.

Method 2: Zapier or Make

Both platforms have TomTom connector options. You can set up a trigger on a new sheet row, call the TomTom geocoding or routing API, and write the result back into a specified column. It works.

Before you invest time here, a few honest questions. Do you know what a REST API connector is? What field mapping means? What an authentication token is? What a JSON path expression does? If any of those terms feel unfamiliar, this path will burn an afternoon getting you nowhere. Skip to Method 3 or 4 — they were built for you.

If you're still here, you've done this before. The setup is real: you pick the right trigger, authenticate to TomTom's developer portal, map each output field by hand, handle type mismatches between the API's numeric response and the sheet's text cells, and test the whole chain on live data.

The automation runs. Row by row.

But a row-per-trigger architecture is not what you need when you're processing 200 GPS coordinates. Two hundred rows means two hundred API calls, two hundred trigger events, and a task log that becomes genuinely difficult to audit when row 87 returns an empty response and the automation silently moves on.

You probably just need the coordinates written into the sheet. You probably have no idea how to wire a TomTom REST connector in Make, and you shouldn't have to. So this becomes a ticket you send to whoever on your team builds automations, and now you're waiting on Slack for them to finish it between everything else they have going.

And once you need to join location data across two tabs, or filter which rows get routed based on a status column, the automation logic multiplies fast.

Method 3: The Previous Generation — Connector Add-Ons

Until recently, the best repeatable option was a category of spreadsheet add-ons that let you configure an API connection, map your columns to the right parameters, and save that config for reuse. You set up the endpoint, tagged your origin and destination columns, ran the import, and got results back.

That was a real step forward from copy-paste. The config was reusable. Output was consistent. The team didn't have to redo the field mapping every run.

But the config was yours to build and yours to maintain. Every column rename broke something. Every new field you wanted to pull required going back into the mapping interface. The add-on moved the data; every decision about which data, filtered how, formatted to what spec, was still on you. The tool got the bytes through — the thinking stayed behind your keyboard.

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 what you're looking at, and through its built-in TomTom integration it can geocode, route, enrich, and write results back — for you. No API configuration. No column mapping. No automation glue. You just ask.

Example 1: Bulk geocode a column of addresses

For each address in column A, geocode it using TomTom and write the returned latitude, longitude, match confidence score, and formatted address into columns B, C, D, and E

Every row gets processed in one operation. The results land in the right columns, labeled, ready for the next step.

Example 2: Calculate driving times for mileage reimbursement

For each row in this sheet where column A is a rep's home address and column B is a client address, calculate the TomTom driving route and write the total distance in km and travel time in minutes into columns C and D

The pattern: instead of exporting the sheet, running a script, and re-importing the enriched file, you ask for what you need inline. SheetXAI handles the API calls and the writebacks in one pass.

Try It

Get the 7-day free trial of SheetXAI and open any Google Sheet with location data, then ask it to geocode, route, or enrich those locations using TomTom. The TomTom integration is included in every SheetXAI plan.