Magento 2 to Google Sheets, spot stuck orders fast
Stuck orders are sneaky. They sit in “processing” for days, nobody notices, and then support tickets pile up right when you’re trying to focus on sales.
Store managers usually catch the heat first, but ops leads and small e-commerce owners feel it too. This Magento Sheets alert automation gives you a clean weekly report plus an email, so you can spot stalled fulfilment before refunds and chargebacks start.
Below, you’ll see exactly what the workflow does, what you need to run it, and how to adapt it for your order statuses and team.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Magento 2 to Google Sheets, spot stuck orders fast
flowchart LR
subgraph sg0["Scheduled Automation Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Scheduled Automation Trigger", pos: "b", h: 48 }
n1@{ icon: "mdi:database", form: "rounded", label: "Generate Spreadsheet", pos: "b", h: 48 }
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/httprequest.dark.svg' width='40' height='40' /></div><br/>Retrieve Media Location"]
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/>Resolve Logo Asset"]
n4["<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/>Compute Recent Workdays"]
n5["<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/>Fetch Active Orders"]
n6["<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/>Assemble Order Details"]
n7@{ icon: "mdi:database", form: "rounded", label: "Upsert Sheet Row", pos: "b", h: 48 }
n8["<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/>Compose Report Email"]
n9@{ icon: "mdi:message-outline", form: "rounded", label: "Dispatch Email Notice", pos: "b", h: 48 }
n3 --> n4
n2 --> n3
n6 --> n7
n0 --> n1
n1 --> n2
n8 --> n9
n5 --> n6
n7 --> n8
n4 --> n5
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 trigger
class n1,n7 database
class n2,n5 api
class n3,n4,n6,n8 code
classDef customIcon fill:none,stroke:none
class n2,n3,n4,n5,n6,n8 customIcon
The Problem: Stuck orders hide in plain sight
Magento 2 doesn’t “feel” broken when orders get stuck. The store still takes payments, customers still get confirmation emails, and your dashboard still looks normal at a glance. Then a week later you’re digging through order grids, trying to remember which statuses matter, which ones are normal delays, and which ones mean something failed in shipping, invoicing, or payment capture. By the time you find the pattern, the customer has already followed up twice. Honestly, that’s when refunds start to look cheaper than fixing the root issue.
It adds up fast. Here’s where it breaks down in real operations.
- Someone has to manually filter orders, check dates, and eyeball what looks “stale” every week.
- Weekends blur the timeline, so teams argue about whether an order is really late or just waiting through non-business days.
- Important details get lost during handoffs, like the customer phone number or order value, so follow-ups take longer than they should.
- No consistent report means you can’t spot the same status getting “stuck” again and again.
The Solution: Weekly stuck-order report to Sheets + Gmail
This workflow runs automatically every Monday morning and checks your Magento 2 store for orders that have not moved status for the last 7 business days (it excludes weekends, so you’re not chasing false alarms). It pulls the order data through the Magento 2 REST API, then formats the useful fields into something your team can act on: customer name, contact details, order value, and the status that’s not changing. Next, it creates a fresh Google Sheet named with the current date and appends the stuck orders as clean rows. Finally, it sends a branded HTML email through Gmail to the store manager with a snapshot table and a link button to the full Sheet for follow-up and delegation.
The workflow starts with a scheduled trigger at 8 AM on Monday. From there it computes the correct business-day window, fetches and reshapes Magento order data, writes the report to Google Sheets, and sends the Gmail alert once the sheet is ready.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say your store averages 20 “active” orders a day. A manual weekly audit often means filtering, opening orders, copying contact info, and pasting into a tracker, which is easily 5 minutes per order you investigate, plus another 30 minutes to write an email. That can turn into about 2–3 hours every Monday. With this workflow, the trigger runs at 8 AM, the sheet is generated in minutes, and the manager gets the Gmail alert without lifting a finger. You review the list, assign fixes, done.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Magento 2 Admin API access to fetch orders via REST
- Google Sheets to store the dated stuck-order report
- Gmail to send the manager’s weekly alert email
- Magento 2 Bearer token (generate it in Magento admin integrations)
Skill level: Intermediate. You’ll connect credentials, paste an API base URL, and confirm which order statuses you consider “stuck.”
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A scheduled Monday-morning trigger fires. The workflow is set to run at 8 AM, so the report lands before standups and daily fulfilment planning.
Business days are calculated automatically. A small JavaScript step computes the last 7 weekdays and skips weekends, which means the “stuck” definition matches how teams actually work.
Magento 2 orders are pulled and cleaned up. n8n calls the Magento 2 REST API (HTTP Request), then assembles the fields you’ll care about in a report: customer details, order value, status, and identifiers that help you troubleshoot.
A new Google Sheet is created, then filled. The workflow generates a dated spreadsheet and inserts one row per stuck order, using batching and merge logic so larger lists still process reliably.
A Gmail alert is sent with a snapshot. The email includes an HTML table summary and a button that links to the full Sheet so the manager can assign items quickly.
You can easily modify which statuses are considered “stuck” or change the email recipient based on store/region. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Scheduled Trigger
This workflow starts on a schedule and then builds the reporting pipeline in a single linear flow.
- Add and open Scheduled Automation Trigger to define when the workflow runs.
- Set your preferred schedule options (e.g., daily or weekly cadence).
- Confirm the execution order continues to Generate Spreadsheet.
Step 2: Connect Google Sheets
The workflow creates or updates spreadsheet data before composing the email report.
- Open Generate Spreadsheet and configure the target spreadsheet and worksheet where the report data will live.
- Open Upsert Sheet Row and set the sheet and key fields for upserting order rows.
- Ensure Generate Spreadsheet outputs into Retrieve Media Location and Upsert Sheet Row receives data from Assemble Order Details.
Credential Required: Connect your Google Sheets credentials in Generate Spreadsheet and Upsert Sheet Row.
Step 3: Set Up Media and Workday Processing
These nodes resolve branding assets and compute the date range used to pull active orders.
- Open Retrieve Media Location and configure the HTTP request to your asset endpoint.
- Review Resolve Logo Asset to map the media URL or path from the previous step.
- Open Compute Recent Workdays and confirm the code produces the desired date range for order retrieval.
- Verify the sequence Generate Spreadsheet → Retrieve Media Location → Resolve Logo Asset → Compute Recent Workdays.
Step 4: Fetch and Assemble Order Data
This segment pulls active orders and formats them for spreadsheet insertion.
- Open Fetch Active Orders and configure the HTTP request to your orders API using the date range from Compute Recent Workdays.
- Open Assemble Order Details and confirm the code maps API fields into structured rows.
- Ensure the execution path continues from Compute Recent Workdays → Fetch Active Orders → Assemble Order Details.
Step 5: Configure Reporting Outputs
The workflow writes order rows to Google Sheets, composes an email summary, and sends the report.
- Review Upsert Sheet Row to ensure rows are inserted or updated with the assembled order details.
- Open Compose Report Email and verify the email body uses the sheet and branding data from prior steps.
- Open Dispatch Email Notice and set the recipient, subject, and body mapping from Compose Report Email.
- Confirm the final execution path is Upsert Sheet Row → Compose Report Email → Dispatch Email Notice.
Credential Required: Connect your Gmail credentials in Dispatch Email Notice.
Step 6: Test and Activate Your Workflow
Run a manual test to confirm the sheet updates and the report email are generated correctly.
- Click Execute Workflow and verify data flows from Scheduled Automation Trigger through to Dispatch Email Notice.
- Check your spreadsheet to confirm Upsert Sheet Row has inserted or updated the expected rows.
- Confirm the email sent by Dispatch Email Notice matches the output from Compose Report Email.
- Activate the workflow to run on schedule once testing is successful.
Common Gotchas
- Magento 2 API credentials can expire or lack the right scope. If calls fail, check your Magento Admin integration token and user role permissions first.
- If you’re using batch processing for a large order list, run time can vary. If downstream nodes fail on empty data, increase the batch wait/handling so the sheet step doesn’t race ahead.
- Default email formatting in the HTML step is fine, but generic. Add your brand voice, escalation instructions, and the exact status definitions early or the team will ignore the alert.
Frequently Asked Questions
About 30 minutes if your Magento, Sheets, and Gmail access are ready.
No. You will connect accounts and paste a few values like your Magento API base URL.
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 Magento hosting limits if your API is slow under load (the workflow itself doesn’t add per-request fees).
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. The “Compute Recent Workdays” and “Fetch Active Orders” parts define what “stuck” means, and the “Assemble Order Details” step controls what columns you see in Google Sheets. Common tweaks include checking only “processing” orders, excluding “pending_payment,” and routing different status groups to different recipients.
Most of the time it’s an expired or invalid bearer token. Regenerate the Magento 2 integration access token, then update the HTTP Request credentials in n8n. Also verify the API user role can read orders, and watch for rate limits if your store has a large order volume.
Hundreds per run is normal, and more depends on your Magento API speed and your n8n plan/server.
Often, yes, because this needs business-day date logic, batching, and a formatted HTML email, and n8n handles that without turning it into a pricey multi-step scenario. Zapier or Make can work if you keep it simple, but Magento API pagination and “exclude weekends” logic gets clunky fast. n8n also gives you a real self-hosting option, which matters when you want the workflow to run forever without worrying about task limits. If you’re on the fence, pick the tool your team will actually maintain. Talk to an automation expert and we’ll sanity-check the best fit.
Once this is running, Monday morning stops being a scavenger hunt. The workflow watches your Magento orders, builds the report, and nudges the right person so problems get fixed while they’re still cheap.
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.
