Bright Data + Google Sheets: Amazon ranks logged
Checking Amazon Best Sellers manually sounds simple until you do it every day. Tabs multiply, screenshots pile up, and one missed detail (like a price drop or a sudden jump in reviews) throws off your whole read on the market.
This hits eCommerce analysts first, but product teams and growth marketers feel it too. With Amazon ranks automation, you can log best-seller positions, pricing, and ratings into a sheet without copy-paste or “did I already capture this?” second-guessing.
Below is the workflow that pulls the Amazon Electronics Best Sellers page via Bright Data, uses an AI model to turn messy page content into clean fields, and pushes the result into a webhook so you can store it in Google Sheets (or anything else).
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Bright Data + Google Sheets: Amazon ranks logged
flowchart LR
subgraph sg0["When clicking ‘Test workflow’ Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Test workflow’", pos: "b", h: 48 }
n1@{ icon: "mdi:brain", form: "rounded", label: "Google Gemini Chat Model", pos: "b", h: 48 }
n2["<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/httprequest.dark.svg' width='40' height='40' /></div><br/>HTTP Request to fetch the Am.."]
n3@{ icon: "mdi:robot", form: "rounded", label: "Structured Data Extractor", pos: "b", h: 48 }
n4@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Amazon URL with the Brig..", pos: "b", h: 48 }
n5["<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/httprequest.dark.svg' width='40' height='40' /></div><br/>Webhook Notifier for structu.."]
n1 -.-> n3
n3 --> n5
n0 --> n4
n4 --> n2
n2 --> 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 n3 ai
class n1 aiModel
class n2,n5 api
classDef customIcon fill:none,stroke:none
class n2,n5 customIcon
The Problem: Amazon Best Seller Tracking Becomes a Time Sink
Amazon’s Best Sellers lists are useful because they change constantly. That’s also what makes them annoying. If you’re tracking rank shifts, price movement, ratings, and review velocity in Electronics, you end up doing the same loop: open the page, scroll, copy product details, paste them into a spreadsheet, and pray the formatting doesn’t break. Then you do it again tomorrow. The work itself isn’t “hard,” but it creates a steady mental tax and a real risk of subtle mistakes that ruin comparisons later.
The friction compounds. Here’s where it usually breaks down for teams trying to do this by hand.
- Capturing 50–100 products can eat about 1–2 hours, especially when you include verification and cleanup.
- A single column drifting out of place makes your week-over-week comparisons basically useless.
- Best Seller pages are inconsistent, so “copy, paste, repeat” never stays repeatable for long.
- You don’t get a reliable history, which means you’re making decisions on vibes instead of trends.
The Solution: Bright Data Scraping + AI Parsing + Sheet-Ready Output
This workflow automates the full “pull → clean → store” loop. It starts in n8n with a manual trigger (you can schedule it later), sets the target Amazon Best Sellers URL and your Bright Data Web Unlocker zone, and then requests the page through Bright Data so you’re not fighting blocks or flaky access. Next, an AI extraction step reads the unstructured page content and turns it into structured JSON fields like product name, rank, price, rating, review count, and other useful attributes. Finally, the workflow sends the structured payload to a webhook endpoint so you can capture it in Google Sheets, a database, or a dashboard pipeline.
The workflow starts when you launch it in n8n. Bright Data fetches the Best Sellers page cleanly, then the AI model extracts the exact fields you care about. From there, the webhook handoff makes it easy to log in Google Sheets and build a trend view that updates on your schedule.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you track the top 100 products in Amazon Electronics once per day. Manually, even at a quick pace of about 1 minute per product (find it, copy details, paste, fix formatting), that’s roughly 100 minutes per day, plus another 20 minutes cleaning the sheet. With this workflow, you trigger the run (about a minute), wait a few minutes for the page pull and AI extraction, then the webhook sends structured rows straight into your log. You get close to 2 hours back each day, and the data is cleaner.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Bright Data Web Unlocker to reliably fetch Amazon pages.
- Google Gemini API to extract structured fields from page content.
- Bright Data Web Unlocker token (get it from Bright Data zone settings).
Skill level: Intermediate. You’ll connect credentials, paste a webhook URL, and tweak a prompt if you want different fields.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A run kicks off in n8n. The workflow is set up with a manual trigger, which is perfect for testing. Once it’s working, many teams switch this to a schedule so the sheet updates every morning.
The target page and access method are set. n8n assigns the Amazon Best Sellers URL plus the Bright Data Web Unlocker zone details so the HTTP request is repeatable and doesn’t depend on someone remembering the right parameters.
Bright Data pulls the page content. The HTTP Request node retrieves the Best Sellers page through Bright Data, which helps avoid the usual blocking and incomplete responses that show up with plain scraping.
AI turns the page into clean fields. The extraction step reads the unstructured content and outputs structured JSON, then the workflow sends that result to your webhook endpoint so you can write rows into Google Sheets or feed another system.
You can easily modify the target Amazon category to track other Best Seller lists 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 so you can test the extraction flow on demand.
- Add the Manual Launch Trigger node to your canvas.
- Leave the default settings as-is because it requires no configuration.
- (Optional) Keep Flowpast Branding as a sticky note for documentation—this node does not affect execution.
Step 2: Connect the Data Source and Target URL
Set the target URL and Bright Data zone, then send the request to fetch the bestseller page.
- In Assign Target URL and Zone, set url to
https://www.amazon.[CONFIGURE_YOUR_API_KEY]?product=unlocker&method=api. - In Assign Target URL and Zone, set zone to
web_unlocker1. - Open Request Bestseller Page and set URL to
https://api.brightdata.com/request. - Set Method to POST, enable Send Body and Send Headers.
- In Body Parameters, set zone to
={{ $json.zone }}and url to={{ $json.url }}, and set format toraw. - Credential Required: Connect your httpHeaderAuth credentials in Request Bestseller Page.
[CONFIGURE_YOUR_API_KEY] in the Assign Target URL and Zone URL, otherwise Bright Data will reject the request.Step 3: Set Up the AI Extraction
Use the LLM-driven extractor to parse the bestseller page into a structured schema.
- Open Extract Structured Fields and set Text to
={{ $json.data }}. - Set Schema Type to manual and paste the provided JSON schema into Input Schema.
- Confirm Gemini Chat Model is connected as the language model to Extract Structured Fields.
- Credential Required: Connect your googlePalmApi credentials in Gemini Chat Model (credentials are added to the model node, not the extractor).
Step 4: Configure the Output Webhook
Send the extracted summary to a webhook endpoint for downstream consumption.
- Open Webhook Result Dispatcher and set URL to
https://webhook.site/bc804ce5-4a45-4177-a68a-99c80e5c86e6. - Enable Send Body and set Body Parameters → summary to
={{ $json.output }}. - Ensure the execution flow is Extract Structured Fields → Webhook Result Dispatcher.
Step 5: Test and Activate Your Workflow
Run the workflow to confirm the extraction and webhook delivery, then activate for production use.
- Click Execute Workflow on Manual Launch Trigger to run a test.
- Verify Request Bestseller Page returns raw HTML in data, and Extract Structured Fields outputs structured JSON.
- Check the webhook endpoint for a payload containing the summary field.
- Turn on the workflow using the Active toggle when you are ready for production runs.
Common Gotchas
- Bright Data credentials can expire or need specific permissions. If things break, check your Web Unlocker zone token and header auth value 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.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 30–60 minutes if you already have Bright Data and Gemini keys.
No. You’ll mostly connect accounts and paste in your webhook destination. The only “technical” part is tweaking the extraction prompt if you want different fields.
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 Bright Data usage and Gemini API costs.
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 a straightforward change. Update the target URL in the “Assign Target URL and Zone” part of the workflow to point at another Best Sellers category (Computers & Accessories, Home Audio, and so on). If the page layout differs, adjust the extraction prompt used for the structured fields so the AI outputs the same columns you expect. Common tweaks include adding promotions, capturing ASINs, or outputting a short summary alongside the JSON.
Usually it’s an expired or incorrect Web Unlocker token in your header authentication. Double-check the Bright Data zone, regenerate the token if needed, then update the credential in n8n. If it still fails, confirm the requested URL is allowed in your Bright Data setup and you’re not hitting account limits during heavy testing.
A typical run can handle the full Best Sellers page without trouble, and most teams log the top 50–100 items per pull.
For scraping + parsing workflows, n8n is usually the more practical choice because you can control the HTTP request, shape the data, and branch logic without fighting platform limits. You also get a self-hosting option, which matters if you’re running frequent pulls. Zapier and Make are fine for simple “app to app” moves, but they’re less comfortable when the data starts messy. If you’re unsure, Talk to an automation expert and we’ll sanity-check the approach with you.
Once this is running, your sheet becomes a living record of what’s actually happening in the category. The workflow handles the repetitive capture so you can focus on what to do about it.
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.
