HumationHuman + Automation
Back to Catalog

Extract Zillow property data to Google Sheets with Scrape.do

OnurOnur
218 views
2/3/2026
File ManagementGoogle DriveAutomationAttachmentsEmail
Official Page

🏠 Extract Zillow Property Data to Google Sheets with Scrape.do

This template requires a self-hosted n8n instance to run.

A complete n8n automation that extracts property listing data from Zillow URLs using Scrape.do web scraping API, parses key property information, and saves structured results into Google Sheets for real estate analysis, market research, and property tracking.

📋 Overview

This workflow provides a lightweight real estate data extraction solution that pulls property details from Zillow listings and organizes them into a structured spreadsheet. Ideal for real estate professionals, investors, market analysts, and property managers who need automated property data collection without manual effort.

Who is this for?

  • Real estate investors tracking properties
  • Market analysts conducting property research
  • Real estate agents monitoring listings
  • Property managers organizing data
  • Data analysts building real estate databases

What problem does this workflow solve?

  • Eliminates manual copy-paste from Zillow
  • Processes multiple property URLs in bulk
  • Extracts structured data (price, address, zestimate, etc.)
  • Automates saving results into Google Sheets
  • Ensures repeatable & consistent data collection

⚙️ What this workflow does

  1. Manual Trigger → Starts the workflow manually
  2. Read Zillow URLs from Google Sheets → Reads property URLs from a Google Sheet
  3. Scrape Zillow URL via Scrape.do → Fetches full HTML from Zillow (bypasses PerimeterX protection)
  4. Parse Zillow Data → Extracts structured property information from HTML
  5. Write Results to Google Sheets → Saves parsed data into a results sheet

📊 Output Data Points

| Field | Description | Example | |-------|-------------|---------| | URL | Original Zillow listing URL | https://www.zillow.com/homedetails/... | | Price | Property listing price | $300,000 | | Address | Street address | 8926 Silver City | | City | City name | San Antonio | | State | State abbreviation | TX | | Days on Zillow | How long listed | 5 | | Zestimate | Zillow's estimated value | $297,800 | | Scraped At | Timestamp of extraction | 2025-01-29T12:00:00.000Z |

⚙️ Setup

Prerequisites

Google Sheet Structure

This workflow uses one Google Sheet with two tabs:

Input Tab: "Sheet1"

| Column | Type | Description | Example | |--------|------|-------------|---------| | URLs | URL | Zillow listing URL | https://www.zillow.com/homedetails/123... |

Output Tab: "Results"

| Column | Type | Description | Example | |--------|------|-------------|---------| | URL | URL | Original listing URL | https://www.zillow.com/homedetails/... | | Price | Text | Property price | $300,000 | | Address | Text | Street address | 8926 Silver City | | City | Text | City name | San Antonio | | State | Text | State code | TX | | Days on Zillow | Number | Days listed | 5 | | Zestimate | Text | Estimated value | $297,800 | | Scraped At | Timestamp | When scraped | 2025-01-29T12:00:00.000Z |

🛠 Step-by-Step Setup

  1. Import Workflow: Copy the JSON → n8n → Workflows → + Add → Import from JSON

  2. Configure Scrape.do API:

    • Sign up at Scrape.do Dashboard
    • Get your API token
    • In HTTP Request node, replace YOUR_SCRAPE_DO_TOKEN with your actual token
    • The workflow uses super=true for premium residential proxies (10 credits per request)

  3. Configure Google Sheets:

    • Create a new Google Sheet
    • Add two tabs: "Sheet1" (input) and "Results" (output)
    • In Sheet1, add header "URLs" in cell A1
    • Add Zillow URLs starting from A2
    • Set up Google Sheets OAuth2 credentials in n8n
    • Replace YOUR_SPREADSHEET_ID with your actual Google Sheet ID
    • Replace YOUR_GOOGLE_SHEETS_CREDENTIAL_ID with your credential ID

  4. Run & Test:

    • Add 1-2 test Zillow URLs in Sheet1
    • Click "Execute workflow"
    • Check results in Results tab

🧰 How to Customize

  • Add more fields: Extend parsing logic in "Parse Zillow Data" node to capture additional data (bedrooms, bathrooms, square footage)
  • Filtering: Add conditions to skip certain properties or price ranges
  • Rate Limiting: Insert a Wait node between requests if processing many URLs
  • Error Handling: Add error branches to handle failed scrapes gracefully
  • Scheduling: Replace Manual Trigger with Schedule Trigger for automated daily/weekly runs

