Product Feed Price & Stock Delta Monitor avatar

Product Feed Price & Stock Delta Monitor

Pricing

Pay per usage

Go to Apify Store
Product Feed Price & Stock Delta Monitor

Product Feed Price & Stock Delta Monitor

Monitor public product feeds in JSON, XML, RSS, Google Merchant, or CSV formats for price drops, stock changes, removed products, and clean stateful deltas.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Nikita S

Nikita S

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Monitor public product feeds — JSON APIs, XML/RSS/Atom feeds, Google Merchant feeds, and CSV exports — and emit only products that changed since the previous run.

Use it for:

  • supplier feed monitoring;
  • affiliate/catalog price changes;
  • competitor product-feed deltas;
  • back-in-stock and sold-out alerts;
  • Google Sheets, n8n, Make, Slack, or Discord workflows.

This Actor is intentionally feed-first: it avoids browser scraping and anti-bot fights. If a store already exposes a feed/API/export, this is the cheap reliable monitor.

Visual demo: Product Feed Delta Monitor

Product Feed Delta Monitor visual overview

Product Feed Delta Monitor workflow diagram

Product Feed Delta Monitor sample output dataset row

These images are hosted in a persistent Apify key-value store so the Store README has stable, clickable visual previews.

Input

{
"feedUrls": ["https://woocommerce.com/wp-json/wc/store/v1/products?per_page=5"],
"onlyChanged": true,
"persistState": true,
"minPriceChangePct": 0,
"priceDropAlertPct": 20
}

Supported formats:

  • JSON arrays or objects with products, items, data, or results;
  • XML/RSS/Atom/Google Merchant <item> or <entry> feeds;
  • CSV feeds with headers like id,title,link,price,availability.

Output

Rows include:

  • feedUrl
  • productId
  • sku
  • name
  • brand
  • productUrl
  • price
  • currency
  • availability
  • available
  • status
  • event
  • events
  • event_severity
  • changes

Example:

{
"feedUrl": "https://example.com/products.xml",
"productId": "SKU-1",
"name": "Example Jacket",
"productUrl": "https://example.com/products/jacket",
"price": 70,
"currency": "EUR",
"availability": "out_of_stock",
"available": false,
"status": "changed",
"event": "price_change",
"events": ["price_change", "sold_out"],
"event_severity": "high",
"changes": [
{ "field": "price", "before": 100, "after": 70 }
]
}

Events

  • new_product
  • price_change
  • availability_change
  • restock
  • sold_out
  • removed_product
  • unchanged if requested
  • error

Monetization hooks

The Actor emits Pay-Per-Event hooks for meaningful deltas:

  • delta_result for new/changed/removed product rows;
  • price_drop_alert for price drops at or above the configured threshold;
  • apify-actor-start once per run/user when enabled by platform pricing.

Notes

  • This Actor does not bypass CAPTCHA, login walls, Cloudflare, or anti-bot systems.
  • For Shopify/WooCommerce/product-page JSON-LD monitoring, use the sibling specialized Actors when they fit better.
  • For scheduled monitoring, keep persistState=true so each run compares against the previous snapshot.

Run it from Claude / Cursor / VS Code via MCP

The Actor is available through the Apify MCP server, so you can ask your AI assistant to "poll this feed daily and email me the changes" instead of writing a cron job.

Add this to your MCP client config (for example claude_desktop_config.json):

{
"mcpServers": {
"apify": {
"command": "npx",
"args": ["-y", "@apify/mcp-server"],
"env": {
"APIFY_TOKEN": "your-apify-api-token"
}
}
}
}

Once connected, the assistant can discover this Actor and trigger runs with a plain prompt like "Run Product Feed Delta Monitor on https://example.com/feed.csv every 6 hours and list the new SKUs." The remote MCP server at https://mcp.apify.com works the same way without a local install.

Quick start

  1. Open this Actor in Apify Console.
  2. Paste one or more product feed/API URLs into the input.
  3. Keep persistState enabled for scheduled monitoring.
  4. Run once to create the baseline snapshot.
  5. Run again on a schedule to receive only delta rows.
  6. Export the dataset to CSV/JSON, or send it to Google Sheets, n8n, Make, Slack, Discord, or a webhook.

Sample output

Use this sample dataset to see the output shape before running it yourself:

The important fields for automation are event, events, event_severity, status, and changes. Filter for event_severity = high when you only want alerts that deserve immediate attention.

Pricing and cost expectations

This Actor is designed for scheduled monitoring and delta-only outputs. It avoids charging or processing unchanged rows where possible. Pay-Per-Event pricing is scheduled/used for meaningful emitted deltas such as new items, removed items, price changes, stock changes, URL changes, or pricing-plan changes depending on the Actor.

Start with a small input list first. Once the baseline looks correct, schedule recurring runs and set a reasonable max charge limit in Apify.

FAQ

Is this a one-time scraper or a monitor?

It is a monitor. The first run creates a baseline. Later runs compare the current data against the stored baseline and emit only the changes.

Can I send alerts to Slack, Discord, Google Sheets, n8n, or Make?

Yes. Use Apify integrations, webhooks, dataset export, or API polling. The event, events, event_severity, and changes fields are meant for automation routing.

Does it bypass CAPTCHA, login walls, or anti-bot systems?

No. This portfolio is intentionally focused on public, low-risk sources such as public APIs, feeds, sitemaps, product pages, or storefront endpoints.

Which rows should trigger alerts?

Use event_severity. High-severity rows are the best candidates for Slack/Discord/email alerts. Low-severity rows are usually better for reports or spreadsheets.

Support and custom monitoring

If a public source does not fit this Actor, check the related monitors below. Open an issue on the Actor page with a sample URL and the output you need.

Which monitor should I use?

This Actor is part of a focused monitoring portfolio. Pick the narrowest Actor that matches your source:

Source you haveUse this ActorBest for
Shopify storeShopify Delta MonitorShopify competitor price/stock/sale monitoring
WooCommerce storeWooCommerce Delta MonitorWooCommerce Store API product deltas
Product page URLs with Schema.org JSON-LDSchema.org Product Delta MonitorMagento, BigCommerce, custom stores, marketplaces
Product feeds / APIs / CSV / XMLProduct Feed Delta MonitorSupplier feeds, affiliate feeds, Google Merchant exports
sitemap.xmlSitemap Delta MonitorSEO, content ops, RAG indexing queues
SaaS pricing pagesSaaS Pricing Page MonitorPlan/price/feature changes on public pricing pages

All monitors are built for scheduled runs, stateful comparisons, delta-only outputs, and workflow automation via Google Sheets, n8n, Make, Slack, Discord, or webhooks.