Back to Catalog

Extract Amazon product data with Scrape.do, GPT-4 & Google Sheets

OnurOnur
675 views
2/3/2026
Official Page

Amazon Product Scraper with Scrape.do & AI Enrichment

> This workflow is a fully automated Amazon product data extraction engine. It reads product URLs from a Google Sheet, uses Scrape.do to reliably fetch each product page’s HTML without getting blocked, and then applies an AI-powered extraction process to capture key product details such as name, price, rating, review count, and description. All structured results are neatly stored back into a Google Sheet for easy access and analysis.

This template is designed for consistency and scalability—ideal for marketers, analysts, and e-commerce professionals who need clean product data at scale.


🚀 What does this workflow do?

  • Reads Input URLs: Pulls a list of Amazon product URLs from a Google Sheet.
  • Scrapes HTML Reliably: Uses Scrape.do to bypass Amazon’s anti-bot measures, ensuring the page HTML is always retrieved successfully.
  • Cleans & Pre-processes HTML: Strips scripts, styles, and unnecessary markup, isolating only relevant sections like title, price, ratings, and feature bullets.
  • AI-Powered Data Extraction: A LangChain/OpenRouter GPT-4 node verifies and enriches key fields—product name, price, rating, reviews, and description.
  • Stores Structured Results: Appends all extracted and verified product data to a results tab in Google Sheets.
  • Batch & Loop Control: Handles multiple URLs efficiently with Split In Batches to process as many products as you need.

🎯 Who is this for?

  • E-commerce Sellers & Dropshippers: Track competitor prices, ratings, and key product features automatically.
  • Marketing & SEO Teams: Collect product descriptions and reviews to optimize campaigns and content.
  • Analysts & Data Teams: Build accurate product databases without manual copy-paste work.

✨ Benefits

  • High Success Rate: Scrape.do handles proxy rotation and CAPTCHA challenges automatically, outperforming traditional scrapers.
  • AI Validation: LLM verification ensures data accuracy and fills in gaps when HTML elements vary.
  • Full Automation: Runs on-demand or on a schedule to keep product datasets fresh.
  • Clean Output: Results are neatly organized in Google Sheets, ready for reporting or integration with other tools.

⚙️ How it Works

  1. Manual or Scheduled Trigger: Start the workflow manually or via a cron schedule.
  2. Input Source: Fetch URLs from a Google Sheet (TRACK_SHEET_GID).
  3. Scrape with Scrape.do: Retrieve full HTML from each Amazon product page using your SCRAPEDO_TOKEN.
  4. Clean & Pre-Extract: Strip irrelevant code and use regex to pre-extract key fields.
  5. AI Extraction & Verification: LangChain GPT-4 model refines and validates product name, description, price, rating, and reviews.
  6. Save Results: Append enriched product data to the results sheet (RESULTS_SHEET_GID).

📋 n8n Nodes Used

  • Manual Trigger / Schedule Trigger
  • Google Sheets (read & append)
  • Split In Batches
  • HTTP Request (Scrape.do)
  • Code (clean & pre-extract HTML)
  • LangChain LLM (OpenRouter GPT-4)
  • Structured Output Parser

🔑 Prerequisites

  • Active n8n instance.
  • Scrape.do API token (bypasses Amazon anti-bot measures).
  • Google Sheets with:
    • TRACK_SHEET_GID: tab containing product URLs.
    • RESULTS_SHEET_GID: tab for results.
  • Google Sheets OAuth2 credentials shared with your service account.
  • OpenRouter / OpenAI API credentials for the GPT-4 model.

🛠️ Setup

  1. Import the Workflow into your n8n instance.
  2. Set Workflow Variables:
    • SCRAPEDO_TOKEN – your Scrape.do API key.
    • WEB_SHEET_ID – Google Sheet ID.
    • TRACK_SHEET_GID – sheet/tab name for input URLs.
    • RESULTS_SHEET_GID – sheet/tab name for results.
  3. Configure Credentials for Google Sheets and OpenRouter.
  4. Map Columns in the “add results” node to match your Google Sheet (e.g., name, price, rating, reviews, description).
  5. Run or Schedule: Start manually or configure a schedule for continuous data extraction.

