Real Estate Market Scanning
Configured with Email Send, Filter, HTTP Request, Schedule Trigger, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Transform
- Web / API
- Code
- Routing
- Messaging
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Schedule Market Scan | Trigger | Schedule Trigger | See node parameters |
| BatchData API Configuration | Transform | Edit Fields | See node parameters |
| Query BatchData Properties | Web / API | HTTP Request | POST |
| Get Previous Results | Code | Code | See node parameters |
| Compare Results | Code | Code | See node parameters |
| Split Properties | Transform | Split Out | See node parameters |
| Filter High Potential | Routing | Filter | See node parameters |
| Get Property Details | Web / API | HTTP Request | See node parameters |
| Format Email Content | Transform | Edit Fields | See node parameters |
| Send Email Alert | Messaging | Email Send | See node parameters |
| Post to Slack | Messaging | Slack | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
Main Workflow Flow
Main Workflow Flow
This part of the workflow handles the regular scanning and processing of property data. It runs on a schedule to detect new properties or changes to existing ones, then passes the filtered results along for detailed analysis.
Property Filtering & Analysis
Property Filtering & Analysis
Here we filter the properties based on criteria for high-potential leads (high equity %, absentee owners, etc.) and fetch detailed information about each property to prepare comprehensive reports for the sales team.
Notifications
Notifications
This section delivers the property leads to the sales team through multiple channels:
- Email alerts with detailed property and owner information
- Slack notifications for quick updates
Both include Google Maps links to quickly view the property location.
Setup Instructions
Setup Instructions
-
API Keys & Credentials:
- Add your BatchData API Key to the BatchData API Configuration node
- Set up SMTP credentials for email delivery
- Configure Slack API credentials for team notifications
-
Customize Search Parameters:
- Adjust property search criteria in the BatchData API Configuration node
- Modify the filtering conditions in the Filter High Potential node
-
Notification Recipients:
- Update email recipients in the Send Email Alert node
- Set appropriate Slack channel in the Post to Slack node
Real Estate Market Scanning
Real Estate Market Scanning
Purpose and structure
This folder contains the Real Estate Market Scanning workflow. Its executable nodes use code, emailSend, filter, httpRequest, scheduleTrigger, set, slack, splitOut. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Schedule Market Scan
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Splitout/1748_Splitout_Code_Automation_Webhook.json MIT; preserve source notices.