Skip to content

Field notes03 of 04

Property data on every record

Fifteen custom cards that put property, valuation, sale history, area and map data on HubSpot deal and company records, with the property data behind a signed, cached Worker.

System
Property data cards in HubSpot
Stack
HubSpot UI extensions · React · TypeScript · Cloudflare Workers · Workers KV · Census ACS API
FIG. 01PROPERTY CARDS10:15 CTSample HubSpot deal record for a retail property with four sidebar cards: property overview, valuation and tax, sale history and area snapshot.

Figures show illustrative sample data. Names, companies and values in them are invented.

01

The situation

For this client a deal is a property, and the facts that decide it (size, value, tax, sale history, debt, the area around it) lived outside the CRM. The data provider keys every record on its own address spelling: of seven plausible spellings of one test address, five returned nothing. A blank lookup could mean an uninteresting property or a wrong string, and nobody could tell which.

HubSpot had its own trap. 31 of the 61 custom deal properties, the address fields among them, turned out to be read-only rollups that mirror the deal's primary company. Writing to them through the API returns success and stores nothing.

  1. Component 1: Four property cards

    Property overview, valuation and tax, sale history, and mortgage and owner, on deal and company records, built in React with HubSpot's UI extensions SDK. The cards run in HubSpot's sandbox and reach outside only through signed fetches.

  2. Component 2: Area and map cards

    Nine census cards for the record's area (population, income, education, housing, commute and more), plus a street-view card and a campaign KPI card.

  3. Component 3: A signed, cached proxy

    A Cloudflare Worker checks HubSpot's v3 signature on every request, maps each card to the right provider endpoint, and caches successful answers in Workers KV: 30 days for property and valuation, 14 for sales and mortgage. 38% of card calls repeat an address and data type across days, and each repeat is served from the cache instead of a new metered call.

  4. Component 4: One address, several records

    When the provider returns several records for one address, the Worker fetches each by its own ID, picks the single improved record as primary when there is exactly one, and returns every record separately. It never sums them.

  5. Component 5: Signed intake

    A second Worker creates the company and deal for an address resolved against the provider: duplicate searches before and after the company is created, a lock against double submits, the address written to the company the deal mirrors, and a 401 for any unsigned request, with no setting that turns that off.

03Stack

  • HubSpot UI extensions
  • React
  • TypeScript
  • Cloudflare Workers
  • Workers KV
  • Census ACS API

04

Results

  • 15 cards on deal and company records across four HubSpot apps.

  • 1,500+ assertions in the property Worker's test suite, run in plain Node with no network.

  • Repeat lookups served from a cache every Cloudflare location can read, instead of a new metered call.

  • Address data written where HubSpot actually keeps it, so it shows on the deal instead of silently disappearing.

  • Every request to the write Worker signature-checked. There is no unsigned mode.

Your system could be the next note.

Bring the part of your business the CRM can't see yet. We'll show you how we build it.