Monitor foreclosure listings by ZIP with Google Sheets and Gmail
Ready for 3.0What this workflow does
This workflow has 14 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Google Sheets and Gmail. It also calls foreclosure-finder1.p.rapidapi.com over HTTP.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Watchlist settings (Edit Fields (Set)): sets 10 fields: zipcode, radius, minPrice…
- Validate settings (Code): runs custom JavaScript code
- Search five sources (HTTP Request): calls foreclosure-finder1.p.rapidapi.com (GET)
- Validate complete scan (Code): runs custom JavaScript code
- Read watchlist history (Google Sheets): read (sheet)
- Find unnotified matches (Code): runs custom JavaScript code
- Save pending matches (Google Sheets): append or update (sheet)
- Build email preview (Code): runs custom JavaScript code
- Release email if enabled (Code): runs custom JavaScript code
- Send watchlist email (Gmail): send (message)
…plus 2 more steps. See the full node list below.
Services it uses
HTTP calls to: foreclosure-finder1.p.rapidapi.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Manual Trigger
n8n-nodes-base.manualTrigger - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - Google Sheets
n8n-nodes-base.googleSheets - Gmail
n8n-nodes-base.gmail
From the author
Quick overview Build a daily ZIP-code property watchlist with Foreclosure Finder on RapidAPI, Google Sheets and Gmail. Save source-deduplicated matches and optionally email records not yet marked notified. This preview starts inactive with email disabled. How…