HumationHuman + Automation
Back to Catalog

Automate your Magento 2 weekly sales & performance reports

Kanaka Kishore KandregulaKanaka Kishore Kandregula
108 views
2/3/2026
emailgmailautomationgoogle-driveattachments
Official Page

Automatically fetches last week’s Magento 2 orders, summarises sales and product performance, logs the data to Google Sheets, and emails a polished report — all without logging into admin or buying extra modules.

Perfect for store owners and agencies.

✅ What This Workflow Does:

This workflow automatically fetches the last 7 days of orders from your Magento 2 store, summarizes key metrics (orders, revenue, products sold), groups product performance data, generates a Google Sheet with two tabs (Weekly Summary & Product Breakdown), and emails the report to your team in a modern dashboard-style HTML format — all without ever logging into Magento admin.

🔧 Modules Used:

🕒 Schedule Trigger ⚙️ Code (JavaScript) 🌐 HTTP Request 📊 Google Sheets ✉️ Gmail (HTML Email with custom design)

💼 Use Cases:

  • E-commerce store managers who want weekly sales snapshots without logging into Magento 2.
  • Agencies managing multiple Magento clients and reporting to them weekly.
  • Business owners who want automated insights without paying for extra reporting modules.
  • Marketing or growth teams that need product-wise performance regularly in Google Sheets.

🔒 Credentials Required:

  • Magento 2 API (Bearer Token)
  • Google Sheets OAuth2
  • Gmail OAuth2 (for sending HTML email reports)

📂 Category:

E-commerce / Magento 2 / Reporting / Automation

✨ Why This Saves Hours:

This workflow replaces manual Magento report exports, repetitive data cleanup, and weekly email formatting. Store managers often waste 1–2 hours/week collecting data — now it takes 0 minutes. Just set it and forget it. You don’t need to buy reporting extensions, log into the admin, or manually touch a spreadsheet again.

🤝 Need a Custom Workflow?

If you need this tailored for your own workflow, store, or client — 📩 Let’s connect. I build custom, high-performance n8n automations for e-commerce, growth, and reporting.

Contact: Author

👤 Author

Kanaka Kishore Kandregula Certified Magento 2 Developer https://gravatar.com/kmyprojects https://www.linkedin.com/in/kanakakishore

n8n Workflow: Scheduled Data Extraction and Reporting

This n8n workflow is designed to automate the process of fetching data from an external API, processing it, and then storing it in Google Sheets, with an optional email notification. It's ideal for generating regular reports or syncing data between systems.

What it does

This workflow performs the following steps on a scheduled basis:

  1. Triggers on a Schedule: The workflow starts at predefined intervals (e.g., daily, weekly, monthly).
  2. Makes an HTTP Request: It calls an external API endpoint to retrieve data.
  3. Processes Data with Custom Code: A Code node is used to transform or manipulate the data received from the HTTP request. This could involve filtering, reformatting, or calculating new values.
  4. Writes Data to Google Sheets: The processed data is then appended or updated in a specified Google Sheet.
  5. Sends Email Notification (Optional): After the data is written to Google Sheets, an email can be sent via Gmail to notify stakeholders or confirm the report generation.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • API Endpoint: Access to an API that provides the data you wish to process.
  • Google Account: A Google account with access to Google Sheets.
  • Gmail Account (Optional): A Gmail account if you wish to send email notifications.
  • n8n Credentials: Configured credentials for:
    • Google Sheets (OAuth2 recommended)
    • Gmail (OAuth2 recommended)

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, click "Workflows" in the left sidebar.
    • Click "New" and then "Import from JSON".
    • Paste the JSON content or upload the file.
  2. Configure Credentials:
    • Locate the "Google Sheets" and "Gmail" nodes.
    • Click on each node and select or create the necessary credentials for your Google account.
  3. Configure HTTP Request Node:
    • Open the "HTTP Request" node.
    • Set the URL, Method, and any Headers or Body parameters required by your API.
  4. Configure Code Node:
    • Open the "Code" node.
    • Modify the JavaScript code to perform the desired data transformations based on the output of your HTTP Request node and the input format required by Google Sheets.
  5. Configure Google Sheets Node:
    • Open the "Google Sheets" node.
    • Specify the Spreadsheet ID and Sheet Name where you want to write the data.
    • Configure the Operation (e.g., "Append Row", "Update Row") and map the data fields from the previous nodes to your sheet columns.
  6. Configure Gmail Node (Optional):
    • Open the "Gmail" node.
    • Set the To email address, Subject, and Body of the email. You can use expressions to include dynamic data from previous nodes in the email.
  7. Configure Schedule Trigger:
    • Open the "Schedule Trigger" node.
    • Set your desired schedule for the workflow to run (e.g., every Monday at 9 AM).
  8. Activate the Workflow:
    • Save the workflow.
    • Toggle the "Active" switch in the top right corner of the workflow editor to enable it.

Related Templates

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31