HumationHuman + Automation
Back to Catalog

Analyze & summarize Amazon product reviews with Decodo, OpenAI and Google Sheets

Ranjan DailataRanjan Dailata
410 views
2/3/2026
Lead ManagementFormstackWebhookSalesforceCRM
Official Page

Disclaimer

Please note - This workflow is only available on n8n self-hosted as it’s making use of the community node for the Decodo Web Scraping

Analyze & Summarize Amazon Product Reviews with Decodo, OpenAI and Google Sheets

This n8n workflow automates the process of scraping, analyzing, and summarizing Amazon product reviews using Decodo’s Amazon Scraper, OpenAI GPT-4.1-mini, and Google Sheets for seamless reporting.

It turns messy, unstructured customer feedback into actionable product insights — all without manual review reading.

Who this is for

This workflow is designed for:

  • E-commerce product managers who need consolidated insights from hundreds of reviews.
  • Brand analysts and marketing teams performing sentiment or trend tracking.
  • AI and data engineers building automated review intelligence pipelines.
  • Sellers and D2C founders who want to monitor customer satisfaction and pain points.
  • Product researchers performing market comparison or competitive analysis.

What problem this workflow solves

Reading and analyzing hundreds or thousands of Amazon reviews manually is inefficient and subjective.

This workflow automates the entire process — from data collection to AI summarization — enabling teams to instantly identify customer pain points, trends, and strengths.

Specifically, it:

  • Eliminates manual review extraction from product pages.
  • Generates comprehensive and abstract summaries using GPT-4.1-mini.
  • Centralizes structured insights into Google Sheets for visualization or sharing.
  • Helps track product sentiment and emerging issues over time.

What this workflow does

Here’s a breakdown of the automation process:

  1. Set Input Fields Define your Amazon product URL, geo region, and desired file name.

  2. Decodo Amazon Scraper Fetches real-time product reviews from the Amazon product page, including star ratings and AI-generated summaries.

  3. Extract Reviews Node Extracts raw customer reviews and Decodo’s AI summary into a structured JSON format.

  4. Perform Review Analysis (GPT-4.1-mini) Uses OpenAI GPT-4.1-mini to create two key summaries:

    • Comprehensive Review: A detailed summary that captures sentiment, recurring themes, and product pros/cons.
    • Abstract Review: A concise executive summary that captures the overall essence of user feedback.

  5. Persist Structured JSON Saves the raw and AI-enriched data to a local file for reference.

  6. Append to Google Sheets Uploads both the original reviews and AI summaries into a Google Sheet for ongoing analysis, reporting, or dashboard integration.

Outcome: You get a structured, AI-enriched dataset of Amazon product reviews — summarized, searchable, and easy to visualize.

Setup

Pre-requisite

If you are new to Decode, please signup on this link visit.decodo.com

Please make sure to install the n8n custom node for Decodo.

Install Decodo Community Node

Decodo Community Node

Step 1 — Import the Workflow

  1. Open n8n and import the JSON workflow template.

  2. Ensure the following credentials are configured:

    • Decodo Credentials account → Decodo API Key
    • OpenAI account → OpenAI API Key
    • Google Sheets account → Connected via OAuth

Step 2 — Input Product Details

