Magento 2 to Google Sheets, weekly sales clarity
Weekly reporting in Magento 2 usually means logging into admin, exporting CSVs, fixing columns, and then trying to explain the numbers in an email you’re rewriting from scratch.
If you’re a store owner, this is the boring task you keep postponing. Agency teams feel it when clients want updates “every Monday”. And e-commerce managers get stuck babysitting spreadsheets instead of improving the store. This Magento Sheets report automation turns last week’s orders into a clean Google Sheet plus a polished Gmail summary, automatically.
Below you’ll see what the workflow does, what you get out of it, and how to run it weekly without extra Magento modules.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Magento 2 to Google Sheets, weekly sales clarity
flowchart LR
subgraph sg0["Scheduled Automation Start Flow"]
direction LR
n0["<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/>Retrieve Week Range"]
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/>Fetch Prior Week 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/>Transform Order Data"]
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/>Weekly Summary Builder"]
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/>Product Mix Report"]
n5@{ icon: "mdi:database", form: "rounded", label: "Record Weekly Summary", pos: "b", h: 48 }
n6@{ icon: "mdi:database", form: "rounded", label: "Record Product Breakdown", pos: "b", h: 48 }
n7@{ icon: "mdi:database", form: "rounded", label: "Generate Spreadsheet File", pos: "b", h: 48 }
n8@{ icon: "mdi:play-circle", form: "rounded", label: "Scheduled Automation Start", pos: "b", h: 48 }
n9@{ icon: "mdi:message-outline", form: "rounded", label: "Dispatch Email Notice", pos: "b", h: 48 }
n2 --> n4
n2 --> n3
n0 --> n7
n3 --> n5
n8 --> n0
n4 --> n6
n7 --> n1
n5 --> n9
n1 --> n2
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 n8 trigger
class n5,n6,n7 database
class n1 api
class n0,n2,n3,n4 code
classDef customIcon fill:none,stroke:none
class n0,n1,n2,n3,n4 customIcon
The Problem: Weekly sales reporting becomes a recurring time sink
Magento has the data, but getting it into a shareable weekly update is the part that quietly steals your time. You export orders, realize your date range is off, export again, then spend another stretch cleaning fields so the spreadsheet is readable. After that comes the email: you copy numbers into a “quick summary,” second-guess revenue totals, and hope nobody asks for product-level performance. It’s not hard work. It’s constant work, and it breaks momentum every single week.
It adds up fast. Here’s where it usually breaks down.
- Pulling the “last 7 days” reliably is annoying, especially when week boundaries and time zones don’t match how you report.
- Manual exports and spreadsheet cleanup can easily take about 1–2 hours a week, and it’s never the same steps twice.
- Product mix insights often get skipped because grouping and totaling line items takes too long when you’re in a rush.
- Email summaries end up inconsistent, which means stakeholders stop trusting the format and start asking for “just one more detail.”
The Solution: Pull last week’s Magento 2 orders, write them to Sheets, and email a clean summary
This n8n workflow runs on a schedule and does the weekly admin work for you. It calculates the prior week’s date range, fetches the matching orders from your Magento 2 store via API, and then reshapes that raw order data into reporting-friendly totals. You end up with a Google Sheet that has two tabs: one for a Weekly Summary (orders, revenue, products sold) and another for Product Breakdown (product-wise performance). Finally, it sends a modern, dashboard-style HTML email through Gmail, so your team or client gets a crisp update without you touching a template.
The workflow starts with a scheduled trigger. From there it pulls Magento 2 orders using an HTTP request, transforms them with a few code steps, then writes structured rows into Google Sheets. Once the sheet is updated (and a spreadsheet file is generated), Gmail sends the finished report out automatically.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you send a weekly update to 5 people and you also keep a Google Sheet for historical tracking. Manually, you’d spend about 30 minutes exporting and checking Magento reports, another 30 minutes cleaning the spreadsheet, and about 20 minutes formatting an email summary. That’s roughly 1.5 to 2 hours every week. With this workflow, the “work” is basically zero minutes: it runs on schedule, updates two tabs in Sheets, then emails the polished summary automatically.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Magento 2 API to fetch last week’s orders
- Google Sheets to store weekly summary and product mix
- Gmail to send the HTML report email
- Magento 2 Bearer Token (get it from Magento Admin API integration settings)
Skill level: Intermediate. You’ll connect accounts, add API credentials, and validate Magento API responses once.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
Scheduled run each week. A Schedule Trigger starts the workflow automatically so you don’t rely on reminders or “I’ll do it later” energy.
Week range is calculated for you. A short code step determines the exact prior-week window, then passes those dates forward so the rest of the workflow always pulls the right slice of data.
Orders are pulled and reshaped. n8n uses an HTTP Request to fetch Magento 2 orders, then transforms the response into two reporting datasets: high-level totals and product-level performance. This is the part that replaces spreadsheet formulas and manual grouping.
Sheets is updated and the email goes out. Google Sheets receives two tabs (Weekly Summary and Product Breakdown), a spreadsheet file is generated, and Gmail sends a styled HTML report to the recipients you choose.
You can easily modify the recipients list to include clients or internal channels based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Schedule Trigger
Set when the weekly reporting workflow should run using the scheduled trigger node.
- Add and open Scheduled Automation Start to define the weekly run schedule.
- Choose your preferred weekly timing (day/time) so the report aligns with your business week.
- Leave Flowpast Branding as-is (it is a sticky note for documentation only and does not affect execution).
Step 2: Connect Google Sheets
Set up the spreadsheet storage for weekly summaries, product breakdowns, and the generated report file.
- Open Generate Spreadsheet File and choose the target spreadsheet and worksheet where the report file should be created or updated.
- Open Record Weekly Summary and configure the destination spreadsheet/sheet to store the weekly summary metrics.
- Open Record Product Breakdown and configure the destination spreadsheet/sheet for product mix data.
Credential Required: Connect your Google Sheets credentials in Generate Spreadsheet File, Record Weekly Summary, and Record Product Breakdown (credentials are missing in the workflow and must be added).
Step 3: Set Up Data Retrieval and Transformation
Define the date range, fetch the order data, and normalize it before reporting.
- Open Retrieve Week Range to confirm the code calculates the correct prior-week date range.
- Verify Generate Spreadsheet File receives input from Retrieve Week Range to build the reporting file context.
- Configure Fetch Prior Week Orders to call your order API endpoint and ensure any required headers or query parameters are added.
- Review Transform Order Data to map API responses into normalized fields used by the reporting steps.
Credential Required: If your API requires authentication, add the appropriate credentials or headers directly in Fetch Prior Week Orders.
Step 4: Configure Report Generation and Outputs
Build weekly summaries and product mix reports, then store results and email the report.
- Confirm Transform Order Data outputs to both Product Mix Report and Weekly Summary Builder in parallel for simultaneous report creation.
- Open Weekly Summary Builder and ensure the code outputs the fields expected by Record Weekly Summary.
- Open Product Mix Report and ensure the code outputs the fields expected by Record Product Breakdown.
- Configure Dispatch Email Notice to include the appropriate recipients and email content for the weekly report.
Credential Required: Connect your Gmail credentials in Dispatch Email Notice (credentials are missing in the workflow and must be added).
Step 5: Test and Activate Your Workflow
Run a manual test to confirm data retrieval, report generation, and delivery before enabling automation.
- Click Execute Workflow to run the process from Scheduled Automation Start manually.
- Confirm Record Weekly Summary and Record Product Breakdown write rows to the expected Google Sheets.
- Verify Dispatch Email Notice sends an email with the intended weekly reporting details.
- Activate the workflow using the Active toggle once the test run succeeds.
Common Gotchas
- Magento 2 credentials can expire or need specific permissions. If things break, check your Magento integration token and API user role permissions 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.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 30 minutes if your Magento token and Google access are ready.
No. You’ll mostly paste credentials and test a sample run. The code blocks are already in the workflow.
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 normal Gmail/Google usage and your Magento API access (usually no added cost).
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, but plan the structure first. The simplest approach is duplicating the workflow per store and changing the Magento API credentials plus the target Google Sheet. If you want one workflow to handle many clients, you can loop through a list of stores and swap the HTTP Request settings dynamically, then write each client to their own tabs or separate spreadsheets.
Usually it’s an expired or invalid Bearer Token. Regenerate the Magento 2 API token, update it in the HTTP Request node, and re-run the workflow. Also check that the API user has permission to read orders, and confirm your base URL is correct (a missing /rest endpoint setup is a common culprit). If it fails only on busy weeks, you may be hitting rate limits and need to add a short delay or fetch in smaller batches.
A typical Magento weekly volume (hundreds to a few thousand orders) is fine, assuming your API response size and Google Sheets limits are respected.
Often, yes, because this workflow needs real data shaping, two different sheet outputs, and a formatted HTML email. n8n handles multi-step logic cleanly without turning every branch into an extra paid task. It’s also easier to self-host, which matters if you run weekly reporting across multiple stores. Zapier or Make can still work if you keep it basic, but the minute you want product mix grouping, things get fiddly. If you want help deciding, Talk to an automation expert.
Once this is running, weekly reporting becomes background noise. The workflow handles the repetitive stuff, and you get your Monday mornings back.
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.