📊 Use Cases

  • Investment Analysis: Track property prices and zestimates over time
  • Market Research: Analyze listing trends in specific neighborhoods
  • Portfolio Management: Monitor properties for sale in target areas
  • Competitive Analysis: Compare similar properties across locations
  • Lead Generation: Build databases of properties matching specific criteria

📈 Performance & Limits

  • Single Property: ~5-10 seconds per URL
  • Batch of 10: 1-2 minutes typical
  • Large Sets (50+): 5-10 minutes depending on Scrape.do credits
  • API Calls: 1 Scrape.do request per URL (10 credits with super=true)
  • Reliability: 95%+ success rate with premium proxies

🧩 Troubleshooting

| Problem | Solution | |---------|----------| | API error 400 | Check your Scrape.do token and credits | | URL showing "undefined" | Verify Google Sheet column name is "URLs" (capital U) | | No data parsed | Check if Zillow changed their HTML structure | | Permission denied | Re-authenticate Google Sheets OAuth2 in n8n | | 50000 character error | Verify Parse Zillow Data code is extracting fields, not returning raw HTML | | Price shows HTML/CSS | Update price extraction regex in Parse Zillow Data node |

🤝 Support & Community

🎯 Final Notes

This workflow provides a repeatable foundation for extracting Zillow property data with Scrape.do and saving to Google Sheets. You can extend it with:

  • Historical tracking (append timestamps)
  • Price change alerts (compare with previous scrapes)
  • Multi-platform scraping (Redfin, Realtor.com)
  • Integration with CRM or reporting dashboards

Important: Scrape.do handles all anti-bot bypassing (PerimeterX, CAPTCHAs) automatically with rotating residential proxies, so you only pay for successful requests. Always use super=true parameter for Zillow to ensure high success rates.

Extract Zillow Property Data to Google Sheets with Scrapedo

This n8n workflow automates the process of extracting Zillow property data using a web scraping API and then storing that data in a Google Sheet. It's designed to be manually triggered, allowing you to fetch property details on demand.

What it does

This workflow performs the following key steps:

  1. Manual Trigger: Initiates the workflow when you click "Execute workflow" in n8n.
  2. HTTP Request (Scrapedo API): Makes an API call to the Scrapedo service to scrape Zillow property data. This node is configured to send a request to a specific URL, likely a Zillow property page, and retrieve its structured data.
  3. Code (Data Transformation): Processes the data received from the Scrapedo API. This JavaScript code node is responsible for parsing the scraped JSON, extracting relevant property fields, and formatting them into a structure suitable for Google Sheets.
  4. If (Conditional Logic): Evaluates the processed data. This node likely checks if the data extraction was successful or if certain key fields are present before proceeding to write to Google Sheets.
  5. Google Sheets (Write Data): If the data passes the conditional check, this node appends the extracted property data as a new row to a specified Google Sheet.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Scrapedo Account & API Key: An account with Scrapedo (or a similar web scraping API) and its corresponding API key to make HTTP requests. The HTTP Request node will need to be configured with the correct endpoint and authentication for Scrapedo.
  • Google Account: A Google account with access to Google Sheets.
  • Google Sheets Credential: An n8n credential configured for Google Sheets to allow the workflow to write data to your spreadsheet.
  • Target Google Sheet: A Google Sheet where the extracted property data will be stored. You will need to specify the Spreadsheet ID and Sheet Name in the Google Sheets node.

Setup/Usage

  1. Import the workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • Set up a Google Sheets credential in n8n if you haven't already.
  3. Configure Nodes:
    • HTTP Request:
      • Update the URL parameter to point to the Scrapedo API endpoint.
      • Add any necessary Headers or Query Parameters for authentication (e.g., your Scrapedo API key).
      • Ensure the Request Method is set correctly (likely GET).
      • The URL for Zillow should be dynamic, passed from a previous node or manually entered for testing.
    • Code: Review the JavaScript code to ensure it correctly parses the output from your Scrapedo API and extracts the desired Zillow property fields. Adjust the parsing logic if your Scrapedo output format differs.
    • If: Review the conditions in the If node to ensure it correctly validates the data before writing to Google Sheets.
    • Google Sheets:
      • Select your configured Google Sheets credential.
      • Specify the Spreadsheet ID of your target Google Sheet.
      • Enter the Sheet Name where the data should be appended.
      • Ensure the Operation is set to Append Row.
  4. Execute the workflow: Click the "Execute workflow" button on the "Manual Trigger" node to run the workflow and test the data extraction and saving process. You may need to manually provide the Zillow URL for the HTTP Request node during testing.

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 invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942