Realty Scraper: turning Zillow searches into automation triggers

Problem

Most Zillow export tools stop at CSV. That is useful, but it still leaves a person doing the next step: downloading the file, cleaning it, uploading it somewhere else, mapping columns, and starting the campaign by hand.

For a service business, the spreadsheet is not the point. The point is getting the right addresses into the next system while the timing still matters.

How I use it at Vent Busters

My own workflow sends recently sold homes from Realty Scraper to self-hosted n8n. The n8n flow parses the webhook payload, filters the homes I care about, and sends the mailing data to LettrLabs for a postcard campaign.

The timing matters. I target homes that sold more than 30 days ago because closing usually takes about a month. New homeowners are already in repair mode. They are finding problems, setting up services, and spending money on the house. Dryer vent cleaning is easy to miss, especially when the previous homeowner may never have done it.

The geography matters too. I can focus on neighborhoods and communities that fit the kind of work Vent Busters wants, then let the campaign feed areas that work with the Serenity schedule instead of scattering leads across the map.

Product shape

Realty Scraper runs as an in-page panel on Zillow search pages. Free users can scrape the current search with core listing fields. Pro users unlock more pages, optional detail scraping, the full column set, and webhook export.

The extension is listed on both the Chrome Web Store and Firefox Add-ons. The account portal at realtyscraper.iohandles signup, Helcim recurring billing, license keys, device binding, and support tickets.

Pro webhook export

Pro users configure an HTTPS webhook URL and optional secret in the extension settings. A scrape can then send one JSON payload directly to that endpoint. The listing data is not relayed through Realty Scraper servers.

The payload includes the event name, version, export id, source Zillow URL, listing count, and listings[]. Pro exports use the full column set, including sold date, detail fields, geo fields, contact fields when Zillow exposes them, and the original listing URL.

Chrome requires one extra step: when the user saves a webhook URL, the extension requests host permission for that endpoint. After that, the background service worker sends the POST because Zillow's page context blocks outbound fetches through CSP.

Closing the loop with Serenity

The next step is tying this directly into Serenity. When a postcard goes out, Serenity can know which address received it. If that homeowner books later, the booking can be flagged and attributed back to the campaign.

That makes the flow more useful than a mailing list export. Zillow finds the homes. Realty Scraper turns the search into a payload. n8n routes the data. LettrLabs handles printing and mailing. Serenity can track the address, booking, route, and campaign result.

• Zillow search → Realty Scraper scrape
• Pro webhook → n8n workflow
• n8n → LettrLabs postcard campaign
• Serenity → attribution, booking analytics, and schedule context