Zeeman Price Monitor - Product prices for Netherlands avatar

Zeeman Price Monitor - Product prices for Netherlands

Pricing

from $2.00 / 1,000 product page reads

Go to Apify Store
Zeeman Price Monitor - Product prices for Netherlands

Zeeman Price Monitor - Product prices for Netherlands

Extract public product prices from Zeeman.com. Includes the product name, price and currency. Zeeman product pages for the Netherlands, including a baseline and a price change. The prefilled sample is the quick default run. Results as JSON, CSV or Excel. Access through API or MCP.

Pricing

from $2.00 / 1,000 product page reads

Rating

0.0

(0)

Developer

Muhammet Mustafa Dincer

Muhammet Mustafa Dincer

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

10 days ago

Last modified

Categories

Features

Limited permissions

Share

🤖 What does the Zeeman price monitor do?

A Zeeman price monitor reads public product prices from Zeeman.com. It can collect:

  • public product prices from Zeeman.com
  • the product name, price and currency
  • A saved baseline when the source compares the next run
  • JSON, CSV or Excel from the dataset
  • The same run through the Apify API or MCP

💡 Why use the Zeeman price monitor?

People use a Zeeman price monitor when the same public page would otherwise be checked by hand.

  • Watch a change. The Actor keeps a baseline and writes the next difference.
  • Feed a sheet. The dataset opens as JSON, CSV or Excel.
  • Call it from code. The Apify API runs the same input.
  • Hand it to an agent. Apify MCP can call the Actor with that input.
  • Stay on the sample. The prefilled input is the short, cheap run.

🚀 How do you run the Zeeman price monitor?

  1. Open this Actor and click Try for free.
  2. Keep the prefilled sample, or set Product URLs.
  3. Leave the other fields on their defaults unless you need a narrower run.
  4. Click Run.
  5. Open the Dataset tab and download JSON, CSV or Excel.

Sample input from the prefilled schema:

{
"productUrls": [
"https://www.zeeman.com/nl-nl/product/handdoek-bruin-109128-1"
],
"onlyChanges": false,
"monitorName": "default"
}

⚠️ What limits does this Actor have?

The input schema is the limit. Defaults and prefills are unchanged by this copy update.

  • productUrls: at most 10 items.
  • A robots.txt disallow is not treated as a successful priced read when the source checks robots.txt.
  • Actor Start is priced in the table. The other events are billed only when the source charges them and the charge is accepted.
  • A spending limit that cannot pay for the next event stops that event. The source does not invent a result to replace it.

💳 How much does the Zeeman price monitor cost?

The table is the live pay-per-event price list (pricingInfos) for this Actor. It is not a guessed price.

EventWhat the price list calls itFreeBronzeSilverGoldPlatinumDiamond
apify-actor-startActor Start$0.0005$0.0005$0.0005$0.0005$0.0005$0.0005
product-checkedProduct page read$0.002$0.002$0.002$0.002$0.002$0.002
price-changedPrice changed$0.005$0.0043$0.0036$0.0029$0.0029$0.0029

One Free-plan run that bills one product-checked plus Actor Start is $0.0005 + $0.002 = $0.0025. 1,000 product-checked events on the Free plan are $2.00, before Actor Start. These figures use only the live prices in the table.

apify-actor-start is in the live price list. Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). The source names product-checked and charges it with Actor.charge when that event happens. One Zeeman product page whose public price was read and kept, including the first baseline and a later run whose price did not change. A search, account, cart, or other non-product page, a robots.txt disallow, an HTTP error, a network error, a page with no product price, an access limit, or a skip because of the spending limit is not this event. The source names price-changed and charges it with Actor.charge when that event happens. Charged in addition to the product check when the kept price or currency differs from the saved baseline. The first baseline and an unchanged price are not this event. A change the spending limit cannot pay for is not requested and not stored.

📝 What input does this Actor take?

Required fields are marked. Defaults and prefills are the quick run; this text does not change them.

FieldRequiredWhat it means
productUrls (Product URLs)YesZeeman product page URLs, one per line. The sample is a public brown towel page. Search, cart, ch...
onlyChanges (Only price changes)NoLeave this off for the sample so a repeated run still writes the current price. Turn it on, or om...
monitorName (Watchlist name)NoBaselines are stored per watchlist. Use a new name to start over without deleting the old snapshot.

