How to Connect TomTom to Excel (4 Methods Compared)

The Problem With Getting Sheet Data In and Out of TomTom

You have an Excel workbook 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 workbook 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 Excel workbook and the TomTom API is a workflow problem that nobody has cleanly solved. The default approach is to export the data as 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 export a CSV from Excel, run it through a geocoding tool or TomTom's developer playground, get back a structured response, and re-import or hand-paste those coordinates back into the workbook. If you have 20 rows that's a nuisance. If you have 300 it is genuinely the kind of work that makes people stare at their screen and question their choices.

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 error, requires a level of focus that doesn't hold for long. By row 50, mistakes are happening that won't surface until the mapping tool imports the file and puts points in the wrong city.

Method 2: Power Automate

Power Automate can reach TomTom APIs and write results back to Excel. You set up a trigger, call the API endpoint you need, parse the response, and map each output field into the right column.

A few honest questions before you go further. Do you know what an HTTP connector is? What field mapping means in a Power Automate flow? What a JSON path expression does? What an API key looks like in an Authorization header? If those feel foreign, this is going to be a difficult afternoon with little to show for it. Method 4 was built for you — skip ahead.

If you're still here, the setup is real. You pick the trigger, configure the HTTP action to call the TomTom endpoint, authenticate correctly, and map each output field by hand. Type mismatches between JSON numerics and Excel text cells are common and will bite you during testing.

The flow works. One row at a time.

That's the structural ceiling. Processing 200 GPS coordinates means 200 individual flow runs, 200 API calls, and a run history that's nearly impossible to audit when row 113 returns null and the flow moves on without writing anything.

You probably just need the coordinates in the workbook. You probably have no idea how to build a Power Automate flow with an HTTP connector, and there's no good reason you should have to. So this becomes something you push to whoever on your team handles automations, and now you're waiting on a Slack reply that may or may not come today.

Add conditional logic — route only rows with a specific status, join against a second worksheet — and the flow complexity multiplies before you've finished the first version.

Method 3: The Previous Generation — Connector Add-Ons

Until recently, the best repeatable option was a category of Excel add-ins that let you configure an API connection, map your columns to endpoint parameters, and save that template for reuse. Set up the endpoint, tag your columns, run the import, get results back.

That was a genuine improvement over CSV exports and manual pasting. Configs were reusable. Output was predictable. The team didn't redo field mapping on every run.

But you were still responsible for every design decision: which columns to map, which filter to apply, which fields to pull from the response. The add-in moved the data through; the thinking never left your plate. And when a column got renamed or a new field was added to the response, you went back into the config and fixed it by hand.

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

The Easy Way: Using SheetXAI in Excel

There is a different way entirely. SheetXAI is an AI agent that lives inside your Excel workbook. It reads the workbook, 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 row in my Excel sheet where columns A through D contain street, city, state, and postal code, use TomTom structured geocoding and write the lat/lng into columns E and F

Every row gets processed in one operation. The coordinates land in the right columns, 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 workbook, running a script, and reimporting 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 Excel workbook with location data, then ask it to geocode, route, or enrich those locations using TomTom. The TomTom integration is included in every SheetXAI plan.