Idealista Scraper - Real Estate Data for Spain, Italy, Portugal
Pricing
$19.00/month + usage
Idealista Scraper - Real Estate Data for Spain, Italy, Portugal
Extract real estate data from Spain, Italy, and Portugal on idealista.com, including pricing, property features, and contact information. Scrape listings for residential, office, and commercial properties available for sale or rent.
0.0 (0)
Pricing
$19.00/month + usage
20
Total users
233
Monthly users
81
Runs succeeded
>99%
Issues response
2.9 days
Last modified
a month ago
Dataset ID / Name won’t stick between periodic runs even if included in input JSON
Open
First, thanks for the actor—it’s very useful!
-
I add in the JSON input: "datasetId": "bnwJkd2HczSy0fEiW", "datasetName": "idealista_madrid_daily"
-
I save the task and run it later (manual or scheduled) → the actor still creates a new dataset instead of re-using the one I set.
-
Extra glitch: if I switch to Manual Input (form view), tweak any field (location, min size, etc.) and save, then switch back to JSON view, the two lines setting datasetId / datasetName have disappeared.
Could you make those fields persistent and make every run honor them? That would let me keep all results in a single dataset for my automation.
Iñigo Garcia Olaizola (igolaizola)
Because the actor's input schema doesn't define a datasetId (or datasetName) property, anything you inject by hand in JSON will be stripped out whenever the form generator rebuilds the inputs. That's also why, when you switch to form view and back, those lines vanish: the UI only knows about the "official" fields.
To implement this I need to add new input parameter (e.g. datasetId or datasetName) to the actor's spec, and then wire them through so that, at run time, the actor checks for an existing dataset and appends to it instead of always creating a new one. I'll take a look now at how much work it is to add those inputs and hook the dataset-lookup logic in.
Thanks for the suggestion!
Gaerasmus
Thanks a lot Iñigo! Super clear the reason why it is working that way. And thanks for looking into option of adding datasetID into Input parameters. I hope it is not a lot of work so you can add it. I think it is useful for periodic tasks. In my case, I would prefer if instead of appending, would completely replace data since the appending I do it at the receiving end. For me it would help a lot since I found some data challenges on the Zapier side to connect at task level and using same datasetID would make it much more stable. Fingers crossed and thanks again!