📊 What output does this Actor return?

The dataset schema names every stored field.

FieldWhat the schema says
recordTypeproduct: one row per product URL.
statusbaseline_saved, unchanged, price_changed, not_a_product, http_error, ...
productNamePublic product name from the page. Null when the price was not stored.
skuPublic catalog SKU from the product page. Null when the price was not...
pricePublic price kept from the product page, with two decimal places. Nul...
currencyISO currency code from the product page.
previousPriceSaved price when this row is a price change. Null otherwise.
previousCurrencySaved currency when this row is a price change. Null otherwise.
sourceZeeman when a public price was kept. Null when nothing was stored.
chargeOutcomesucceeded only when Actor.charge() covered the event. ignored when th...
inputThe product URL as entered.
urlNormalized https://www.zeeman.com product URL. Null for an invalid line.
httpStatusHTTP status from the product page. Null when no product request was m...
checkedAtWhen this row was handled, ISO 8601.
chargedTrue only when Actor.charge() returned a chargedCount that covered ev...
messageWhat changed, or why the price was not stored.

Field examples declared in the dataset schema shipped with this Actor. They are not a newly invented row.

{
"recordType": "product",
"status": "baseline_saved",
"productName": "Handdoek - Bruin",
"sku": "109128-1",
"price": "1.00",
"currency": "EUR",
"previousPrice": null,
"previousCurrency": null,
"source": "Zeeman",
"chargeOutcome": "ignored",
"input": "https://www.zeeman.com/nl-nl/product/handdoek-bruin-109128-1",
"url": "https://www.zeeman.com/nl-nl/product/handdoek-bruin-109128-1",
"httpStatus": 200,
"checkedAt": "2026-11-08T12:00:00.000Z",
"charged": false,
"message": "Baseline saved."
}

🔌 How do you call this Actor from the API?

Call mmdincer/zeeman-product-price-monitor with the Apify API. The body is the input schema. MCP clients on Apify use the same input. Make and Zapier can start the Actor through Apify's integration. The input is the same JSON.

from apify_client import ApifyClient
client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("mmdincer/zeeman-product-price-monitor").call(run_input={"productUrls": ["https://www.zeeman.com/nl-nl/product/handdoek-bruin-109128-1"], "onlyChanges": false, "monitorName": "default"})
items = client.dataset(run["defaultDatasetId"]).list_items().items
import { ApifyClient } from "apify-client";
const client = new ApifyClient({ token: "<APIFY_TOKEN>" });
const run = await client.actor("mmdincer/zeeman-product-price-monitor").call({"productUrls": ["https://www.zeeman.com/nl-nl/product/handdoek-bruin-109128-1"], "onlyChanges": false, "monitorName": "default"});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

❓ What else should you know?

Does the Zeeman price monitor need a login?

The sample run uses the public source and the prefilled input. A field that asks for your own key is optional unless the input schema marks it required.

What does the Zeeman price monitor charge for?

The primary event in the live price list is product-checked (Product page read). Actor Start is separate. An event the source does not call is not billed by the source.

Can this Actor run on a schedule?

Yes. Save the input and schedule it. The next run compares against the baseline when the source stores one.

Where do the results go?

Results land in the run dataset. Download JSON, CSV or Excel, or read them with the API.

You are responsible for the source terms and for privacy law that applies to you, including the GDPR if you handle personal data. This Actor stores the public fields described above. The source checks robots.txt before a fetch when that check is in the code. This Actor is not affiliated with Zeeman.

Not affiliated with Zeeman. Source license: Apache-2.0. The price figures in the table were not sent to the pricing API by this Actor's source code. Actor.charge bills the events named above. The git file pricing-ppe.json still lists price-changed at $0.0025 on Platinum and $0.002 on Diamond. Those two file cells are not the live prices. The live Platinum and Diamond price for price-changed is $0.0029. Where the source checks robots.txt, a disallowed URL is not fetched as a normal result. An HTTP 403 from the product host is not stored as a kept price. A row can contain charged: false when Actor.charge did not bill that row.

Other public Actors from mmdincer in this group:

Download the dataset as JSON, CSV or Excel when the run finishes.

The same input can be saved and started again tomorrow.

A status row explains a page that was skipped or blocked.