Templates / Extract ecommerce product data with Google Sheets, ScrapingBee and Gemini

Extract ecommerce product data with Google Sheets, ScrapingBee and Gemini

Needs changes

by Ravi Patel ✓ · 28 views · created 2026-06-15 · Market Research, AI RAG

Needs changes. This template uses 1 thing(s) that n8n 3.0 removes: AI Agent v1 (old agent modes). 1 breaking item(s) found. Static check, last run 2026-10-19.

What to replace before upgrading

Removed in 3.0Replace with
AI Agent v1 (old agent modes)
Vision-based Scraping Agent (v1.7)
Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.

Nodes used (11)

Structured Output ParserGoogle Gemini Chat ModelGoogle SheetsCall n8n WorkflowAI Agent

What it does

Quick Overview This workflow manually runs to read a list of webpage URLs from Google Sheets, scrape each page with ScrapingBee, and use Google Gemini to extract structured product data from screenshots with an HTML fallback, then append the results back into a Google Sheets sheet. How it works 1. Runs when you manually trigger the workflow. 2. Reads the list of URLs to scrape from a Google Sheets spreadsheet. 3. Fetches a full-page screenshot for each URL using the ScrapingBee API. 4. Sends the screenshot (and the URL for context) to a Google Gemini model to extract product details into a structured JSON format, calling a ScrapingBee HTML fetch tool when screenshot extraction is incomplete. 5. Converts any fetched HTML to Markdown and returns it to the Gemini agent to complete the extraction. 6. Splits the extracted product array into individual items and appends them as new rows in the Google Sheets “Results” sheet. Setup 1. Create a Google Sheets service account connection in n8n and set the target spreadsheet and the “List of URLs” and “Results” sheet selections. 2. Add a Google Gemini (PaLM) API credential in n8n and ensure the selected model (gemini-1.5-pro-latest) is available for your account. 3. Add your ScrapingBee API key in both ScrapingBee HTTP requests (screenshot and HTML) and confirm the target URLs are reachable from your n8n environment. 4. Ensure the “Results” sheet columns match the structured output fields (for example: producttitle, productprice, productbrand, promo, promopercentage/promopercent) or update the output schema and column mappings accordingly.

View the original on n8n.io → Check your own copy

Get the weekly “what broke” email

New templates, newly broken ones, and n8n release changes. One short email a week.

Form not loading? Subscribe here.