Since release 21.01, WebChangeMonitor offers an "interpreter" feature that enables to e.g. watch prices on selling/shopping portals or alike.
For example, to watch prices on selling portals (like eb*y), you could do the following (as of today, since eb*y may change the layout):
1.) Setup the items address to the homepage with the offer
2.) Go to the "Content" tab. eb*y encodes the price in a special tag which is what needs to be grabbed. Therefore, setup:
2.1.) Start-tag: <span class="notranslate" id="prcIsum_bidPrice" itemprop="price" content="
2.2.) Stop-tag: ">
3.) Now since we grab the current bid price and this is a float value, enable the the interpreter and setup as following:
3.1.) Data type: Float
3.2.) Condition: Above
3.3.) Value: The price you want to be informed about (e.g. slightly above the value)
4.) You can hit the "Try" button to check the setup
Note that all ignores, white space removals etc. do apply, too, in a normal (interval-based) run, just not for the quick test. So if you need to filter a little more complex, you can do that, too.
Optionally you could setup to run an external command, like mail-send-go, to have an email sent to you on changes. If you provide %guid as parameter, you can attach the [%guid.new] file in the folder for temporary which is the current price as a text file.
Of course, in the same way you could watch price drops, by setting the interpreter condition to "Below" and your desired price as value (e.g. on *m*z*n).
Last edit: Morten MacFly 2020-12-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Since release 21.01, WebChangeMonitor offers an "interpreter" feature that enables to e.g. watch prices on selling/shopping portals or alike.
For example, to watch prices on selling portals (like
eb*y
), you could do the following (as of today, sinceeb*y
may change the layout):1.) Setup the items address to the homepage with the offer
2.) Go to the "Content" tab.
eb*y
encodes the price in a special tag which is what needs to be grabbed. Therefore, setup:2.1.) Start-tag:
<span class="notranslate" id="prcIsum_bidPrice" itemprop="price" content="
2.2.) Stop-tag:
">
3.) Now since we grab the current bid price and this is a float value, enable the the interpreter and setup as following:
3.1.) Data type: Float
3.2.) Condition: Above
3.3.) Value: The price you want to be informed about (e.g. slightly above the value)
4.) You can hit the "Try" button to check the setup
Note that all ignores, white space removals etc. do apply, too, in a normal (interval-based) run, just not for the quick test. So if you need to filter a little more complex, you can do that, too.
Optionally you could setup to run an external command, like mail-send-go, to have an email sent to you on changes. If you provide
%guid
as parameter, you can attach the[%guid.new]
file in the folder for temporary which is the current price as a text file.Of course, in the same way you could watch price drops, by setting the interpreter condition to "Below" and your desired price as value (e.g. on
*m*z*n
).Last edit: Morten MacFly 2020-12-30
It is possible that the site has changed the code of the prices. Now it is
<span class="notranslate" id="prcIsum" itemprop="price" style="text-decoration:none" content="
I'm right?