This Amazon Product Scraper delivers fast, reliable, and AI-enriched product data, ensuring your e-commerce analytics, pricing strategies, or market research stay accurate and fully automated.

Extract Amazon Product Data with Scraped HTML using GPT-4 and Google Sheets

This n8n workflow automates the process of extracting structured product data from Amazon product pages (provided as HTML), enriching it with GPT-4, and then storing the results in Google Sheets. It's designed to streamline data collection for market research, competitor analysis, or inventory management.

What it does

  1. Triggers Manually: The workflow starts when you manually execute it within n8n.
  2. Reads HTML Input: It expects HTML content (likely from an Amazon product page) as input.
  3. Extracts Product Details (HTML): Uses an HTML node to parse the provided HTML and extract specific product information (e.g., product title, price, description).
  4. Splits Data for Processing: If multiple items are processed, it splits them into individual batches for iterative handling.
  5. Enriches Data with GPT-4: For each product, it uses a LangChain Basic LLM Chain with an OpenAI Chat Model and a Structured Output Parser to intelligently extract and structure specific product attributes (e.g., features, specifications, benefits) from the raw HTML or previously extracted data. This leverages the advanced understanding capabilities of GPT-4.
  6. Saves to Google Sheets: Finally, it appends the extracted and enriched product data to a specified Google Sheet.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • OpenAI API Key: An API key for OpenAI, with access to GPT-4 models, configured as an n8n credential.
  • Google Sheets Account: A Google account with access to Google Sheets, configured as an n8n credential.
  • Amazon Product HTML: The workflow expects raw HTML content of Amazon product pages as input. This typically comes from a previous step (e.g., an HTTP Request node for scraping, or manual input for testing).
  • Scraped Amazon Product Data: The workflow assumes you have a method to obtain the raw HTML of Amazon product pages. While this workflow processes the HTML, it doesn't scrape it directly. An HTTP Request node is present, but not connected as a primary data source in the provided JSON, suggesting it might be used for testing or an alternative input path.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the workflow JSON.
  2. Configure Credentials:
    • OpenAI Chat Model: Click on the "OpenAI Chat Model" node. Select or create an "OpenAI API" credential. Ensure it has access to the models you intend to use (e.g., gpt-4).
    • Google Sheets: Click on the "Google Sheets" node. Select or create a "Google Sheets" credential. Grant it the necessary permissions to write to your desired spreadsheet.
  3. Configure Nodes:
    • HTML (Extract Product Details): Review the CSS selectors in this node to ensure they correctly target the product title, description, and other elements you wish to extract from the Amazon HTML. You may need to adjust these based on Amazon's current HTML structure.
    • Basic LLM Chain:
      • Prompt: Adjust the prompt within this node to guide GPT-4 on what specific information to extract and how to structure it.
      • Output Parser: Review the schema in the "Structured Output Parser" node. This defines the JSON structure that GPT-4 should return. Modify it to match the exact fields you want to extract (e.g., product_name, price, features_list, category).
    • Google Sheets:
      • Spreadsheet ID: Enter the ID of your Google Sheet.
      • Sheet Name: Specify the name of the sheet within the spreadsheet where data should be appended.
      • Column Mapping: Ensure the column mapping aligns with the output from the Basic LLM Chain and the columns in your Google Sheet.
  4. Provide Input HTML:
    • For testing, you can manually input sample Amazon product HTML into the first node (e.g., using a "Set" node before the "HTML" node, or by directly pasting it into the "HTTP Request" node if you configure it to accept static data).
    • For live use, you would typically connect a preceding node (e.g., an HTTP Request node configured to scrape an Amazon URL, or a Webhook receiving HTML) to feed the Amazon product page HTML into the "HTML" node.
  5. Execute the Workflow: Click "Execute Workflow" to run it. Observe the output at each step to ensure data is being processed as expected.

This workflow provides a powerful foundation for automating product data extraction and enrichment, leveraging the capabilities of large language models for intelligent data structuring.

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