Tech
Why n8n Workflows Drop Idealista Data When Runs Exceed 300 Seconds
Why n8n Workflows Drop Idealista Data When Runs Exceed 300 Seconds
When orchestrating web scrapers inside a production data pipeline, developers often default to synchronous webhook patterns. You configure an HTTP request node in n8n, point it to the Apify API run-sync endpoint, and wait for the payload to return. This simple pattern breaks down when scraping real estate listings from platforms like Idealista.
The idealista-scraper is designed to handle pagination, mirror-first routing,...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to