Amazon to Google Sheets, purchase trends you can use
Copying Amazon product details into a spreadsheet sounds simple, until you’ve done it 30 times in a row and realized half your “insights” are just notes you forgot to standardize.
This Amazon Sheets automation hits marketing managers first (campaign timing needs real signals), but e-commerce operators and product researchers feel it too. You get consistent, searchable purchase-trend insights without spending your week squinting at listings.
This workflow pulls Amazon links from Google Sheets, uses AI to analyze each listing, then writes structured “purchase signals” back into the same sheet. You’ll see how it works, what you need, and what to watch out for.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Amazon to Google Sheets, purchase trends you can use
flowchart LR
subgraph sg0["When clicking ‘Execute workflow’ Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Execute workf..", pos: "b", h: 48 }
n1@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
n2@{ icon: "mdi:database", form: "rounded", label: "Fetch Amazon URLs from Googl..", pos: "b", h: 48 }
n3@{ icon: "mdi:robot", form: "rounded", label: "Amazon Product Analyzer (AI ..", pos: "b", h: 48 }
n4@{ icon: "mdi:cog", form: "rounded", label: "Tool: MCP Client (Bright Data)", pos: "b", h: 48 }
n5@{ icon: "mdi:database", form: "rounded", label: "Update Sheet with Product In..", pos: "b", h: 48 }
n6@{ icon: "mdi:robot", form: "rounded", label: "Auto-fixing Output Parser", pos: "b", h: 48 }
n7@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model1", pos: "b", h: 48 }
n8@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser", pos: "b", h: 48 }
n1 -.-> n3
n7 -.-> n6
n8 -.-> n6
n6 -.-> n3
n4 -.-> n3
n3 --> n5
n2 --> n3
n0 --> n2
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 n3,n6,n8 ai
class n1,n7 aiModel
class n2,n5 database
The Problem: Amazon research is messy, slow, and hard to reuse
Amazon research tends to start with good intentions and end with a chaotic spreadsheet. One person pastes links, another adds notes, and a third tries to “summarize” what matters for demand, seasonality, or customer preferences. A week later, you can’t remember why a product looked promising, or what pattern you thought you saw. Worse, you can’t compare apples to apples because everyone captured different fields. The time cost is obvious. The opportunity cost is bigger, because inconsistent research leads to cautious decisions and missed launches.
It adds up fast. Here’s where it breaks down once you’re doing this regularly.
- Manually reviewing 20 listings can eat about 2 hours, and that’s before you’ve turned notes into actual decisions.
- Your “insights” end up trapped in freeform text, which means you can’t filter or trend them later.
- Small errors creep in (wrong ASIN, wrong variation, outdated price), and the spreadsheet becomes untrustworthy.
- Teams redo the same analysis because they can’t find the original rationale or supporting signals.
The Solution: Turn Amazon listings into structured purchase-trend insights
This n8n workflow gives you a repeatable way to analyze Amazon listings and store the results in Google Sheets in a format you can actually use. You start with a simple input: a list of Amazon links in a spreadsheet. When you run the workflow, it picks up those links, pulls the relevant page data through a scraping layer (so you’re less likely to get blocked), and passes that information into an AI analyst. The AI doesn’t just “summarize” the listing. It tries to extract purchase signals and consumer behavior patterns you can compare across products, like seasonal hints, positioning cues, likely audiences, and differentiators. Finally, it writes the structured insights back into Google Sheets, so your research stays searchable and consistent.
The flow starts with a manual trigger inside n8n. Next, Google Sheets provides the queue of Amazon URLs to analyze. The AI agent then generates a structured output, and the workflow saves those fields back into your sheet, ready for filtering, tagging, and planning.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you review 25 Amazon listings every Monday to plan promos and content angles. Manually, even 6 minutes per listing to open tabs, skim, capture notes, and paste into a sheet is about 2.5 hours, and the notes still won’t match from one product to the next. With this workflow, you paste the 25 links into Google Sheets, run the manual trigger, and wait for the AI analysis to populate structured fields. You spend maybe 10 minutes queueing links and scanning the output, not half a morning doing repetitive capture.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets for storing links and insights
- Bright Data to scrape listing data reliably
- OpenAI API key (get it from your OpenAI dashboard)
Skill level: Intermediate. You’ll connect accounts, add credentials, and map a few sheet columns.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
You launch it on demand. A manual trigger starts the run, which is useful when you want to analyze a fresh batch of links (not drip-feed results all day).
Your sheet becomes the queue. The workflow reads Amazon URLs from Google Sheets, so your team can add links anytime without touching n8n.
AI analyzes each listing using scraped page data. Bright Data helps retrieve the content, then the AI agent produces structured fields. Behind the scenes, output parsers clean and standardize the response so the results are easier to trust.
Insights are written back into Google Sheets. That means you can filter by trend, tag opportunities, and share a single “source of research” across marketing and ops.
You can easily modify the analysis fields to match your category (beauty, electronics, home goods) based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
This workflow starts manually and then pulls Amazon product URLs from Google Sheets for analysis.
- Add the Manual Launch Trigger node as the workflow entry point.
- Confirm Manual Launch Trigger has no parameters to configure.
- Connect Manual Launch Trigger to Retrieve Amazon Links.
Step 2: Connect Google Sheets
Retrieve product URLs and update the same sheet with analyzed insights.
- Open Retrieve Amazon Links and select your spreadsheet for Document ID using the list picker.
- Set Sheet Name to
gid=0(cached asSheet1). - Credential Required: Connect your googleSheetsOAuth2Api credentials in Retrieve Amazon Links.
- Open Write Insights to Sheet and select the same Document ID and Sheet Name
gid=0. - Credential Required: Connect your googleSheetsOAuth2Api credentials in Write Insights to Sheet.
Step 3: Set Up AI Analysis and Parsing
The AI agent analyzes each Amazon URL using OpenAI and a web data tool, then parses results into structured output.
- Open Amazon Listing AI Analyst and set Text to
=extract the unit sold, current price, stock availability, review count & rating, sales rank and based on it's purchasing performance give it rating out of 10. Below is the url of the amazon product: {{ $json.url }}. - Confirm Prompt Type is set to define and hasOutputParser is enabled.
- Open OpenAI Dialogue Model and select the model
gpt-4o-mini. - Credential Required: Connect your openAiApi credentials in OpenAI Dialogue Model.
- Open Web Data MCP Tool and set Tool Name to
web_data_amazon_productand Operation toexecuteTool. - Set Tool Parameters to
={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Tool_Parameters', ``, 'json') }}. - Credential Required: Connect your mcpClientApi credentials in Web Data MCP Tool.
- Confirm Auto Repair Output Parser is connected to Structured Data Parser and uses Secondary Chat Model for auto-fixing.
- Credential Required: Connect your openAiApi credentials in Secondary Chat Model.
Step 4: Configure the Output Mapping
Map parsed AI output fields back to the spreadsheet row that supplied each URL.
- Open Write Insights to Sheet and keep Operation set to
update. - In Columns, map Ranking to
={{ $json.output[0].performance_rating }}. - Map Sales rank to
={{ $json.output[0].sales_rank }}and Units sold to={{ $json.output[0].units_sold_last_month }}. - Map Current price to
={{ $json.output[0].current_price }}and Stock availability to={{ $json.output[0].stock_status }}. - Map Review count & rating to
={{ $json.output[0].review_count }} & {{ $json.output[0].rating }}. - Set the match field row_number to
={{ $('Retrieve Amazon Links').item.json.row_number }}.
$json.output[0].current_price may return empty values.Step 5: Test and Activate Your Workflow
Run a manual test to verify the end-to-end flow before enabling it for regular use.
- Click Execute Workflow to run Manual Launch Trigger.
- Verify Retrieve Amazon Links outputs rows containing a url field and row_number.
- Confirm Amazon Listing AI Analyst produces a structured output array with pricing, stock, and rating fields.
- Check your Google Sheet to confirm Write Insights to Sheet updates the matching row with the new values.
- Toggle the workflow to Active once the test run completes successfully.
Common Gotchas
- Google Sheets credentials can expire or need specific permissions. If things break, check the n8n Credentials page and confirm the connected Google account still has access to the target spreadsheet.
- If you’re using Wait nodes or external scraping, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice and your definition of “purchase signals” early or you’ll be editing outputs forever.
Frequently Asked Questions
About 30–60 minutes if your credentials are ready.
No. You will connect accounts and map your sheet columns once.
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 OpenAI API usage and Bright Data costs, which depend on how many listings you analyze.
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, but you’ll want to do it deliberately. The easiest lever is the prompt used by the Amazon Listing AI Analyst, because that’s where you define what “purchase signals” mean for your niche (giftability, repeat purchase likelihood, compliance risks, or whatever matters). You can also adjust the Structured Data Parser fields to match the exact columns you want in Google Sheets. Many teams add a simple “category” column in the input sheet so the AI can adapt its analysis per row.
Usually it’s an expired Google authorization or the wrong Google account attached in n8n. Reconnect the Google Sheets credential, then confirm the spreadsheet is shared with that account and that the sheet/tab name matches what the node expects. If it still fails, check if the file was moved into a Shared Drive with stricter permissions.
If you self-host n8n, there’s no execution cap beyond your server and scraping/API limits. Practically, most teams run batches of 20–100 listings at a time so the sheet stays readable and you don’t hit rate limits.
Often, yes. This workflow depends on an AI agent plus structured output parsing, and n8n is simply more comfortable with that kind of multi-step logic. You also get the option to self-host, which matters when you’re processing lots of listings and don’t want to pay per tiny step. Zapier or Make can still work if you only need lightweight enrichment and you’re fine with simpler formatting. If you’re unsure, Talk to an automation expert and you’ll get a straight recommendation.
Once this is in place, your Amazon research stops being a one-off chore and turns into an asset you can build on. The workflow handles the repetitive capture so you can spend your time making the call.
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.
