Squarespace to Google Sheets, orders logged clean
Exporting orders from Squarespace sounds simple. Then you do it every week, reconcile missing rows, fix columns that shifted, and realize your “quick report” just ate your afternoon.
Store owners feel it first. But marketing managers trying to track campaigns and accountants cleaning up month-end numbers run into the same mess. This Squarespace Sheets orders automation keeps your spreadsheet accurate without babysitting exports.
This workflow pulls every order from the Squarespace Commerce API (in paginated batches) and writes it into Google Sheets with consistent columns. You’ll see what breaks, what this fixes, and how to run it on-demand or on a schedule.
How This Automation Works
See how this solves the problem:
n8n Workflow Template: Squarespace to Google Sheets, orders logged clean
flowchart LR
subgraph sg0["On clicking 'execute' Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "On clicking 'execute'", 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/>Query Orders"]
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split Out Order ", pos: "b", h: 48 }
n3@{ icon: "mdi:database", form: "rounded", label: "Squarespace Orders Spreadsheet", pos: "b", h: 48 }
n4@{ icon: "mdi:swap-vertical", form: "rounded", label: "Globals", pos: "b", h: 48 }
n5@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
n4 --> n1
n1 --> n2
n5 --> n4
n2 --> n3
n0 --> n4
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,n5 trigger
class n3 database
class n1 api
classDef customIcon fill:none,stroke:none
class n1 customIcon
The Challenge: Clean order reporting without messy exports
Manual order exports are deceptively fragile. One day you export “all orders,” the next day you export “last 30 days,” and suddenly your totals don’t match. Columns can shift depending on what fields are present, and someone inevitably pastes into the wrong tab. If you run ads, it gets worse because you want “orders since X date” for a campaign recap, but you also need the full history for taxes and inventory checks. The mental load is the real cost: you stop trusting your sheet, so you double-check everything.
It adds up fast. Here’s where it breaks down in real teams.
- Exporting orders, downloading a file, and re-uploading it turns into a weekly ritual you can’t skip.
- Small formatting differences (dates, currency, blank fields) create “ghost errors” that ruin pivots and charts.
- Pagination and date filtering are easy to get wrong manually, so you miss orders or accidentally duplicate them.
- When someone asks, “What changed since last Friday?” you end up rebuilding the report from scratch.
The Fix: Automatically pull Squarespace orders into Google Sheets
This n8n workflow connects directly to the Squarespace Orders API and moves the data into Google Sheets for you. You can run it manually when you need an update right now, or let it run on a schedule so your sheet stays current in the background. Instead of exporting CSVs, cleaning them, and hoping your columns still line up, the workflow fetches orders in paginated batches and writes each order record into the spreadsheet in a consistent structure. It also uses a “Global Defaults” configuration step so you can set things like API version, date windows (modifiedAfter/modifiedBefore), fulfillment status, and maximum pages without editing the whole workflow. Less fiddling. More reliable reporting.
The workflow starts with either a timed trigger or a manual run. Then it builds the API request based on your Global settings, pulls orders from Squarespace, splits the results into individual records, and inserts each record into Google Sheets. You get a clean, analyzable table that’s always ready when you open it.
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Say you export orders twice a week: once for marketing (campaign tracking) and once for bookkeeping. A typical export-and-clean cycle takes maybe 30 minutes each time, plus another 20 minutes when something looks off. That’s roughly 2 hours most weeks. With this workflow, you trigger the run (about 2 minutes), let it fetch paginated batches in the background, and your Google Sheet is updated without file handling. You’re mostly just reviewing numbers, not rebuilding them.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Squarespace Commerce API to retrieve order data securely.
- Google Sheets to store orders in consistent columns.
- Squarespace API Key (get it from your Squarespace settings).
Skill level: Beginner. You’ll connect accounts, paste an API key, and choose a spreadsheet.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
A manual run or scheduled trigger kicks things off. If you want a “refresh now” button, use the manual trigger. If you prefer hands-off updates, the schedule trigger runs it for you.
Global settings define what you want to pull. This is where you set your Squarespace API version and optional filters like modifiedAfter/modifiedBefore, fulfillmentStatus, and how many pages to fetch (including “keep paging until there’s nothing left”).
Squarespace orders are retrieved in batches. The workflow calls the Squarespace Orders endpoint via HTTP Request, then uses pagination (cursor-based) to keep going until it has what you asked for.
Each order is written into Google Sheets as a clean record. Split-over-items breaks the response into individual orders, then the Google Sheets node inserts rows so your reporting sheet stays tidy and usable.
You can easily modify the date filters to pull “since last run” instead of a fixed window based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Trigger Type
Set up how the workflow starts, whether manually or on a schedule, before data flows into the rest of the automation.
- Add the Manual Run Kickoff node to enable on-demand testing and manual runs.
- Add the Timed Automation Trigger node and define a schedule in Rule so the workflow runs automatically.
- Connect both Manual Run Kickoff and Timed Automation Trigger to Global Defaults so either trigger initializes the request settings.
Step 2: Connect Squarespace Orders API
Configure the API request that pulls order data from Squarespace using the HTTP request node.
- Open Fetch Order List and set URL to
=https://api.squarespace.com/{{ $json["api-version"] }}/commerce/orders. - Enable Send Query and set query parameters to:
- modifiedAfter →
{{ $json.modifiedAfter }} - =modifiedBefore →
{{ $json.modifiedBefore }} - cursor →
{{ $json.cursor }} - =fulfillmentStatus →
{{ $json.fulfillmentStatus }}
- modifiedAfter →
- In Pagination, keep maxRequests set to
{{ $json.maxPage === -1 ? Infinity : $json.maxPage }}and completeExpression set to{{ !$response.body.pagination.nextPageCursor }}so all pages are fetched. - Credential Required: Connect your httpHeaderAuth credentials in Fetch Order List.
Step 3: Set Up Processing Defaults and Split Orders
Initialize request defaults and split the API response so each order is processed individually.
- Open Global Defaults and confirm the assignments:
- api-version →
1.0 - modifiedAfter →
- modifiedBefore →
- cursor →
- fulfillmentStatus →
- maxPage →
-1
- api-version →
- Connect Global Defaults → Fetch Order List so the API request uses these values.
- Open Split Order Records and set Field To Split Out to
resultso each order becomes a separate item. - Connect Fetch Order List → Split Order Records to process the response array.
Step 4: Configure Output to Google Sheets
Append or update each order record in your Google Sheet with mapped fields from the API response.
- Open Update Order Spreadsheet and set Operation to
appendOrUpdate. - Set Document ID to
[YOUR_ID]and Sheet Name to[YOUR_ID](the sheet namedsquarespace_ordersin the workflow). - Keep Matching Columns set to
Order IDso existing orders update instead of duplicating. - Verify key column mappings include:
- Email →
{{ $json.customerEmail }} - Total →
{{ $json.grandTotal.value }} - Currency →
{{ $json.subtotal.currency }} - Order ID →
{{ $json.orderNumber }} - Billing Name →
{{ $json.billingAddress.firstName }} {{ $json.billingAddress.lastName }} - Channel Name →
{{ $json.channel }} - Fulfillment Status →
{{ $json.fulfillmentStatus }}
- Email →
- Credential Required: Connect your googleSheetsOAuth2Api credentials in Update Order Spreadsheet.
[YOUR_ID] with your actual Google Sheet ID and worksheet reference, otherwise the node will fail to locate the file.Step 5: Test and Activate Your Workflow
Run a manual test to confirm data pulls from Squarespace and writes into Google Sheets, then enable the schedule for production.
- Click Execute Workflow from the Manual Run Kickoff trigger to run a test.
- Verify that Fetch Order List returns orders and Split Order Records outputs individual items.
- Check your Google Sheet and confirm that Update Order Spreadsheet appended or updated rows based on
Order ID. - Once verified, toggle the workflow to Active so Timed Automation Trigger runs on schedule.
Watch Out For
- Google Sheets credentials can expire or need specific permissions. If things break, check the Google account connection inside n8n’s Credentials list first.
- If you’re using a schedule trigger, pagination can take longer when order volume spikes. Increase your maxPage setting carefully (or keep it at -1) and make sure your n8n execution timeout isn’t too aggressive.
- Squarespace API filters can conflict: cursor pagination can’t be combined with other filters. If you’re not getting expected results, remove cursor and use modifiedAfter/modifiedBefore instead.
Common Questions
Usually about 30 minutes if your API key and spreadsheet are ready.
Yes. There’s no coding, but you do need to follow the setup steps carefully in n8n and Google Sheets.
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 Squarespace and Google API usage (usually minimal for typical stores).
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.
You can adjust the “Global Defaults” settings to change date windows, fulfillment status, and pagination behavior without rebuilding the workflow. Common tweaks include pulling only PENDING orders for fulfillment checks, pulling “modified after yesterday” for daily reporting, or setting maxPage to fetch full history during tax season. If your sheet uses a different structure, map fields in the Google Sheets step so every run writes to the same columns. And if you want separate tabs per month, you can duplicate the Sheets action and route based on the order date.
Most of the time it’s an API key issue or the wrong API version in your Global settings. Regenerate the Squarespace API key, confirm it has Commerce permissions, and update it in n8n. If the request works for one page but fails later, it can also be a cursor/filter conflict or a rate limit spike during big backfills.
For most stores, it comfortably handles daily or hourly syncs, and pagination lets it pull large order histories in batches.
Often, yes, because this kind of pull-sync needs pagination, cursor handling, and flexible filtering, which can get awkward (and pricey) in simpler automation tools. n8n is also easier to run on a schedule without worrying about per-step pricing when you’re processing lots of orders. Zapier or Make can still be fine if you only need a basic “new order to sheet” action and don’t care about backfills. The big difference is control: this workflow is built to fetch everything reliably, not just react to one event. Talk to an automation expert if you want a quick recommendation for your exact setup.
Once this is running, your spreadsheet stops being a “project” and becomes a tool again. The workflow handles the repetitive pulls, so you can focus on decisions, not cleanup.
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.
