ScrapeGraphAI to Google Sheets, Amazon data ready
Competitor tracking on Amazon sounds simple until you do it for real. Tabs multiply, listings change overnight, and your “quick check” turns into an hour of copy-paste and second-guessing.
E-commerce analysts feel it first. A product manager trying to defend positioning does too. Even a business owner keeping an eye on “best sellers” ends up stuck in spreadsheet cleanup. This Amazon Sheets scraping automation keeps your Amazon keyboard listings flowing into one clean Google Sheet.
You’ll set up an n8n workflow that scrapes Amazon search results with ScrapeGraphAI, formats the data consistently, and appends it to Google Sheets so you can spot changes faster.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: ScrapeGraphAI to Google Sheets, Amazon data ready
flowchart LR
subgraph sg0["Automated Schedule Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Automated Schedule Trigger", pos: "b", h: 48 }
n1@{ icon: "mdi:cog", form: "rounded", label: "AI-Powered Amazon Product Sc..", pos: "b", h: 48 }
n2@{ icon: "mdi:database", form: "rounded", label: "Google Sheets Data Storage", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Data Formatting and Processing"]
n0 --> n1
n3 --> n2
n1 --> n3
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n2 database
class n3 code
classDef customIcon fill:none,stroke:none
class n3 customIcon
Why This Matters: Amazon listings change faster than your sheet
Amazon search pages are noisy and constantly shifting. A keyboard that was on page one yesterday might drop to page three today, a title gets tweaked, or a listing URL changes to a new variation. When you track this manually, you end up with messy rows, inconsistent naming, and “did I already log this one?” anxiety. The worst part is the hidden cost: you stop trusting the sheet, so you stop using it, and competitor monitoring becomes a vague gut feel instead of a repeatable routine.
It adds up fast. Here’s where it breaks down.
- You spend about 30–60 minutes per check just collecting listings and pasting them into the right columns.
- Small formatting differences make sorting and filtering unreliable, which means analysis takes longer than it should.
- URLs get missed or pasted incorrectly, so later you can’t confirm what product a row actually referred to.
- Because the work is tedious, checks happen less often, and you notice competitor moves after they’ve already mattered.
What You’ll Build: Amazon keyboard data piped into Google Sheets
This workflow runs on a schedule, so it quietly checks Amazon for keyboard listings without you remembering to do it. When it starts, ScrapeGraphAI visits your chosen Amazon search URL and extracts the product details you care about using an AI-guided prompt. n8n then takes that raw scrape output and cleans it up in a Code step so it fits your spreadsheet columns consistently. Finally, it appends each product as a new row in Google Sheets, creating a simple “source of truth” you can filter, sort, and chart. Over time, you get a living dataset that’s easy to compare week to week.
The workflow begins with a Scheduled Trigger, then ScrapeGraphAI extracts listings from your Amazon results page. After a quick formatting pass, Google Sheets receives clean rows (title, url, category) that are ready for tracking and reporting.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you track 40–50 keyboard listings every week. Manually, grabbing titles, URLs, and a category label is maybe 2 minutes per product plus cleanup time, so you’re looking at about 2 hours weekly once you include fixing messy rows. With this workflow, setup is roughly 15 minutes, and each scheduled run takes a few minutes of background processing while you do other work. Most weeks, your “time spent” becomes a quick 10-minute review of the sheet.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- ScrapeGraphAI for extracting Amazon search results.
- Google Sheets to store and review the dataset.
- ScrapeGraphAI API key (get it from your ScrapeGraphAI dashboard)
Skill level: Beginner. You’ll connect accounts, paste an API key, and tweak one Amazon URL.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
A schedule kicks things off. You choose how often to run it (daily, weekly, or something in between), and n8n starts the workflow automatically.
ScrapeGraphAI pulls the listings. The workflow visits your Amazon keyboard search URL and extracts structured fields from the results page using an AI prompt, which helps it handle messy page layouts more gracefully than brittle “CSS selector” scrapers.
The results get cleaned up. A Code step reshapes the output into a consistent format so Google Sheets receives the same column structure every time (title, url, category by default).
Google Sheets becomes the home base. The workflow appends new rows to your target spreadsheet, giving you an audit trail of what was found on each run.
You can easily modify the Amazon search URL to target different products based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Scheduled Trigger
Set the workflow to run on a schedule using the trigger node.
- Add and open Scheduled Run Launcher.
- Define the schedule in Rule based on your desired run frequency (e.g., hourly or daily).
- Keep Flowpast Branding as a visual note; no configuration is required.
Step 2: Connect Google Sheets
Prepare the spreadsheet destination for storing scraped product data.
- Open Append to Google Spreadsheet.
- Credential Required: Connect your googleSheetsOAuth2Api credentials.
- Set Operation to
append. - Set Sheet Name to
Sheet1. - Set Document ID to your Google Sheets URL in
Document ID(currently empty). - Confirm Columns are mapped with
title,url, andcategoryusing Auto-Map Input Data.
Step 3: Set Up AI Amazon Product Extraction
Configure the AI scraper to pull product data from Amazon search results.
- Open AI Amazon Product Extractor.
- Credential Required: Connect your scrapegraphAIApi credentials.
- Set Website URL to
https://www.amazon.com/s?k=keyboard&crid=2FI5OSSH1T0Q8&sprefix=keyboar%2Caps%2C191&ref=nb_sb_ss_p13n-pd-dpltr-ranker_ci_hl-bn-left_1_7. - Set User Prompt to
Extract all the products from this site. Use the following schema for response { "title": "Logitech MX Keys Advanced Wireless Illuminated Keyboard", "url": "https://www.amazon.com/dp/B07S92QBCX", "category": "Electronics" }. - Verify the node connection order: Scheduled Run Launcher → AI Amazon Product Extractor.
result.products array, adjust the prompt to clarify the expected structure.Step 4: Configure Output/Action Nodes
Process the extracted data into a structured array and append it to Google Sheets.
- Open Format & Process Results and confirm the JavaScript logic maps
title,url, andcategoryfrominputData.result.products. - Ensure the execution flow is AI Amazon Product Extractor → Format & Process Results → Append to Google Spreadsheet.
- Run a manual test to verify each output item matches the Google Sheets column IDs.
inputData.result.products is undefined, the code node will fail. Validate the scraper output before running large schedules.Step 5: Test and Activate Your Workflow
Confirm the workflow runs end-to-end and then enable it for scheduled operation.
- Click Execute Workflow to run a manual test from Scheduled Run Launcher.
- Check that AI Amazon Product Extractor returns products and Format & Process Results outputs structured items.
- Verify that rows are appended in Append to Google Spreadsheet with
title,url, andcategory. - Once confirmed, toggle the workflow to Active for production use.
Troubleshooting Tips
- ScrapeGraphAI credentials can expire or need specific permissions. If things break, check your ScrapeGraphAI dashboard and the API key stored in n8n Credentials first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Google Sheets OAuth permissions cause silent failures more often than you’d think. Reconnect the Google account, confirm access to the right spreadsheet, and make sure the Sheet name matches exactly.
Quick Answers
About 10–15 minutes if you already have your ScrapeGraphAI and Google credentials ready.
No. You can use the workflow as-is, and only tweak the Amazon URL and the fields you want.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in ScrapeGraphAI API usage based on how often you run the scraper.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s the whole point. Change the Amazon search URL inside the AI Amazon Product Extractor node to target a different query (brands, layouts, “mechanical keyboard”, and so on). If you want more columns like price, rating, or review count, update the extraction prompt in the ScrapeGraphAI step and then adjust the Format & Process Results code so your sheet receives those new fields. Many teams also switch Google Sheets from “append” to an upsert-style approach so repeated runs update the same product instead of creating duplicates.
Usually it’s an invalid or expired API key. Regenerate the key in ScrapeGraphAI, then update the credential in n8n and run a manual test. If it still fails, check that your n8n instance allows community nodes and that the ScrapeGraphAI node is installed and enabled.
It depends mostly on your ScrapeGraphAI plan and how many results you try to extract per run; for many setups, dozens of listings per scheduled run is a realistic starting point.
Often, yes. Scraping plus formatting usually needs more control than a simple “trigger → action” recipe, and n8n makes it easier to shape data before it hits your sheet. You also get the option to self-host for unlimited executions, which matters once you run this daily. Another practical perk is community nodes (like ScrapeGraphAI) that may not exist on other platforms. Zapier or Make can still be fine for lightweight monitoring, but if you want repeatable research runs with clean rows, n8n tends to be the calmer choice. Talk to an automation expert if you’re not sure which fits.
Once this is running, your spreadsheet stays current without you babysitting it. The workflow handles the repetitive stuff, and you get to spend your time actually interpreting the market.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
