How to Connect ipdata.co to Excel (4 Methods Compared)

The Problem With Getting Workbook Data In and Out of ipdata.co

You have an Excel workbook full of IP addresses — session logs, login events, form submissions, or network monitoring exports. You need each one enriched with geolocation, ASN details, or threat intelligence from ipdata.co. The data is already in the workbook. The problem is getting it to the API and back without writing a macro or exporting a CSV every time.

ipdata.co is good at returning structured geolocation, company, and security metadata for any IP, with a bulk endpoint that handles up to 100 at a time. But moving a workbook column of IPs through that API and writing the results into the right cells is still an afternoon of work by default. The usual route is a CSV export, a script or a separate tool, a fresh import, and then a manual reconciliation of which rows matched.

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

Method 1: CSV Export and Re-Import

The Excel default. Export the IP column to CSV, run it through a script or the API manually, get a result CSV back, and import it. Then match the rows back to the original workbook by row number or a key column.

For a single ad-hoc enrichment this is tolerable. But the moment the workbook changes — new rows added, rows reordered, a filter applied — the re-import lands in the wrong cells. You spend as much time reconciling as you saved on the API call.

Do it every week and you will find yourself maintaining a parallel process just to keep the workbook accurate.

Method 2: Power Automate

Power Automate has HTTP connectors that can call the ipdata.co REST API. You set up a flow that reads rows from the workbook, calls the API with the IP from each row, and writes results back to specific columns.

A few questions before you continue — do you know how to configure an HTTP action in Power Automate? How to parse a JSON response and map specific fields to Excel columns? How to handle the batch endpoint versus the single-IP endpoint? How to schedule the flow to run on a cadence? If those feel foreign, Method 4 is the faster path.

If you are still here: the flow is buildable. The structural limit is that it fires one row at a time. Five hundred IPs means five hundred HTTP calls, five hundred items in your run history, and a flow that fails silently if row 187 returns a 429 and nothing retries it.

You probably just need the threat flags and the country codes. You probably have no idea how to configure retry logic or batch chunking in Power Automate — and you should not have to. So this lands on the IT desk, and now the enrichment that should have taken an hour is queued behind three other requests.

Licensing tier requirements apply too. The HTTP action and scheduled triggers sit behind premium connectors on most plans.

Method 3: The Previous Generation — Connector Add-Ons

Until recently, the best option for repeatable Excel-to-API workflows was a category of add-ins that let you configure field mappings, save a run template, and execute it on demand. You defined the input column, mapped each response field to a destination column, and ran it.

That was a meaningful step forward from CSV exports. Configs were reusable, output landed in the right columns, and the team could repeat the process without re-reading the docs.

But the template design, the field mapping, the batch-size decisions, the conditional logic for which rows to include — all of that was still on you. The add-in got the data through the pipe; it did not know what the data meant. And the moment you restructured the worksheet, your saved config needed manual repair.

This is the previous generation. It worked, and it required a configured operator every time.

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 the structure of what you are looking at, and through its built-in ipdata.co integration it can enrich IP columns, flag threat rows, and write results back — without templates, without Power Automate flows, without a CSV handoff. You just ask.

Example 1: Threat screening on a suspicious-login export

For each IP in column A, call ipdata.co and write country, ASN organization, and is_threat to columns B, C, and D. Flag any row where is_threat is true as HIGH RISK in column E.

SheetXAI batches the API calls, writes the enrichment fields into the right columns, and applies the HIGH RISK label to every flagged row.

Example 2: Currency segmentation for a customer workbook

Use ipdata.co to look up the currency code and currency name for every IP in column B and write them to columns C and D.

The enrichment and the column placement happen in one instruction. No mapping template needed.

Try It

Get the 7-day free trial of SheetXAI and open any Excel workbook with IP addresses, then ask it to enrich the column with ipdata.co data. The ipdata.co integration is included in every SheetXAI plan.