Scheduled Walmart product scraping to Google Sheets with ScrapeOps
UnknownWhat this workflow does
This workflow has 10 nodes and runs on a schedule (every 4 hours). Along the way it connects Google Sheets, Slack and Scrapeops (community).
How it runs
Trigger: On a schedule (every 4 hours).
- Set Search Parameters (Edit Fields (Set)): sets or maps fields
- Scrape Ops: uses Scrape Ops
- Scrape Ops: uses Scrape Ops
- Add Metadata (Edit Fields (Set)): sets or maps fields
- Split Products Array (Code): runs custom JavaScript code
- Format Product Data (Edit Fields (Set)): sets or maps fields
- Filter Valid Products (If): checks a condition and branches into true / false
- Save to Google Sheets (Google Sheets): append
- Send Slack Summary (Slack): uses Slack
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @scrapeops/n8n-nodes-scrapeops is verified or supports 3.0 (used in ScrapeOps Parser, ScrapeOps Proxy).
Nodes used (7)
- Scrape Ops
@scrapeops/n8n-nodes-scrapeops.ScrapeOps - Edit Fields (Set)
n8n-nodes-base.set - Google Sheets
n8n-nodes-base.googleSheets - Code
n8n-nodes-base.code - Schedule Trigger
n8n-nodes-base.scheduleTrigger - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack
From the author
Overview This n8n template automates Walmart product discovery and sends clean results to Google Sheets on a fixed schedule (default: every 4 hours). It uses ScrapeOps Proxy API for resilient page fetches (with JS render + scroll) and ScrapeOps Parser API for…