Shopify to Google Sheets, orders logged without gaps
Your order data is in Shopify, but your reporting is in Google Sheets. So you export, copy, paste, fix columns, and still end up wondering if you missed anything (especially on busy days).
This Shopify Sheets logging setup hits store owners first, but marketers building weekly dashboards and ops folks reconciling fulfillment feel it too. The goal is simple: every order lands in one spreadsheet, reliably, without gaps.
This workflow pulls orders through the Shopify Admin REST API with proper pagination, then writes the results into Google Sheets in a consistent format. You’ll see what it does, why it avoids the usual failure points, and how to run it on-demand or on a schedule.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Shopify to Google Sheets, orders logged without gaps
flowchart LR
subgraph sg0["When clicking ‘Test workflow’ Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Test workflow’", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get Orders"]
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Extract page_info "]
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Merge Loop items"]
n4@{ icon: "mdi:swap-vertical", form: "rounded", label: "List Orders", pos: "b", h: 48 }
n5@{ icon: "mdi:database", form: "rounded", label: "Google Sheets", pos: "b", h: 48 }
n6@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
n7@{ icon: "mdi:swap-vertical", form: "rounded", label: "Assign page_info parameter", pos: "b", h: 48 }
n8@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check page_info existence", pos: "b", h: 48 }
n1 --> n8
n4 --> n5
n3 --> n4
n6 --> n1
n2 --> n7
n8 --> n3
n8 --> n2
n7 --> n1
n0 --> n1
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0,n6 trigger
class n8 decision
class n5 database
class n1 api
class n2,n3 code
classDef customIcon fill:none,stroke:none
class n1,n2,n3 customIcon
The Problem: Shopify exports don’t stay complete
Shopify makes it easy to view orders. It’s much less pleasant to keep a clean, complete order log somewhere else. Exports get messy as volume grows, and “just pull the latest orders” turns into a constant fear that you skipped a page, duplicated rows, or broke your sheet structure with a new field. Then reporting becomes a debate instead of a decision: “Is this number real?” That uncertainty quietly costs you time every week, and it tends to show up right when you need answers fast (end of month, a big promo, a stock issue).
It adds up fast. Here’s where it breaks down in real life:
- Manual exports are easy to forget, which means your “dashboard” is always a few days behind.
- Pulling “all orders” can miss records if pagination isn’t handled correctly, especially when you rely on tools that assume page numbers.
- Sheets get corrupted over time when columns shift or new fields appear, so you end up fixing formulas instead of reading them.
- Duplicate rows sneak in when you re-run a sync without a consistent approach, and you don’t notice until totals look wrong.
The Solution: Paginated Shopify order sync into one Google Sheet
This workflow fetches Shopify orders using the Shopify Admin REST API and writes them into Google Sheets in a repeatable way. Instead of relying on the built-in “get many orders” shortcut, it uses an HTTP request that deliberately handles Shopify’s cursor-based pagination. That’s the part most exports get wrong. Each API call pulls a batch of orders, then the workflow reads the pagination token (from response headers), sets the token for the next request, and repeats until there are no more pages. After all pages are collected, it splits the orders into individual items and updates your target spreadsheet so one sheet stays accurate for reporting.
The workflow starts on a schedule or with a manual run. Shopify returns orders in chunks, and the workflow keeps looping by passing the page_info cursor forward. Finally, Google Sheets gets updated with a clean list of order records you can filter, pivot, and share.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you run a weekly ops check and you need all orders in a Google Sheet for pivots, refunds, and fulfillment notes. Manually, you export from Shopify, format columns, then sanity-check totals, which is usually about 45 minutes each time. If the export splits or you have to repeat it, it can easily hit 90 minutes. With this workflow, you click run (or let the schedule handle it), wait a few minutes for pagination to finish, and your sheet updates in one place with no file juggling.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Shopify Admin REST API to retrieve order batches.
- Google Sheets to store and report on orders.
- Shopify API credentials (create an app in Shopify admin).
Skill level: Intermediate. You’ll paste API credentials, choose fields, and confirm your sheet columns match what you’re writing.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
Manual or scheduled trigger. You can run it instantly for a backfill, or let the Scheduled Run Trigger keep your Google Sheet fresh without anyone remembering to export.
Shopify order retrieval with pagination. The HTTP Request node calls the Shopify Admin REST API with a limit (often 50, and you can push higher). Response headers are included so the workflow can see the cursor token Shopify uses for the next page.
Cursor parsing and loop control. A small code step reads the next-page token (page_info), stores it, and an If check decides if another request is needed. If yes, it loops back to fetch the next chunk. If not, it moves on.
Sheet update. Orders are combined, split into row-shaped items, then the Google Sheets node writes or updates records in your target spreadsheet so your reporting stays in one file.
You can easily modify the fields you pull from Shopify to match the exact columns you want in Sheets based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Trigger Type
This workflow can be started manually or on a schedule before pulling Shopify orders.
- Open Manual Start Trigger if you want to run the workflow on-demand.
- Open Scheduled Run Trigger to define an automated interval (set the schedule rule as needed for your cadence).
- Ensure both Manual Start Trigger and Scheduled Run Trigger connect to Fetch Order Records as shown in the workflow.
Step 2: Connect Shopify
Configure the API call that fetches order records from Shopify.
- Open Fetch Order Records.
- Credential Required: Connect your shopifyAccessTokenApi credentials.
- Set URL to
https://{store}.myshopify.com/admin/api/2025-01/orders.json. - Enable Send Query and ensure the query parameters include limit =
250and fields =id,note,email,processed_at,customer. - For pagination, set the dynamic query parameter name to
{{ $json.page_info ? "page_info" : "status" }}and value to{{ $json.page_info ? $json.page_info : 'any' }}.
{store} in the Shopify URL with your actual store subdomain, or the request will fail.
Step 3: Set Up Pagination and Aggregation
These nodes determine whether more pages exist and build a combined result set.
- In Verify Next Page Link, keep the condition that checks
{{ $json.headers.link }}does notContainsrel="next"to determine if a next page exists. - Confirm Verify Next Page Link sends one output to Combine Loop Results and the other to Parse Next Page Token.
- In Parse Next Page Token, keep the provided JavaScript for parsing the
linkheader into pagination params. - In Set Next Page Value, set the page_info assignment value to
{{ $json.page_info }}. - Ensure Set Next Page Value routes back to Fetch Order Records to continue pagination.
- In Combine Loop Results, keep the JavaScript that concatenates all runs of Fetch Order Records for a full dataset.
Step 4: Configure Output to Google Sheets
Split the order list and write each order to your spreadsheet.
- Open Split Order Items and set Field to Split Out to
body.orders. - Open Update Sheets Records.
- Credential Required: Connect your googleSheetsOAuth2Api credentials.
- Set Operation to
appendOrUpdate. - Set Document to
[YOUR_ID]and Sheet toshopify_orders. - Map columns: id =
{{ $json.id }}, note ={{ $json.note }}, email ={{ $json.email }}, processed_at ={{ $json.processed_at }}. - Keep Matching Columns set to
idso records update by order ID.
Step 5: Test and Activate Your Workflow
Run a manual test, verify output, then activate the scheduled automation.
- Click Execute Workflow using Manual Start Trigger.
- Confirm Fetch Order Records returns data and that Verify Next Page Link routes correctly based on pagination.
- Verify Update Sheets Records appends or updates rows in the
shopify_orderssheet. - Once validated, activate the workflow so Scheduled Run Trigger runs on your defined interval.
Common Gotchas
- Shopify Admin REST API credentials can expire or lose scopes after app changes. If things break, check your Shopify app permissions and regenerated access token first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Google Sheets writes fail more often than people expect when column headers drift. Keep a fixed header row and only change fields in the workflow after you update the sheet.
Frequently Asked Questions
About 30 minutes if your Shopify and Google credentials are ready.
No. You’ll mostly paste credentials and choose which order fields to store. The included workflow already handles the pagination logic for you.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Shopify API usage (usually negligible for typical order pulls).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you should. Change the fields parameter in the Shopify HTTP Request so you only pull what you’ll actually report on, then align those fields with the columns your Google Sheets node writes. Common tweaks include adding customer email, financial status, fulfillment status, and line-item totals. Keep your header row stable, then adjust the workflow to match it, not the other way around.
Most of the time it’s an invalid or expired access token, so regenerating the Shopify Admin API credentials fixes it. It can also be missing API scopes on your Shopify app, or a wrong store domain in the request URL. If it fails only on larger pulls, you may be hitting rate limits, so lowering the limit (batch size) usually helps.
A lot. Shopify returns orders in paginated batches (often 50–250 per request), and the workflow keeps looping until it’s done, so volume is mostly constrained by API limits and how long you’re willing to let it run. On n8n Cloud, your monthly execution quota matters; on self-hosted n8n there’s no execution cap, but your server size and Google Sheets write speed become the bottleneck.
Often, yes, if “all orders with pagination” is the requirement. Cursor-based pagination is where simpler tools tend to get awkward, and you can end up with partial exports unless you build a more complex scenario. n8n also gives you control over headers, conditional logic, and loop behavior without charging extra for every branch. Zapier or Make can still be fine for lightweight “new order → add row” syncs, but they’re not my first choice for backfills or audits. If you’re torn, Talk to an automation expert and we’ll help you choose based on volume and reporting needs.
Once this is running, your sheet stops being “another export” and starts being dependable. Honestly, that alone is worth the setup.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
