Log property search results from Searchbug into Google Sheets
Ready for 3.0What this workflow does
This workflow has 17 nodes and runs when someone submits an n8n form (“Property Search”). Along the way it connects Google Sheets. It also calls data.searchbug.com over HTTP.
How it runs
Trigger: When someone submits an n8n form (“Property Search”).
- Single or Bulk? (If): checks a condition and branches into true / false
- Normalize Input (Edit Fields (Set)): sets 3 fields: What, Location, Search Type
- Extract CSV (Extract from File): extracts data from a file
- Set Search Input (Edit Fields (Set)): sets 3 fields: SRCH, WHAT, LOCATION
- Validate Input (If): checks a condition and branches into true / false
- Dedupe Searches (Code): runs custom JavaScript code
- Invalid Input (Edit Fields (Set)): sets 3 fields: message, api_status, what
- Property Search API (HTTP Request): calls data.searchbug.com (POST)
- Check Results (If): checks a condition and branches into true / false
- Attach Search Context (Edit Fields (Set)): sets 5 fields: search_id, searched_type, searched_what…
…plus 6 more steps. See the full node list below.
Services it uses
HTTP calls to: data.searchbug.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)
- n8n Form Trigger
n8n-nodes-base.formTrigger - If
n8n-nodes-base.if - Extract from File
n8n-nodes-base.extractFromFile - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - Google Sheets
n8n-nodes-base.googleSheets
From the author
Quick overview This workflow collects property search criteria via an n8n form, queries the Searchbug Property Search API (apiprop) for matching records, and appends detailed property fields (owner, parcel, values, mailing address, and land data) to a Google…