How to Connect Ashby to Excel (4 Methods Compared)

The Problem With Getting Workbook Data In and Out of Ashby

You have an Excel workbook full of data — sourced candidates, headcount plans, referral batches, comp benchmarks. You need it pushed into Ashby, or pulled back out, without spending a Friday afternoon doing it by hand.

Ashby is built for recruiting teams that care about process and data quality. But there is no native "import from Excel" button. The default flow is to export a CSV from your workbook, reformat columns to match Ashby's field expectations, import through the UI, watch it error on row 47 because of a mismatched email format, fix the file, and try again.

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

Method 1: Manual Copy-Paste

Open Ashby, find the right object — candidate, job, application — fill in the fields one record at a time. For a tiny batch that arrives once, fine.

But sourcing campaigns don't produce five leads. The more common reality: you have a CSV export from LinkedIn or an internal tracking workbook with 80 rows of referrals. The usual flow is to save it as a CSV, clean the columns, try to match the field names Ashby expects, and import. When the import fails on a bad email format, you fix the file and try again.

The part that grinds people down is the reformatting cycle. Every time your internal column names differ from Ashby's field names — which is every time — someone spends time translating. Multiply that by every sourcing batch.

Method 2: Power Automate

Power Automate has Ashby connector options. You can build a flow that triggers on a new Excel table row, calls the Ashby API, and creates the corresponding record.

Before you go further — do you know what an HTTP action is in Power Automate? Have you configured an API connector before? Do you understand Ashby's application versus candidate object distinction? If those questions feel opaque, skip to Method 4. That's the faster path.

If you're still reading: the flow works. You set your trigger, map your table columns to Ashby's field schema, handle auth, test on one row, debug the type mismatches, and eventually it runs. A record appears in Ashby.

The problem is structural — one flow run fires for one row.

Pushing 60 referrals through it means 60 separate flow triggers, 60 API calls, and a run history that becomes impossible to read when row 22 fails silently and rows 23 through 60 succeed. You probably have no idea which records made it — and you probably didn't sign up to audit Power Automate run logs to find out. Most people push this work to whoever manages their M365 environment and then wait.

Complexity compounds once you add error handling, field normalization, and conditional logic into the same flow.

Method 3: The Previous Generation — Connector Add-Ons

Until recently, the best option for repeatable workbook-to-Ashby workflows was a category of add-ins that let you configure column mappings and save templates. You picked your table, tagged your fields, saved the config, and ran it.

That was a real improvement over manual entry. Configs were reusable, output was consistent, and you didn't reformat the same columns every week.

But you were still responsible for every mapping decision, every conditional rule about which rows to include, every field name that changed when Ashby updated their schema. The add-in moved the data. You still did all the thinking. And when your workbook structure changed, the config broke until someone rebuilt it.

This is the previous generation. It worked, but it required a dedicated operator to keep it running.

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 Ashby integration it can push to or pull from Ashby for you. No template configuration, no flow debugging, no column-mapping sessions. You just ask.

Example 1: Create Ashby candidates from a sourcing workbook

Read the SourcingBatch table and create one Ashby candidate per row using FirstName, LastName, Email, CurrentCompany, and LinkedInURL columns. Write the Ashby candidate ID into the CandidateID column.

SheetXAI reads the table, calls the Ashby candidates endpoint once per row, and writes the IDs back as it goes. Rows that error get the error text in CandidateID so you know exactly which ones need attention.

Example 2: Export accepted offers into this workbook

Pull all accepted Ashby offers from the last 90 days and write candidate name, job title, department, offer date, and salary into the CompensationReview sheet.

The pattern: instead of exporting, reformatting, and pasting, you describe what you want and SheetXAI handles the pagination and field mapping inline.

Try It

Get the 7-day free trial of SheetXAI and open any Excel workbook with Ashby-related data — a sourcing list, a headcount plan, a referral batch — then ask it to do one of the tasks above. The Ashby integration is included in every SheetXAI plan.