In the Set node, replace:

  • amazon_url → your product link (e.g., https://www.amazon.com/dp/B0BVM1PSYN)
  • geo → your region (e.g., US, India)
  • file_name → output file name (optional)

Step 3 — Connect Google Sheets

Link your desired Google Sheet for data storage. Ensure the sheet columns match:

  • product_reviews
  • all_reviews

Step 4 — Run the Workflow

Click Execute Workflow. Within seconds, your Amazon product reviews will be fetched, summarized by AI, and logged into Google Sheets.

How to customize this workflow

You can tailor this workflow for different use cases:

  • Add Sentiment Analysis — Add another GPT node to classify reviews as positive, neutral, or negative.
  • Multi-Language Reviews — Include a language detection node before summarization.
  • Send Alerts — Add a Slack or Gmail node to notify when negative sentiment exceeds a threshold.
  • Store in Database — Replace Google Sheets with MySQL, Postgres, or Notion nodes.
  • Visualization Layer — Connect your Google Sheet to Looker Studio or Power BI for dynamic dashboards.
  • Alternative AI Models — Swap GPT-4.1-mini with Gemini 1.5 Pro, Claude 3, or Mistral for experimentation.

Summary

This workflow transforms the tedious process of reading hundreds of Amazon reviews into a streamlined AI-powered insight engine.

By combining Decodo’s scraping precision, OpenAI’s summarization power, and Google Sheets’ accessibility, it enables continuous review monitoring.

In one click, it delivers comprehensive and abstract AI summaries, ready for your next product decision meeting or market strategy session.

n8n Workflow: Analyze and Summarize Amazon Product Reviews

This n8n workflow demonstrates a powerful way to process and extract insights from Amazon product reviews using AI. It leverages an Information Extractor to structure review data and an OpenAI Chat Model to generate summaries, with the results stored in Google Sheets.

What it does

This workflow performs the following key steps:

  1. Manual Trigger: The workflow is initiated manually, allowing you to control when the analysis begins.
  2. Read/Write Files from Disk: This node is present in the workflow, indicating a potential step for reading review data from a local file. However, without further configuration details, its exact role in fetching Amazon reviews is not fully defined in the provided JSON.
  3. Code (Prepare Data): A Code node is used, likely to transform or prepare the raw review data into a format suitable for the subsequent AI processing.
  4. Information Extractor (Decodable AI): This node uses an AI model (likely from Decodable AI, given the directory name context) to extract structured information from the product reviews. This could include aspects like sentiment, key features mentioned, common complaints, etc.
  5. OpenAI Chat Model (Summarize): The extracted information or the original review text is then fed into an OpenAI Chat Model to generate concise summaries of the product reviews.
  6. Function (Process Summaries): Another Function node is used, likely to further process or format the AI-generated summaries before they are stored.
  7. Edit Fields (Set): A Set node is used to manipulate or set specific fields in the data, ensuring it's in the correct structure for Google Sheets.
  8. Google Sheets (Write Data): Finally, the processed and summarized review data is written to a Google Sheet, providing an organized and accessible repository for the insights.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • OpenAI API Key: For the OpenAI Chat Model to generate summaries.
  • Google Account: With access to Google Sheets to store the results.
  • Decodable AI (or similar Information Extractor service): The workflow utilizes an "Information Extractor" node, which, based on the directory name, suggests integration with a service like Decodable AI for structured data extraction. You will need credentials or access to such a service.
  • Review Data: A source of Amazon product reviews, potentially in a file format that the "Read/Write Files from Disk" node can access.

Setup/Usage

  1. Import the Workflow: Download the workflow JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your OpenAI credentials for the "OpenAI Chat Model" node.
    • Set up your Google Sheets credentials for the "Google Sheets" node.
    • Configure any necessary credentials for the "Information Extractor" node (e.g., Decodable AI API key).
  3. Configure Nodes:
    • Read/Write Files from Disk: Specify the path to your Amazon product review data file.
    • Code (Prepare Data): Review and adjust the JavaScript code to correctly parse and prepare your specific review data format.
    • Information Extractor: Configure the schema or prompts for the information you want to extract from the reviews.
    • OpenAI Chat Model: Adjust the prompt for summarization as needed (e.g., "Summarize the following product review:").
    • Function (Process Summaries): Adjust the JavaScript code if further processing of summaries is required.
    • Edit Fields (Set): Ensure the fields are correctly mapped to your Google Sheet columns.
    • Google Sheets: Specify the Spreadsheet ID and Sheet Name where the data should be written.
  4. Execute the Workflow: Click "Execute Workflow" on the "Manual Trigger" node to run the analysis.

Related Templates

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 Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616