Back to Catalog

Weekly Magento 2 stuck order reporting with Gmail & Google Sheets

Official Page

Automatically identifies and reports Magento 2 orders stuck for the past 7 business days. Sends a weekly email alert to the store manager with a Google Sheets report, helping streamline order follow-ups and prevent fulfilment delays.

Automate_Order_Stuck_reporting2.png

πŸ” What It Does:

This n8n automation identifies Magento 2 orders that have been stuck in the same status (like "processing") for the past 7 weekdays (excluding weekends), compiles them into a clean Google Sheet report, and emails the store manager every Monday morning with a snapshot and link to the full data for immediate action.

βš™οΈ Technical Highlights:

  • Automatically runs every Monday at 8 AM using the Schedule Trigger.
  • Dynamically calculates business days only (excluding weekends) to identify stale orders.
  • Fetches order data using Magento 2 REST API.
  • Filters and formats key details like customer name, order value, phone, and email.
  • Stores the data in a Google Sheet titled with the current date.
  • Sends a professionally formatted HTML email to the manager with:
  • A summary table of stuck orders.
  • A button linking directly to the full Google Sheet report.

βœ… Ideal For:

  • Magento 2 store owners/managers who need better visibility on stuck or delayed orders.
  • Operations teams who want to avoid lost revenue or customer complaints due to order inaction.
  • Automation engineers looking to integrate Google Workspace and Magento efficiently using n8n.
  • πŸ“ˆ Why This Matters in the Current Market:
  • In e-commerce, stuck orders = lost trust and lost revenue. As fulfillment expectations continue to rise, proactively managing delayed or idle orders is crucial. This workflow empowers store managers to act fast, reduce manual monitoring, and keep operations smooth β€” all while preserving customer satisfaction and operational reputation.

πŸ”§ Modules Used:

  • Schedule Trigger
  • HTTP Request (Magento 2 REST API)
  • Code (JavaScript logic for date filtering, formatting)
  • Google Sheets (Create & Append rows)
  • Gmail (Send custom HTML email)
  • Set/Get Logo (optional media path fetch for branding)

πŸ’Ό Use Cases:

  • Weekly operational check-ins for stuck orders.
  • Root cause analysis of order processing delays.
  • Escalation trigger for order fulfillment teams.
  • Dashboard data feed for pending revenue reports.
  • Enhance Magento store manager awareness with automation.

πŸ”’ Credentials Required:

  • Magento 2 Bearer Auth (Admin API access)
  • Google Sheets OAuth2 (Access to Google Drive & Sheets)
  • Gmail OAuth2 (Authorized sender account)

πŸ“‚ Category:

Magento 2 / E-Commerce Automation / Order Management / Reporting

πŸ’¬ Need Help?

If you'd like help customizing this for your Magento store, such as: Filtering by specific order statuses Adding Slack/Telegram alerts Multi-store/multi-manager support Feel free to reach out β€” we can assist in tailoring the workflow to your unique business logic.

Contact: Author

πŸ‘€ Author Kanaka Kishore Kandregula Certified Magento 2 Developer https://gravatar.com/kmyprojects https://www.linkedin.com/in/kanakakishore

Weekly Magento 2 Stuck Order Reporting with Gmail & Google Sheets

This n8n workflow automates the process of identifying and reporting stuck Magento 2 orders, delivering a weekly summary via email and logging the details in a Google Sheet. It helps e-commerce teams proactively address order issues, ensuring smooth operations and preventing customer service bottlenecks.

What it does

This workflow runs on a weekly schedule and performs the following actions:

  1. Triggers Weekly: Initiates the workflow once a week at a specified time.
  2. Fetches Stuck Orders: Makes an HTTP request to a Magento 2 API endpoint to retrieve a list of orders that are currently in a "stuck" state.
  3. Processes Order Data: Uses a Code node to transform and format the retrieved order data into a more readable and usable format.
  4. Logs to Google Sheets: Appends the details of the stuck orders (after processing) to a designated Google Sheet, creating a historical record.
  5. Sends Email Report: Compiles the processed stuck order data into an email and sends it via Gmail to a specified recipient (e.g., the operations team or customer support).

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Magento 2 API Access: An accessible Magento 2 API endpoint for retrieving order data, along with appropriate authentication credentials (e.g., API key or token).
  • Google Sheets Account: A Google account with access to Google Sheets. You'll need to create a new spreadsheet or identify an existing one where the stuck order data will be appended.
  • Gmail Account: A Google account with access to Gmail for sending the email reports.
  • n8n Credentials: Configured n8n credentials for:
    • Google Sheets (OAuth2 or Service Account)
    • Gmail (OAuth2)
    • HTTP Request (if your Magento API requires authentication, e.g., Bearer Token, Basic Auth)

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file for this workflow.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • Click on the "Google Sheets" node and set up your Google Sheets credential.
    • Click on the "Gmail" node and set up your Gmail credential.
    • Click on the "HTTP Request" node. If your Magento API requires authentication, configure the appropriate credential (e.g., "Generic Credential" for Bearer Token or Basic Auth).
  3. Customize Nodes:
    • Schedule Trigger (Node 839): Adjust the "Mode" and "Time" to your desired weekly schedule for running the report.
    • HTTP Request (Node 19):
      • Update the URL field to your Magento 2 API endpoint for fetching orders.
      • Configure Headers or Query Parameters as needed for filtering orders by status (e.g., status=stuck or similar).
      • Ensure Authentication is correctly set up if required by your Magento API.
    • Code (Node 834): Review and modify the JavaScript code if you need to change how the Magento order data is processed or formatted before being sent to Google Sheets and Gmail.
    • Google Sheets (Node 18):
      • Select the Spreadsheet ID of your target Google Sheet.
      • Specify the Sheet Name where the data should be appended.
      • Ensure the Operation is set to Append Row.
    • Gmail (Node 356):
      • Set the To email address(es) for the recipients of the report.
      • Customize the Subject and Body of the email to include relevant information from the processed order data. Use expressions like {{ $json.propertyName }} to dynamically insert data.
  4. Activate the Workflow: Once all nodes are configured, save the workflow and activate it by toggling the "Active" switch in the top right corner.

The workflow will now run automatically on your defined schedule, providing timely reports on stuck Magento orders.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger β€” Manually start the workflow or schedule it to run periodically. Input Setup β€” Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) β€” Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring β€” Clean and convert GPT output into JSON format. Data Storage (Google Sheets) β€” Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the β€œSet Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors β†’ Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection β†’ Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report β†’ Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization β†’ Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs β†’ Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chatβ€”turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. πŸ“‹ What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing πŸ”§ Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation πŸ”‘ Required Credentials OpenAI API Setup Go to platform.openai.com β†’ API keys (sidebar) Click "Create new secret key" β†’ Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai β†’ Dashboard β†’ API Keys Generate a new API key β†’ Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) βš™οΈ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflowβ€”chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content β†’ the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger β†’ Download File From Google Download File From Google β†’ Extract from File β†’ Update File to One Drive Extract from File β†’ Message a model Message a model β†’ Create or update an account Create or update an account β†’ Create an opportunity Create an opportunity β†’ Build SOQL Build SOQL β†’ Query PricebookEntries Query PricebookEntries β†’ Code in JavaScript Code in JavaScript β†’ Create Opportunity Line Items --- Quick setup checklist πŸ” Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. πŸ“‚ IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name β†’ Account upsert fields Invoice code/date/amount β†’ Opportunity fields Product name must equal your Product2.ProductCode in SF. βœ… Test: Drop a sample PDF β†’ verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep β€œReturn only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942