Track price and stock changes between two product scrapes
Quiet Works Lab
Feed it today's and yesterday's datasets from any product scraper and get one row for each product whose price, stock or other fields changed, with the old and new values side by side. New and removed products are left out, so the result is a short list of real changes. Run it after each scheduled scrape to build a price history or an alert list.
Input
Output fields
Sign up on Apify or log in
The Dataset Change Tracker Actor is ready to run with the inputs already set for "Track price and stock changes between two product scrapes". Sign up or log in and you'll land in Apify Console with a copy of this exact task.
Start the "Track price and stock changes between two product scrapes" task
The Dataset Change Tracker Actor will start running based on the input automatically. You can also change all the input fields, like key fields, fields to ignore, and more, to match your specific use case.
Receive the "Track price and stock changes between two product scrapes" output
Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as change type, key, key hash, and more.
Integrate into your workflow
The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Track price and stock changes between two product scrapes" task via API.
Integrate "Track price and stock changes between two product scrapes" into your workflow
Connect "Track price and stock changes between two product scrapes" with 100+ integrations, or run it via API or MCP.
Webhook
n8n
Make
Zapier
Airbyte
Keboola
IFTTT
Hubspot
GDrive
Gmail
Apify MCP
GitHub
Slack
LangChain
LlamaIndex
Flowise
Pinecone
OpenAI
Mastra
Clay
The price change task works with the dataset of any scraper, as long as each product has a stable key such as its URL or SKU. Choose that field as the key field.
Yes. List them in ignoreFields, for example scrapedAt or a rating count, and the price change task compares only the remaining fields.
Yes. Set stateStoreName and the Dataset Change Tracker remembers the last run (as hashes), so each run of the price change task compares with the previous one without choosing it.