How to Connect Shortcut to Excel (4 Methods Compared)

The Problem With Getting Workbook Data In and Out of Shortcut

You have an Excel workbook full of data — sprint backlog items, epic plans, OKR tracking rows, member assignment lookups. You need it pushed into Shortcut, or pulled back out, without spending an afternoon retyping what the spreadsheet already contains.

Shortcut is good at organizing the actual work of building software. But the moment you need to move structured data between it and a workbook, you're on your own. The usual flow is: export a CSV if Shortcut offers one for what you need, or open both tools side by side and manually recreate each row as a story, epic, or iteration.

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

Method 1: Manual CSV Export and Paste

The default for Excel users. Export whatever Shortcut offers as CSV, open it in Excel, clean up the columns, and paste across. Or go the other direction: format your workbook as a CSV, import it, and deal with whatever the importer rejects.

For a workbook with 20 backlog items, this is 30 minutes of fiddling. For 120 items — the size of a real sprint planning intake — you're fighting CSV formatting, field mismatches, and state IDs that have to be looked up separately. The data was already in the workbook. The import process turns it into a forensics exercise.

Method 2: Power Automate

Power Automate has Shortcut connector options. You can wire up a trigger on a workbook change or a schedule, call the Shortcut API, and write the result back. The automation exists. It functions.

A quick gate before you continue — do you know what an API action is? What a trigger is? How field mapping works in Power Automate? Have you set up HTTP connectors before? If those feel unclear, skip ahead to Method 3 or 4. This path requires all of that before your first story gets created.

For the reader who passed: the setup works, but it's not lightweight. You configure the trigger, map every field from your Excel table to the Shortcut schema, handle the mismatch between your plain-text story types and Shortcut's enumerated values, test it, and debug it on the tier that supports what you need.

But a trigger-per-row flow is not the same as a bulk operation.

Creating 120 stories means 120 flow runs, 120 API calls, and a run history that becomes impossible to read when row 43 fails silently because the workflow state ID was wrong.

You probably just need the backlog into Shortcut. You probably have no idea how to wire a Power Automate flow — and there's no good reason you should. So you push this to whoever handles automation on the team, and now you're waiting for them to surface from whatever else they're dealing with.

And once you need to skip blank rows, look up state IDs from a second sheet, or filter by a column value, you've moved past what the flow can handle natively.

Method 3: The Previous Generation — Connector Add-Ons

Until recently, the best option for repeatable workbook-to-Shortcut workflows was a category of add-ons that let you configure column mappings, save templates, and run imports on demand. You picked your range, tagged your fields, saved a config, ran it.

That was a real step up from CSV fiddling. Output was consistent, configs were reusable, and you didn't have to redo your field mapping every run.

But you were still responsible for every decision: which columns mapped to which Shortcut fields, what the workflow state IDs were, what to do with rows that were missing a required field. The tool moved the data. The thinking was still entirely on you. And the moment your workbook structure changed — a new column, a renamed header — your config silently broke.

This is the previous generation. It worked, but it treated you like a system administrator.

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 Shortcut integration it can push to or pull from Shortcut for you. No template configuration, no field mapping dialogs, no automation glue. You just ask.

Example 1: Create stories from a backlog workbook

Add all 120 items in my Excel table to Shortcut as stories in workflow state 500, using column A as name and column B as description, then paste each new story ID into column C

SheetXAI reads the table, calls the Shortcut API for each row, and writes each new story ID back into column C. Rows with missing required fields get flagged instead of silently skipped.

Example 2: Export an iteration for velocity review

Get all Shortcut stories in iteration ID 12345 and list story name, type, estimate, state, and owner name starting in row 2 of this worksheet

The pattern: instead of exporting a CSV and cleaning it up, you ask for both the fetch and the layout in one prompt. SheetXAI handles the field extraction inline.

Try It

Get the 7-day free trial of SheetXAI and open any workbook with Shortcut backlog data — even a rough planning list — then ask it to create the stories. The Shortcut integration is included in every SheetXAI plan.