Back to Catalog

WooCommerce ๐Ÿ›’ Product Review Sentiment Analysis and AI Report ๐Ÿค– for Improvement

DavideDavide
19 views
2/3/2026
Official Page

This workflow automates the end-to-end analysis of WooCommerce product reviews, transforming raw customer feedback into actionable product and customer-care insights, and delivering them in a structured, visual, and shareable format.

This workflow analyzes product review sentiment from WooCommerce using AI. It starts by retrieving reviews for a specified product via the WooCommerce.

Each review then undergoes sentiment analysis using LangChain's Sentiment Analysis. The workflow aggregates sentiment data, creates a pie chart visualization via QuickChart, and compiles a comprehensive report using an AI Agent.

The report includes executive summaries, quantitative data, qualitative analysis, product diagnostics, and operational recommendations. Finally, the AI-generated report is converted to HTML and emailed to a designated recipient for review by customer and product teams.


Key Advantages

1. โœ… Full Automation of Review Analysis

Eliminates manual work by automating data collection, sentiment analysis, reporting, visualization, and delivery in a single workflow.

2. โœ… Scalable and Reliable

Batch processing ensures the workflow can handle dozens or hundreds of reviews without performance issues.

3. โœ… Action-Oriented Insights (Not Just Sentiment)

Instead of stopping at sentiment scores, the workflow produces:

  • Root-cause hypotheses
  • Concrete improvement actions
  • Prioritized recommendations (P0 / P1 / P2)
  • Measurable KPIs

4. โœ… Combines Quantitative and Qualitative Analysis

Merges hard metrics (averages, distributions, outliers) with qualitative insights (themes, risks, opportunities), giving a 360ยฐ view of customer feedback.

5. โœ… Visual + Narrative Output

Stakeholders receive both:

  • Visual sentiment charts for quick understanding
  • Structured written reports for strategic decision-making

6. โœ… Ready for Product & Customer Care Teams

The output format is tailored for non-technical teams:

  • Clear language
  • Masked personal data (GDPR-friendly)
  • Immediate usability in meetings, emails, or documentation

7. โœ… Easily Extensible

The workflow can be extended to:

  • Run on a schedule
  • Analyze multiple products
  • Store results in a database or CRM
  • Trigger alerts for negative sentiment spikes

Ideal Use Cases

  • Continuous monitoring of product sentiment
  • Supporting product roadmap decisions
  • Identifying customer pain points early
  • Improving customer support response strategies
  • Reporting customer voice to stakeholders automatically

How it works

  1. Manual Trigger & Configuration The workflow starts manually and sets the target WooCommerce product ID and store URL.

  2. Data Retrieval from WooCommerce

    • Fetches all reviews for the selected product via the WooCommerce REST API.
    • Retrieves product details (name, description, categories) to enrich the analysis context.
  3. Batch Processing of Reviews Reviews are processed in batches to ensure scalability and reliability, even with a large number of reviews.

  4. AI-Powered Sentiment Analysis

    • Each review is analyzed using an OpenAI-based sentiment analysis model.

    • For every review, the workflow extracts:

      • Sentiment category (Positive / Negative / Neutral)
      • Strength (intensity)
      • Confidence (reliability of the classification)
  5. Data Normalization & Aggregation

    • Review text is cleaned and structured.
    • Sentiment data is aggregated to compute overall distributions and metrics.
  6. Visual Sentiment Distribution

    • A pie chart is dynamically generated via QuickChart to visually represent sentiment distribution.
  7. Advanced AI Insight Generation A specialized AI agent (โ€œProduct Insights Analystโ€) transforms the raw and aggregated data into a professional, structured report, including:

    • Executive summary
    • Quantitative statistics
    • Qualitative themes
    • Product diagnosis
    • Operational recommendations
    • Product backlog ideas
    • Next steps
  8. HTML Conversion & Delivery

    • The report is converted into clean HTML.
    • The final output is automatically sent via email to stakeholders (e.g. product or customer care teams).

Set up steps

  1. Configure credentials:

    • Set up WooCommerce API credentials in the HTTP Request node.
    • Add OpenAI API credentials for both sentiment analysis and reporting.
    • Configure Gmail OAuth2 credentials for sending the final email report.
  2. Set parameters:

    • In the "Product ID" node, replace PRODUCT_ID and YOUR_WEBSITE with actual product ID and WooCommerce site URL.
    • Update the recipient email address in the "Send a message" node.
  3. Optional adjustments:

    • Modify the pie chart design in the "QuichChart" node if needed.
    • Adjust the report structure or language in the "Product Insights Analyst" system prompt.
  4. Run the workflow:

    • Click "Execute workflow" on the manual trigger to start the process.
    • Monitor execution in n8n to ensure all nodes process correctly.

Once configured, the workflow will automatically analyze product reviews, generate insights, and deliver a formatted report via email.


๐Ÿ‘‰ Subscribe to my new YouTube channel. Here Iโ€™ll share videos and Shorts with practical tutorials and FREE templates for n8n.

image


Need help customizing?

Contact me for consulting and support or add me on Linkedin.

WooCommerce Product Review Sentiment Analysis and AI Report

This n8n workflow automates the process of fetching WooCommerce product reviews, analyzing their sentiment using AI, and generating a comprehensive report for product improvement. It then sends this report via email.

What it does

This workflow simplifies and automates the following steps:

  1. Triggers Manually: The workflow starts when manually executed.
  2. Fetches Product Reviews: It retrieves all product reviews from your WooCommerce store.
  3. Prepares Review Data: It transforms the raw review data into a format suitable for AI processing, focusing on the review content.
  4. Analyzes Sentiment: For each review, it performs sentiment analysis using an AI model to determine if the review is positive, negative, or neutral.
  5. Aggregates Sentiment Results: It collects all sentiment analysis results.
  6. Generates AI Report: It uses an AI agent to create a detailed report based on the product reviews and their sentiments, identifying areas for improvement.
  7. Sends Email Report: The generated AI report is sent to a specified email address using Gmail.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • WooCommerce Account: Access to your WooCommerce store with API credentials (Consumer Key and Consumer Secret) configured in n8n.
  • OpenAI API Key: An OpenAI API key configured as a credential in n8n for the AI Agent and Chat Model.
  • Gmail Account: A Gmail account configured as a credential in n8n to send the reports.

Setup/Usage

  1. Import the Workflow:

    • Download the provided JSON file.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the three dots in the top right corner and select "Import from JSON".
    • Paste the workflow JSON or upload the file.
  2. Configure Credentials:

    • WooCommerce: Update the "WooCommerce" node with your WooCommerce API credentials.
    • OpenAI: Ensure your OpenAI API key is configured in n8n and linked to the "OpenAI Chat Model" and "AI Agent" nodes.
    • Gmail: Configure your Gmail account credentials in n8n and link them to the "Gmail" node. You will need to specify the recipient email address in the Gmail node's settings.
  3. Customize (Optional):

    • Edit Fields: The "Edit Fields" node prepares the review text for sentiment analysis. You might adjust this if your review structure differs or if you want to include other review aspects.
    • AI Agent Prompt: The "AI Agent" node's prompt can be customized to refine the generated report's focus and detail.
    • Gmail Recipient: Change the "To" email address in the "Gmail" node to send the report to the desired recipient.
  4. Execute the Workflow:

    • Click the "Execute Workflow" button (the play icon) on the "Manual Trigger" node to run the workflow manually.
    • For continuous monitoring, you could replace the "Manual Trigger" with a "Cron" node to run it on a schedule (e.g., daily, weekly).

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