# WooCommerce Product Monitor: Price and Stock Alerts (`accountable_eel/woocommerce-product-monitor`) Actor WooCommerce store scraper and price monitor: export a WooCommerce store catalog to Google Sheets, or watch a supplier store for dropshipping. One row per variant: price, regular/sale price, stock, then only price drops, back in stock alerts, new, removed products. Alerts to Discord, Slack, Telegram. - **URL**: https://apify.com/accountable_eel/woocommerce-product-monitor.md - **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community) - **Categories:** E-commerce, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.50 / 1,000 product variant returneds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## WooCommerce Product Monitor: Price and Stock Alerts WooCommerce's own public Store API (`wc/store/v1`) — the endpoint every WooCommerce storefront already uses to render its own catalog and cart — read and turned into one row per variant: price, regular/sale price, stock and a direct product link. Turn on monitoring and every later run returns only what changed since the last one: new products, price drops, price rises, back in stock, out of stock, or removed — with alerts to Discord, Slack or Telegram. No key, no login, no proxy by default. ### Who it's for Anyone who needs to watch a WooCommerce competitor's or supplier's catalog without checking it by hand: dropshippers tracking a supplier's prices and stock, brands watching a reseller's pricing, or a sourcing team that wants a Slack ping the moment a product goes back in stock. WooCommerce runs a large share of the web's independent online stores (Shopify's own equivalent, `shopify-product-monitor`, covers the other half); this actor is the same monitoring pattern applied to WooCommerce's Store API instead of Shopify's `/products.json`. ### Monitoring: price drops, back in stock, new and removed Turn on **"Only return variants that changed since the last run"** and this actor becomes a watchlist. The first run reads the whole catalog and remembers every variant's price and stock in a named key-value store; every later run compares against that memory and returns only the variants that are new, cheaper, dearer, back in stock, out of stock, or removed from the store — pick which of those six count with **"Alert me on"**. Unchanged variants are dropped before billing, so a quiet run (nothing changed) costs only the per-run start fee, not a cent per variant. Schedule it hourly or daily as an Apify Task to get a running price-and-stock feed for a store you don't control. A removed variant is only ever reported once a run reads the *whole* catalog successfully (no page failed, no "most products per store" cap was hit) — a run that stopped early never claims something still on the shelf was removed. A variant not seen for 30 days is quietly forgotten rather than kept as a permanent tombstone. ### Send alerts to Discord, Slack or Telegram Paste a webhook URL into **"Send alerts to"** and every changed variant is posted there the moment it's billed: product photo, name, variant, price (with the previous price for a move), stock, and a link, tagged NEW / PRICE DROP -12% / BACK IN STOCK / REMOVED. Discord and Slack take their channel webhook URL directly; Telegram takes `https://api.telegram.org/bot/sendMessage?chat_id=`; any other URL gets the same alert as JSON, for n8n, Make, Zapier or a bot of your own. Messages are always free and a delivery failure never fails the run — the row's `notifyErrors` field says why, if anything. ### Why a store might not respond Not every WooCommerce store leaves its Store API reachable. Some installs disable it outright; others sit behind a CDN or WAF that blocks requests that don't look like a normal browser tab, while the same store's un-proxied path works fine. Measured live during this build: the same store's `www.` alias can answer a Cloudflare challenge on the identical path its bare domain serves as clean JSON. When that happens the row comes back as `"found": false` with a `status` of `STORE_API_DISABLED` (a real WordPress site, but WooCommerce's Store API isn't available) or `BLOCKED` (a firewall or CDN refused the request) — not a bug, and never charged. This actor does not retry a blocked store through a proxy by default; if it matters for your store, open an Apify support ticket or try again later, since these firewalls are often intermittent. ### Example runs Each input below needs no key or login and returns real rows on its own: - **One live store, default settings** — `{"domains": ["porterandyork.com"]}`. The Console's prefilled "Start" button runs exactly this. Returns every variant currently in the catalog. - **Watchlist mode** — `{"domains": ["porterandyork.com"], "deltaMode": true}`. The first run banks a baseline for free comparison next time; every run after that returns only variants that are new, cheaper, dearer, back in stock, out of stock or removed. - **A capped sample** — `{"domains": ["porterandyork.com"], "maxProductsPerStore": 20}`. Reads only the first 20 products (and their variants) for a cheap, quick check of a new store before committing to a full read. ### How to use 1. **In the Apify Console.** Open the actor page and click **Start** — the `domains` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found. 2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token: ```bash curl "https://api.apify.com/v2/acts/accountable_eel~woocommerce-product-monitor/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"domains":["porterandyork.com"]}' ``` 3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required. ### Input ```json { "domains": [ "porterandyork.com" ] } ``` One store per line: a bare domain such as example.com. Only public WooCommerce stores whose Store API is reachable work; no login and no API key. Accepted formats: porterandyork.com, example-shop.com. ```json { "items": ["", ""], "maxConcurrency": 5 } ``` `items` is a list of WooCommerce store domains. One dataset row is returned per item; rows with `"found": false` are never charged. ### Output One row per item, for example: | query | found | status | domain | productCount | totalVariants | variantCount | truncated | truncatedBy | monitorStatus | newCount | priceDropCount | priceRiseCount | backInStockCount | outOfStockCount | removedCount | variants | productId | productName | variantId | variantName | sku | price | regularPrice | salePrice | currency | available | stockQuantity | permalink | imageUrl | scrapedAt | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | porterandyork.com | true | OK | | | | \ | | | | | | | | | | \ | | | | \ | | | | | | | | | | 1970-01-01T00:00:00.000Z | A miss comes back as a row with `"found": false` and is never charged. ### Pricing - **Product variant returned**: $1 per 1,000 variants Plus a $0.0075 start fee per run. Each event above is billed independently, only when it actually returns data — misses (`found:false`) are never charged. ### Use it from Clay, n8n, Make, or an AI agent This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token. ```bash curl "https://api.apify.com/v2/acts/accountable_eel~woocommerce-product-monitor/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"domains":["porterandyork.com"]}' ``` **n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~woocommerce-product-monitor/run-sync-get-dataset-items?token=`, Body Content Type `JSON`, JSON Body `{"domains":["porterandyork.com"]}` (swap in an expression from an earlier node for a real value). **Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~woocommerce-product-monitor/run-sync-get-dataset-items?token=`, Body `{"domains":["{{store}}"]}`, mapping the row's store into the `domains` array. **MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "woocommerce product monitor: price and stock alerts" — the agent will find and run this actor. # Actor input Schema ## `domains` (type: `array`): One store per line: a bare domain such as example.com. Only public WooCommerce stores whose Store API is reachable work; no login and no API key. Accepted formats: porterandyork.com, example-shop.com. You're only charged for the ones we actually find — a miss costs nothing. ## `maxProductsPerStore` (type: `integer`): Products read per store, up to 10,000. A variable product usually has several variants (sizes, colours) and you pay per variant row returned. Lower this to cap the cost. ## `testRun` (type: `boolean`): Turn this on to test your input on a small sample before running the full list. Turn it off to process everything. ## `onlyFound` (type: `boolean`): Only keep rows where something was actually found. Misses are always free, whether or not you show them here. ## `includeKeywords` (type: `array`): Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything. ## `excludeKeywords` (type: `array`): Optional. Drop any result that mentions one of these words. Leave empty to skip nothing. ## `maxResults` (type: `integer`): Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit. ## `deltaMode` (type: `boolean`): Turns each store into a watchlist. The first run remembers every variant's price and stock; every later run returns only the variants that are new, cheaper, dearer, back in stock, out of stock or removed (pick which below). Unchanged variants are removed before you are billed, so a quiet run costs only the start fee. Schedule it hourly or daily and send the alerts to Discord, Slack or Telegram. ## `deltaName` (type: `string`): Leave empty and a name is derived from your alert settings, so two schedules with different settings keep separate memories. Type your own name to keep one memory across a settings change, or to share it between schedules. Naming a watchlist with the checkbox above off returns every variant but still marks each one. ## `alertOn` (type: `array`): Which changes count. Only these are returned and billed with monitoring on, and only these are sent as messages. A variant that changed in two ways (cheaper and back in stock) is one row whose changeType is the first match and whose changes lists both. Leave all selected to see everything. ## `minPriceChangePct` (type: `integer`): A price move smaller than this is ignored, so a 1 cent rounding change does not fire an alert. 0 counts every change. Applies to price drops and price rises. ## `skipFirstRun` (type: `boolean`): Off by default: on the first run every variant counts as new and is billed. Turn this on to store the baseline and return nothing (no rows, no messages, no per-row charge) so alerts start with the second run. ## `quietRunOutput` (type: `string`): A quiet run is a store with no changes since the last run. "One summary row" keeps a row with monitorStatus NO_CHANGES so you can see the store was checked. "Nothing" writes zero items, so a bot or spreadsheet integration never has to skip rows. A store that failed still returns its error row. ## `notifyUrl` (type: `string`): Optional. After the variants are billed, each changed variant is posted here as one message: photo, name, size or colour, price, stock and link, with a NEW / PRICE DROP -X% / BACK IN STOCK badge. Discord or Slack: paste the channel's webhook URL. Telegram: https://api.telegram.org/bot/sendMessage?chat_id=. Any other URL receives the alert as JSON. Messages are free, and a message that fails never fails the run (the row's notifyErrors says why). Stored encrypted, never logged or written to the results. Needs monitoring turned on. ## `notifyFormat` (type: `string`): Leave on "Detect from the link": discord.com links get Discord messages, hooks.slack.com Slack, api.telegram.org Telegram, anything else JSON. Pick one only to override that. ## `maxNotificationsPerRun` (type: `integer`): Up to 100. Above this, one "+N more" message says how many more variants are in the run's dataset, so a busy first run never floods the channel. 0 sends only that one summary message. ## `columns` (type: `array`): Choose which pieces of information to include in each result row. All are included by default. ## `expandRows` (type: `boolean`): When on, each variant found gets its own row instead of being grouped under its store. You're still only charged once per store, no matter how many rows it produces. ## `maxConcurrency` (type: `integer`): Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady. ## `proxyConfiguration` (type: `object`): Apify Proxy config. Residential recommended for anti-bot-sensitive targets. ## Actor input object example ```json { "domains": [ "porterandyork.com" ], "maxProductsPerStore": 250, "testRun": false, "onlyFound": false, "includeKeywords": [], "excludeKeywords": [], "deltaMode": false, "deltaName": "", "alertOn": [], "minPriceChangePct": 0, "skipFirstRun": false, "quietRunOutput": "summary", "notifyFormat": "auto", "maxNotificationsPerRun": 20, "columns": [ "domain", "productCount", "totalVariants", "variantCount", "truncated", "truncatedBy", "monitorStatus", "newCount", "priceDropCount", "priceRiseCount", "backInStockCount", "outOfStockCount", "removedCount", "variants", "productId", "productName", "variantId", "variantName", "sku", "price", "regularPrice", "salePrice", "currency", "available", "stockQuantity", "permalink", "imageUrl" ], "expandRows": true, "maxConcurrency": 5, "proxyConfiguration": { "useApifyProxy": true } } ``` # Actor output Schema ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "domains": [ "porterandyork.com" ], "includeKeywords": [], "excludeKeywords": [], "alertOn": [] }; // Run the Actor and wait for it to finish const run = await client.actor("accountable_eel/woocommerce-product-monitor").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "domains": ["porterandyork.com"], "includeKeywords": [], "excludeKeywords": [], "alertOn": [], } # Run the Actor and wait for it to finish run = client.actor("accountable_eel/woocommerce-product-monitor").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "domains": [ "porterandyork.com" ], "includeKeywords": [], "excludeKeywords": [], "alertOn": [] }' | apify call accountable_eel/woocommerce-product-monitor --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/woocommerce-product-monitor" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/27CDhFO8tv0n2tauK/builds/Jz81gsnVrkimas0Ma/openapi.json