How to Connect Google Slides to Excel (4 Methods Compared)

The Problem With Getting Workbook Data In and Out of Google Slides

You have an Excel workbook full of structured data — client names and revenue figures, product specs, department KPIs, campaign performance numbers. You need that data in a presentation: one slide per client, a summary deck for the leadership sync, or updated figures pushed into an existing deck before it goes to the board.

Google Slides is good at building polished, shareable presentations. But moving data from an Excel workbook into a slide deck — or pulling slide records back out — is where the process falls apart. Most teams end up re-entering values by hand, exporting CSVs and rebuilding structure, or patching a script every time a column shifts.

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

Method 1: Manual Copy-Paste

The default with Excel starts with a CSV export. You export the sheet, open the file, copy a row, switch to a slide, paste each value into the right text box, go back, copy the next row, repeat. For a 20-row workbook, that's 20 decks. For a 10-column template, that's 200 individual entries.

The problem isn't the first pass. It's the second one — when a revenue figure changes, or the client's logo URL updates, or someone added a column between B and C. Now you're re-doing the export, re-matching the columns to the text boxes, re-checking every deck to confirm the old value is gone.

The CSV export step adds a layer of friction that makes every revision feel like starting over. Three rounds of updates on a 15-client deck set and you've spent more time on the data transfer than on the content itself.

Method 2: Power Automate

Power Automate has Google Slides connector options and can be wired to trigger on an Excel change or a schedule. You can set it up to copy a template presentation, read a workbook row, and replace placeholder text with the column values.

Quick check before you go further — do you know what a connector action is? What field mapping looks like in Power Automate's interface? How to authenticate against a Google Slides API from a Microsoft flow? If any of those require a Google search to answer, you'll spend more time on setup than the task is worth. Skipping ahead to Method 3 or 4 is the faster path.

If you're still here: the flow can work. You pick the trigger, map the workbook columns to the slide placeholders, chain the copy-template and replace-text actions. When it runs without errors, it's repeatable.

The ceiling appears fast when you're working at scale.

Running 30 rows through the flow means 30 separate action chains, 30 API calls to Google Slides, and a run history that becomes unreadable the first time one row has a mismatched field name. The others silently skip or produce partially populated decks.

You probably just need the presentation built and sent. You probably have no idea where Power Automate logs the error details for a specific row, or how to fix a field-mapping mismatch without rebuilding the whole flow. So you escalate it to whoever manages your Microsoft environment, and now the deck is delayed while you wait for a response.

The moment you add conditional logic — only include rows marked "approved," skip rows missing a logo URL — the flow gets complex enough that touching it feels risky.

Method 3: The Previous Generation — Connector Add-Ons

Until recently, the best option for repeatable Excel ↔ Google Slides workflows was a category of add-ons that let you define column-to-placeholder mappings, save a config, and run it against your workbook.

That was a genuine improvement over manual work. The output was consistent across runs, the field assignments were saved for next time, and the team wasn't rebuilding the logic every quarter.

But you were still responsible for designing the template, naming the placeholders to match the column headers, handling blank cells, and deciding which rows qualified. The tool got the data across, but the judgment about what to send, in what shape, was still entirely yours. And when a worksheet was restructured or a header renamed, the saved config broke and someone had to go back in to realign it.

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 Google Slides integration it can build presentations, update existing decks, or pull slide data back into your spreadsheet — on request. No template config, no automation wiring. You just ask.

Example 1: One deck per row, populated from a client table

For each row in my Excel sheet, copy the slide template with the ID in cell A1 and replace the client_name, revenue, and kpi placeholders with values from columns B, C, and D, then write the new presentation URL to column E

Each row produces a separate branded deck. The new presentation URL lands in column E so you have a record of every created deck without a separate tracking step.

Example 2: Refresh figures across a batch of existing slide decks

For each row in my Excel sheet with a presentation ID in column A, old figure in column B, and new figure in column C, open that presentation and replace all occurrences of the old figure with the new one

The pattern: instead of opening 15 decks one at a time, you describe the batch operation once and SheetXAI handles every row in sequence.

Try It

Get the 7-day free trial of SheetXAI and open any Excel workbook with client data, product rows, or a reporting table — then ask it to build you a deck. The Google Slides integration is included in every SheetXAI plan.