Price Monitoring Bot avatar

Price Monitoring Bot

Pricing

from $1.00 / 1,000 results

Go to Apify Store
Price Monitoring Bot

Price Monitoring Bot

Scrapes product prices and availability from a page, compares them with the previous run and optionally sends a Telegram alert when something changes.

Pricing

from $1.00 / 1,000 results

Rating

0.0

(0)

Developer

Mykhailo Rudiak

Mykhailo Rudiak

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

19 hours ago

Last modified

Categories

Features

Limited permissions

Share

Monitor prices, availability and new products on any product-catalog page and get a Telegram alert when something changes.

You point the Actor at a catalog page, tell it which CSS selectors hold the title, price (and optionally availability) of each product, and schedule it. It remembers what it saw last time and tells you only what changed.

How it works

  1. First run – baseline. The Actor scrapes the page(s) and saves the result as the baseline state. No alert is sent. Every product gets changeType: "new" in the Dataset.
  2. Every next run – comparison. The Actor scrapes again and compares each product with the saved state. It reports only real changes:
    • 🆕 a product that was not in the previous run,
    • 💰 a price change,
    • 📦 an availability change.
  3. If there are changes and notifyOnChange is on, one Telegram message with the list of changes is sent. Without a Telegram token and chat ID the message is only written to the run log.
  4. The new result replaces the saved state.

The state is stored in a named Key-Value Store (price-state) in your account, separately for each startUrl, so it survives between runs. To get regular alerts, run the Actor on an Apify Schedule. Deleting that store resets the baseline.

Pages are rendered in headless Chromium (Playwright), so JavaScript-rendered catalogs work too.

Input

Only startUrl is required. The default selectors match books.toscrape.com and are only a starting point – set them for your site.

FieldTypeRequiredDescriptionExample
startUrlstringyesURL of the catalog page to monitor.https://books.toscrape.com/
itemSelectorstringnoCSS selector matching one product card. Default: article.product_pod.li.product
titleSelectorstringnoSelector of the title, relative to the card. The element's title attribute is used if present, otherwise its text. Default: h3 a.h2.product-title
priceSelectorstringnoSelector of the price, relative to the card. Default: p.price_color.span.price
availabilitySelectorstringnoSelector of the availability text, relative to the card. Leave empty if the site has none – availability will then be null. No default.p.instock.availability
linkSelectorstringnoSelector of the link to the product page, relative to the card. Its URL is used as the product's identity between runs. Set it when the title is not a link. No default.a.product-link
maxItemsintegernoMaximum number of products checked in total, across all pages. Default: 12.100
maxPagesintegernoMaximum number of pages to scrape. Needs nextPageSelector. Default: 1.3
nextPageSelectorstringnoSelector of the "next page" link or button. Pagination stops when it is not found, or at maxPages / maxItems. If empty, only the first page is scraped.li.next a
navigationTimeoutSecsintegernoTimeout for page navigation and for waiting for the product list. Default: 15.30
telegramBotTokenstring (secret)noBot token from @BotFather.123456:ABC-DEF...
telegramChatIdstringnoID of the chat that receives alerts.123456789
notifyOnChangebooleannoSend the alert when changes are found. Default: true. The Dataset is written either way.true
proxyConfigurationobjectnoApify Proxy or your own proxy URLs. If not set, the Actor connects directly.{"useApifyProxy": true}

Setting up Telegram

  1. Message @BotFather in Telegram, send /newbot and copy the token.
  2. Send any message to your new bot.
  3. Open https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates and find "chat":{"id": ...} – that is your chat ID.
  4. Put both values into telegramBotToken and telegramChatId.

Telegram messages are limited to 4096 characters; longer change lists are truncated.

Output (Dataset)

One item per product per run:

FieldTypeDescription
titlestringProduct title.
pricenumberPrice as a number (£1,234.50 → 1234.5). If the text cannot be parsed, the raw text is kept as a string.
currencystring | nullISO code detected from the currency symbol (see limitations), or null if unknown.
availabilitystring | nullAvailability text. null if availabilitySelector is not set; empty string if it is set but not found on the card.
changeTypestringResult of the comparison with the previous run (see below).
previousPricenumber | nullPrevious price when the price changed, otherwise null.
checkedAtstringUTC timestamp of the run, ISO 8601.

changeType values:

ValueMeaning
newProduct was not in the previous run. On the very first run all products are new, but no alert is sent.
price_changedPrice (or currency) differs from the previous run.
availability_changedAvailability text differs from the previous run.
price_and_availability_changedBoth changed.
unchangedNothing changed.

Example item:

{
"title": "Ivysaur",
"price": 79.0,
"currency": "GBP",
"availability": null,
"changeType": "price_changed",
"previousPrice": 87.0,
"checkedAt": "2026-11-17T16:04:04+00:00"
}

Currency symbols recognized: £ GBP, € EUR, $ USD, ¥ JPY, ₴ UAH, ₹ INR, zł PLN, Kč CZK, CHF.

Known limitations

  • Currency comes from the symbol only. $ is always read as USD – USD, CAD, AUD and others cannot be told apart. ¥ is always read as JPY (it is also used for CNY). Prices with other or no symbols get currency: null.
  • Availability is null unless you set availabilitySelector. The Actor does not guess it. A status that exists only as a CSS class (for example instock on the card) cannot be read.
  • Set linkSelector when the title is not a link, and do not change it between runs. Products are matched between runs by their URL; if there is no link, by title. Titles are not always unique, so without a link two different products with the same title can be confused. Adding or changing linkSelector on an already monitored page changes the product identities, and the next run will report all products as new.
  • Monitor stable catalog pages only. Blocks such as "popular right now" or "top items" whose content rotates will produce constant new alerts.
  • Changing maxItems, maxPages or the selectors between runs changes the set of products and is reported as new products. Choose them once per monitored page.
  • Disappeared products are not reported. The Actor alerts on new products, price changes and availability changes, not on removed products.
  • A failed run does not change the state. If a page after the first one fails to load, the run fails and the saved state stays as it was.
  • One run monitors one startUrl with one set of selectors. Logins, forms and other page interaction are not supported.

Example

Goal: get a Telegram message when a Pokémon on scrapeme.live gets cheaper.

Input:

{
"startUrl": "https://scrapeme.live/shop/",
"itemSelector": "li.product",
"titleSelector": "h2.woocommerce-loop-product__title",
"priceSelector": "span.price",
"linkSelector": "a.woocommerce-LoopProduct-link",
"nextPageSelector": "a.next.page-numbers",
"maxPages": 3,
"maxItems": 100,
"telegramBotToken": "<your bot token>",
"telegramChatId": "<your chat id>"
}

Run it once – it stores the baseline of 48 products and sends nothing. Then put the Actor on a schedule (for example every 6 hours). When the price of a product changes, you receive a message like:

📊 Price Monitor: changes detected
💰 Ivysaur: price changed 87.0 → 79.0

The alert lists every price change, up or down. To work only with price drops, open the Dataset and filter items where price < previousPrice.

Proxy

Many shops block automated traffic. For sites with bot protection or rate limits, enable Apify Proxy in proxyConfiguration (for example {"useApifyProxy": true}; for strictly protected sites choose the residential proxy group). You can also pass your own proxy URLs with {"useApifyProxy": false, "proxyUrls": ["http://user:pass@host:port"]}.