Back to Blog

How to Export Zapier JSON to Excel (Complete Guide)

Zapier is the glue of the internet, moving data between thousands of apps. But often, that data gets stuck in the middle—trapped as a complex JSON object inside a Webhook or Code step.

You might see a "Output" block full of raw JSON and think: "I just need this in a spreadsheet."

Navigating nested JSON arrays in Zapier (Line Items) is notoriously difficult. In this guide, I'll show you how to reliably get your JSON data out of Zapier and into Excel.

Method 1: The "Real-Time" Way (Zapier Excel Action)

Best For: Adding one row at a time as data comes in (e.g., New Lead -> Add Row).

If you want to build a live database, use Zapier's native Excel integration.

The Catch: It hates nested JSON. If your JSON has a list of items (like an order with multiple products), Zapier will often dump them all into one cell or create multiple rows in a messy way (Line Item Support).

Steps:

  1. Trigger: Catch Hook (or any app trigger).
  2. Action: Microsoft Excel Online -> "Add Row to Table".
  3. Map Fields: Click into each column and map the JSON values.
    • Tip: If you have a nested object (e.g., address.city), you might need a "Formatter" step or "Code by Zapier" step first to parse it.

Method 2: The "Bulk Analysis" Way (Export JSON -> Convert)

Best For: Debugging, historical data, or complex nested data that Zapier breaks.

Sometimes you just want to see the raw data to understand what's going on, or you need to bulk-process 1,000 webhook events that failed.

Step 1: get the Raw JSON

If you are using a "Catch Hook" trigger:

  1. Go to your Zap History.
  2. Find a specific run.
  3. Copy the "Data In" (the raw JSON payload).

Step 2: Convert to Excel

Zapier's raw output is often unformatted or deeply nested.

  1. Go to JsonExport.com.
  2. Paste the raw JSON from your Zap history.
  3. JsonExport will visualize the structure.
    • Table View: Great for checking if your "Line Items" are actually arrays.
    • Tree View: Great for debugging deeply nested logic.
  4. Click Download Excel.

Verdict: Essential for debugging Zaps or doing one-off analysis of payload data.

Method 3: The "Code Step" Way (Python/JavaScript)

Best For: Advanced users who need to transform the JSON before Excel.

If Zapier's "Formatter" tool isn't cutting it, use a Code Step.

Example (Python Step):

import json

# Input data from previous step
raw_json = input_data['raw_body']
data = json.loads(raw_json)

# Flatten specific field
flat_record = {
    "id": data.get("id"),
    "email": data.get("user", {}).get("email"),
    "tags": ", ".join(data.get("tags", [])) # Convert list to string for Excel
}

return flat_record

Then map flat_record fields to your Excel step.

Common Zapier JSON Headaches

1. "Line Items" Hell

Zapier treats arrays (lists) as "Line Items". If you map a Line Item to a single Excel cell, it might format it as A,B,C or throw an error. Fix: Use a Looping by Zapier step to run an action for each item in the JSON list, rather than trying to shove the whole list into one row.

2. Truncated Data

Zapier sometimes truncates very large JSON payloads in the history view. Fix: If you need to back up huge amounts of raw JSON data, add a step to save the raw JSON string to a text file in Google Drive or Dropbox. Then convert those files later using a desktop tool.

Conclusion

  • Live Data: Use Zapier's Excel integration (and pray line items work).
  • Debugging/Bulk: Copy the JSON from Zap History and use JsonExport.
  • Complex Parsing: Use a Code Step (Python/JS).

Mastering JSON in Zapier separates the pros from the amateurs. Good luck!