How to Connect Placekey to Excel (4 Methods Compared)

The Problem With Getting Workbook Data In and Out of Placekey

You have an Excel workbook full of location data — store addresses, delivery stops, commercial properties, retail partner sites. You need a Placekey for each one so you can join this list with foot traffic data, a third-party POI dataset, or a routing tool that speaks standard location IDs.

Placekey is good at assigning a universal, stable identifier to any physical address — one that other datasets already use, so joining is a matter of matching keys rather than fuzzing addresses. But getting your address columns through the Placekey API, in bulk, without writing any code, is more friction than it looks. The default path is to export your workbook as a CSV, hand it to whoever on your team knows Python or Postman, wait for them to run the batch call, and import the result back.

Below are the four common ways teams handle this. Only the last one scales.

Method 1: Manual Copy-Paste

The default for Excel users is usually a CSV export rather than direct copy-paste. You export your location sheet, hand it off to the Placekey CSV upload tool or a developer, collect the enriched file, and re-import it into your workbook.

If you have 50 locations, that round trip takes an hour. If you have 500, you are looking at a multi-day cycle every time the list changes — and Placekey IDs are only useful if they're current. The moment you add a new distribution center or a partner site closes, your Placekey column is stale until someone runs the process again.

Method 2: Power Automate

Power Automate can connect to REST APIs and write results back to an Excel workbook in OneDrive or SharePoint. You can set up a flow that triggers on new worksheet rows, calls the Placekey API, and writes the returned ID into a target column.

Quick check — are you comfortable building a Power Automate flow with a custom HTTP action? Do you know how to parse a JSON response body and extract a nested field? Do you know how to handle pagination and rate limits in a sequential loop? If any of those feel like walls, skip to Method 3 or 4.

If you're still reading: the flow is buildable. Authenticate to Placekey's API, map your address fields to the request parameters, parse the response, write back to the worksheet.

But one-row-at-a-time processing is not a bulk operation.

Running 5,000 addresses through a Power Automate loop means 5,000 sequential HTTP calls, a run history that fills up fast, and no native way to batch the requests the way the Placekey API is designed to accept them.

You probably just need a Placekey column added to your workbook. You probably have no idea how to build a custom HTTP action in Power Automate — and there's no reason you should. So this ends up in a ticket queue for your IT admin or whoever owns the company's Power Platform licenses, and you wait.

And once you need to filter which rows get processed — skipping rows where the address is incomplete, or where the country isn't US, or where column E is already populated — you've moved well past what a simple trigger-and-write flow can handle.

Method 3: The Previous Generation — Connector Add-Ons

Until recently, teams without a developer would reach for a category of spreadsheet add-ons that let you configure an API call template, map your columns, and re-run it on demand.

That was a real step forward. You could run a batch call without opening a terminal, the column mappings were saved across sessions, and results wrote directly into the workbook.

But you were still the one designing the template. Every field mapping was yours to specify. Every edge case — missing city, ambiguous address format, international address — required you to update the config. The add-on got the data through, but it only knew what you told it. When your worksheet schema changed, your template was wrong until you fixed it.

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

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 your address columns, understands what you're working with, and through its built-in Placekey integration it can run a bulk lookup and write the results back — without you configuring a single field mapping. You just ask.

Example 1: Bulk-assign Placekeys to a full address list

For every row in this workbook, submit the address in columns A–D to the Placekey bulk API in batches of 100 and write the returned Placekey to column E

The returned Placekey goes into column E, one ID per row. Rows where Placekey returns no match get a blank cell, not a silent skip.

Example 2: Flag duplicates after assigning Placekeys

Bulk-submit all addresses in columns A–D to Placekey in batches of 100 and write the Placekey to column E, then mark any row whose Placekey already appears in a row above as 'DUPLICATE' in column F

The pattern: instead of deduplicating on raw address text — which breaks the moment one location has a trailing comma — you let Placekey resolve the canonical ID first, then flag on that. SheetXAI handles both steps in one pass.

Try It

Get the 7-day free trial of SheetXAI and open any Excel workbook with address columns, then ask it to run a Placekey bulk lookup. The Placekey integration is included in every SheetXAI plan.