HumationHuman + Automation
Back to Catalog

Scrape property listings from Zillow with Olostep API and store in data tables

Yasser SamiYasser Sami
232 views
2/3/2026
WebhookAutomationEmailDatabaseCRM
Official Page

Zillow Property Scraper Using Olostep API

This n8n template automates Zillow property data collection by scraping Zillow search results using the Olostep API.
It extracts property price, link to listing, and location, removes duplicates, and stores everything in a Google Sheet or Data Table.

Who’s it for

  • Real estate analysts and investors researching property markets.
  • Lead generators needing structured Zillow data.
  • Freelancers and automation builders collecting housing listings.
  • Anyone needing fast, clean Zillow data without manual scraping.

How it works / What it does

  1. Form Trigger

    • User enters a Zillow search URL.
    • This becomes the base Zillow search URL.

  2. Pagination Logic

    • A list of page numbers (1–7) is generated.
    • Each number is used to load the next Zillow search page.

  3. Scrape Zillow Pages with Olostep

    • For each page, the Olostep API scrapes the Zillow results.
    • Olostep’s LLM extraction schema extracts:
      • price
      • url (link to the Zillow listing)
      • location

  4. Parse & Split Results

    • Returned JSON is cleaned and converted into individual listing items.

  5. Remove Duplicates

    • Ensures each Zillow listing appears only once.

  6. Insert into Google Sheet / Data Table

    • Final cleaned listings are inserted row-by-row.
    • Perfect for filtering, exporting, or further analysis.

This workflow gives you a fast, scalable property scraper using Zillow + Olostep — no browser automation, no manual copy/paste.

How to set up

  1. Import the template into n8n.
  2. Add your Olostep API key.
  3. Connect your Google Sheet or n8n Data Table.
  4. Deploy the form and start scraping by entering a place name.

Requirements

  • Olostep API key
  • Google Sheets account or Data Table
  • n8n cloud or self-hosted instance

How to customize the workflow

  • Add more pages to the pagination array (e.g., 1–20).
  • Expand the LLM extraction schema to include:
    • number of bedrooms
    • number of bathrooms
    • square footage
    • property type
  • Trigger via Telegram or API instead of a form.
  • Send results to Airtable or Notion instead of Google Sheets.

👉 This template gives you an automated Zillow scraper powered by AI extraction — perfect for real estate lead gen or market research.

Scrape Property Listings from Zillow with Olostep API and Store in Data Tables

This n8n workflow demonstrates how to integrate with the Olostep API to scrape property listings from Zillow and then store the extracted data into an n8n Data Table. It's designed to be triggered manually or via a form submission, allowing for flexible data collection and storage.

What it does

This workflow automates the following steps:

  1. Triggers on Form Submission: The workflow starts when an n8n form is submitted. This form likely contains parameters for the Zillow scraping (e.g., search query, location).
  2. Edits Fields: It prepares the incoming data, potentially transforming or adding fields required for the API request.
  3. Makes an HTTP Request to Olostep API: It sends an HTTP GET request to the Olostep API, using the prepared data to query Zillow for property listings.
  4. Loops Over Items: The workflow then processes the response from the Olostep API, iterating through each property listing returned.
  5. Splits Out Data: For each property listing, it extracts specific fields or nested data into individual items.
  6. Stores Data in a Data Table: Finally, it saves the processed property listing data into an n8n Data Table for structured storage and easy access.
  7. Provides Notes: Includes a sticky note for additional context or instructions within the workflow.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • Olostep API Key: An API key for the Olostep service, which is used to scrape Zillow.
  • n8n Form: An n8n form configured to trigger this workflow.
  • n8n Data Table: An n8n Data Table configured to store the scraped property listing data.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Olostep API Key:
    • Locate the "HTTP Request" node.
    • Configure the credentials for your Olostep API key.
  3. Configure n8n Form:
    • Locate the "On form submission" (n8n Form Trigger) node.
    • Ensure your n8n form is correctly set up to send the necessary input to this workflow (e.g., Zillow search parameters).
  4. Configure Data Table:
    • Locate the "Data table" node.
    • Specify the name of your n8n Data Table where the property listings will be stored.
    • Ensure the Data Table schema matches the data you intend to store from the Zillow listings.
  5. Activate the Workflow: Once configured, activate the workflow.
  6. Trigger the Workflow: Submit the n8n form to initiate the Zillow scraping process. The scraped data will then be populated into your specified n8n Data Table.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247