Regrid Integration
Data & Market IntelligenceWhat It Does
Regrid (formerly Loveland Technologies) is a nationwide parcel-data platform built around the legal boundary of the parcel rather than the mailing address. It standardizes records from more than 3,000 U.S. counties into a single schema covering parcel geometry, the owner of record, situs and mailing addresses, assessed and market values, land-use and zoning classifications, lot dimensions, and a deep set of standardized parcel attributes — across 150M+ parcels nationwide.
Why Real Estate Professionals Use It
Off-market sourcing and site analysis both begin at the parcel, not the listing. Before there is a deal, there is a boundary, an owner of record, and a zoning designation — and assembling those three things across a market has historically meant toggling between a county GIS viewer, an assessor portal, and a recorder's office, parcel by parcel. Regrid collapses that into a spatial query: draw a polygon around a corridor or pass a radius around an anchor asset, and the Parcel API returns every parcel inside it with owner, zoning, and lot attributes attached. For a team running [/solutions/off-market-deal-sourcing](/solutions/off-market-deal-sourcing), that is the difference between a week of manual GIS work and a scored prospecting list by lunch.
AI Solutions for Data
Ebook
CTO's Guide to AI Implementation
Technical framework for CTOs evaluating AI solutions with Build vs Buy analysis
Solution
Property Data Enrichment
Auto-enrich contacts with property ownership, tax records, and market data
Solution
Universal CRM Sync Hub
Keep HubSpot, Follow Up Boss, Salesforce, and spreadsheets in perfect sync
Key Features for Real Estate
Discover how Regrid powers real estate automation workflows
1 of 7
Feature
Parcel Boundary Geometry (GeoJSON)
Every Regrid record carries the legal parcel boundary as a GeoJSON polygon, normalized from county GIS sources into a consistent coordinate system and schema across 3,000+ counties.
Real Estate Impact
Boundary geometry is the foundation of site selection and assemblage analysis. Render target parcels on a market map, measure true lot area and frontage, and detect when contiguous parcels share an owner — none of which is possible from an address-only data feed.
See how we automate Regrid
Get a personalized plan for your tech stack
Automation Workflows
Ready-to-deploy workflows powered by Regrid + NextAutomation
Workflow 1 of 4
Advanced
Target Area Scan → Matching Parcels + Owners → Prospecting List
On a defined cadence, this workflow runs a spatial query over your target corridor or polygon, filters the returned parcels to your buy-box (zoning, minimum lot size, land-use), enriches each with owner and mailing address, scores them, and drops a ranked prospecting list into a Google Sheet for the sourcing sprint.
Trigger: Scheduled weekly run (Monday 7:00 AM) via n8n cron, scoped to one or more target-area polygons
Workflow Steps
1n8n cron fires and loads the target-area polygon(s) from a config sheet or Airtable base
2Call the Regrid Parcel API with the polygon (or bounding box) to retrieve all intersecting parcels as GeoJSON with attributes
3Filter parcels to the buy-box: matching zoning/land-use codes, lot size above minimum, and excluded use categories removed
4For each qualifying parcel, extract owner name, entity type, situs address, and mailing address
+4 more steps
Each sourcing sprint starts with a ranked, parcel-level prospecting list built from boundaries and owners — not a manual crawl of the county GIS viewer. Absentee, by-right, individually-owned parcels rise to the top automatically.
Triggers & Actions
Connect Regrid to your workflows with powerful triggers and actions
Triggers
Actions
Lookup Parcel by Point
Query the Regrid Parcel API with a latitude/longitude coordinate to resolve the parcel containing that point and return its GeoJSON boundary and attribute record.
When a site visitor drops a map pin on a vacant lot, resolve the exact parcel, owner, and zoning from the coordinate before they leave the property.
Lookup Parcel by Address
Resolve a street address to its canonical Regrid parcel, returning the parcel identifier, boundary polygon, and full attribute set.
When a broker emails an off-market teaser with only an address, resolve it to the parcel record to pre-populate the deal card with owner, zoning, and lot size.
Query Parcels by Polygon or Bounding Box
Submit a drawn polygon or a bounding box to retrieve every parcel that intersects the geometry, each with boundary and attributes — the spatial primitive for market and corridor scans.
Pass a polygon over a redevelopment corridor and pull the complete parcel set in one call to seed a weekly prospecting list.
Query Parcels by Radius
Retrieve all parcels within a configurable radius of a coordinate, returning geometry and attributes for each.
Pull every parcel within a half-mile of a newly announced transit stop to identify owners who may be open to a transit-oriented development play.
Fetch Owner of Record
Retrieve the current owner name, entity type where derivable, situs address, and mailing address for a parcel by ID, point, or address.
After a market scan flags a target parcel, pull the owner of record to determine whether it is an institution or an absentee individual before starting outreach.
Fetch Zoning and Land-Use
Retrieve the parcel's land-use code and zoning designation where published, normalized into Regrid's standardized use categories.
Filter a sourcing list to parcels zoned for multifamily and auto-flag which sites permit your intended density by right versus those needing a variance.
Fetch Parcel Boundary (GeoJSON)
Retrieve the legal boundary polygon for a parcel as GeoJSON, suitable for mapping, area calculation, or contiguity analysis.
Store the boundary on a deal record so it renders on the portfolio map and supports assemblage adjacency checks against neighboring parcels.
Fetch Parcel Attributes
Retrieve standardized attributes — lot size, assessed and market values, land-and-improvement splits, year built where available, and county fields — for any parcel.
Screen candidates by minimum lot size and land-to-improvement ratio to surface land-rich redevelopment parcels in a target submarket.
Load Parcel Vector Tiles
Configure Regrid's MVT endpoint as a tile source in Mapbox GL, MapLibre, or Leaflet to render the parcel layer interactively with click-to-inspect attributes.
Embed an interactive parcel map inside an investor dashboard so partners can click any holding and see owner, zoning, and lot size in context.
Batch Resolve Parcels
Submit a list of addresses or coordinates and receive their resolved parcel records in bulk, reducing per-call overhead on large sourcing lists.
After a corridor scan returns hundreds of candidate addresses, resolve them all to parcels in a batch job rather than issuing sequential lookups.
Setup Guide
Get started in approximately 45 minutes for token setup and the first point lookup; 2-3 hours for a full parcel-enrichment and spatial-scan workflow suite, plus 1-2 hours to wire the vector-tile map layer
Prerequisites
- Regrid account with API access (sign up at regrid.com; the Parcel API and tiles are provisioned on a paid plan — confirm parcel coverage and tile access for your markets with Regrid)
- Regrid API token (bearer token issued from your Regrid account dashboard) passed on every request
- n8n instance (cloud or self-hosted) with the HTTP Request node — Regrid uses standard REST/GeoJSON, so no dedicated node is required
- A CRM or spreadsheet destination (HubSpot, Salesforce, Airtable, or Google Sheets) for enriched parcel records
- For maps: a tile-aware map library (Mapbox GL, MapLibre, or Leaflet) configured to consume Regrid's vector tiles
- Basic familiarity with GeoJSON and REST authentication headers
1
Provision Your Regrid Account and Retrieve Your API Token
Sign up at regrid.com and select a plan that includes Parcel API and tile access for your target markets. In your account dashboard, locate the API tokens section and copy your bearer token. You will pass it on every request, typically as an Authorization header or a token query parameter per Regrid's documentation.
Confirm parcel coverage for your specific counties before building. Regrid's national coverage is broad, but attribute depth (especially zoning) varies by county — verify the markets you actually source in return the fields you depend on.
2
Test the Parcel API with a Single Point Lookup
Before building any workflow, confirm your token works. In n8n, add an HTTP Request node set to GET against Regrid's Parcel API endpoint, passing a known latitude and longitude (or a known address) and your token. Execute the node — you should receive a 200 response with a GeoJSON feature: a boundary polygon plus the parcel's attribute properties.
Save the Regrid token as an n8n credential (Header Auth or query parameter, per Regrid's docs) so you can reuse it across every workflow without re-entering it.
3
Map the GeoJSON Response to Your CRM Fields
Regrid returns a GeoJSON feature where attributes live under the feature's properties object and the boundary lives under geometry. Add a Set or Code node after the HTTP Request to extract the fields you need — owner name, mailing address, zoning/land-use code, lot size, assessed value — and to retain the geometry if you intend to map it. Map these to your CRM's custom fields.
Build a reusable 'Regrid Enrichment' sub-workflow that accepts an address or coordinate and returns a flat object plus the boundary. Reference it from every sourcing and intake workflow so the field mapping lives in one place.
4
Build the Parcel Enrichment Workflow
Create your first end-to-end flow: Trigger (intake form, map pin, or CRM webhook) → HTTP Request (Regrid parcel lookup) → Set node (flatten properties, retain geometry) → CRM node (create or update the record). Run a test with a real parcel in your target market and confirm owner, zoning, lot size, and boundary populate correctly.
Add an error branch after the lookup. Non-standard addresses or parcels in low-coverage counties can return no match — route those to a 'Needs Manual Parcel Match' flag rather than failing the run silently.
5
Configure the Parcel Map Layer with Vector Tiles
To render parcels interactively, add Regrid's MVT endpoint as a vector tile source in your map library (Mapbox GL, MapLibre, or Leaflet). Style the parcel boundary layer in NextAutomation blue (#0049B8), and wire a click handler that calls the Parcel API for the clicked feature to show owner, zoning, and lot size in a popup. This gives any dashboard or deal memo a live parcel layer.
Use vector tiles for the visual layer and the Parcel API for the detail-on-click. Loading every polygon as raw GeoJSON does not scale for a metro; tiles render only what's in the viewport while the API serves attributes on demand.
6
Schedule Your Spatial Sourcing Workflows
For recurring scans (target-area prospecting, same-owner adjacency), add a Cron Trigger at the start of the workflow and load your target polygons from a config sheet. Weekly is typically sufficient for sourcing scans; monthly suits portfolio boundary sync. Activate the workflows and monitor the first runs to verify the spatial query and scoring logic.
Log a count at the end of each run (e.g., '312 parcels in polygon, 41 matched buy-box, 7 absentee-owned') to a Slack message. A sudden drop to zero is your earliest signal that a county's data shape changed or a polygon was misconfigured.
Frequently Asked Questions
Common questions about Regrid integration
Related Integrations
Explore other tools that work great with your workflow
Ready to Automate Regrid?
Get a free AI roadmap showing how to connect Regrid with your existing tools for maximum impact.
Get Your Free AI Roadmap