Zillow data in n8n

How n8n fits

Store the key in a Header Auth credential

Create a credential of type Header Auth. Its Name is the header the API reads and its Value is your key. The HTTP Request node then sends the header on every request, and the key never appears in the node's own fields.

Credential type:  Header Auth
Name:             x-api-key
Value:            <your PropertiesAPI key>

Look up each item with the HTTP Request node

Send address when the item carries a street address, or url when it carries a Zillow link, never both. Never Error and Include Response Headers and Status make an error answer arrive as a normal item with its status code, so the next node can route it instead of the workflow stopping.

Method:                     GET
URL:                        https://api.propertiesapi.com/v1/zillow/property
Authentication:             Generic Credential Type
Generic Auth Type:          Header Auth   (the credential above)
Send Query Parameters:      on
  Specify Query Parameters: Using Fields Below
  Name: address   Value: {{ $json.address }}
      (or  Name: url   Value: {{ $json.zillowLink }})
Options
  Timeout:                  120000
  Response
    Include Response Headers and Status:  on
    Never Error:                          on

Route on the status code and map the fields

With the full response on, each output item has body, headers, statusCode and statusMessage, and the API's JSON sits under body. An If node on statusCode sends found homes one way and errors the other. Failed lookups aren't billed; retry rate_limited and busy answers on a later run, and send address_ambiguous answers to a person with the closest match's Zillow link.

If node condition:  Number > is equal to
  {{ $json.statusCode }}   200

true branch, map fields with expressions:
  Address        {{ $json.body.data.address }}
  Status         {{ $json.body.data.homeStatus }}
  Price          {{ $json.body.data.price }}
  Zestimate      {{ $json.body.data.zestimate }}
  Rent Zestimate {{ $json.body.data.rentZestimate }}
  Zillow link    {{ $json.body.data.detailUrl }}
  From cache     {{ $json.body.meta.cached }}
  Credits used   {{ $json.body.meta.credits }}

false branch, read the error:
  Code           {{ $json.body.error.code }}
  Message        {{ $json.body.error.message }}
  Closest home   {{ $json.body.error.details.candidate.detailUrl }}   (address_ambiguous only)

Batch: many items in one request

The batch endpoint takes up to 50 items per request. An Aggregate node collects the items' addresses into one list, the HTTP Request node posts it, and a Split Out node turns the results back into one item per home, each with ok, data and error. For a longer list, put a Loop Over Items node in front so each pass sends one batch. A full batch can take a few minutes, so raise the timeout.

Aggregate node
  Aggregate:              Individual Fields
  Input Field Name:       address
  Rename Field:           on
  Output Field Name:      items

HTTP Request node
  Method:                 POST
  URL:                    https://api.propertiesapi.com/v1/zillow/batch
  Authentication:         Generic Credential Type, Header Auth (same credential)
  Send Body:              on
  Body Content Type:      JSON
  Specify Body:           Using JSON
  JSON:                   {{ JSON.stringify({ items: $json.items }) }}
  Options > Timeout:      300000

Split Out node
  Field to Split Out:     data

If node:  Boolean > is true   {{ $json.ok }}
  true:   {{ $json.data.address }}, {{ $json.data.price }}, {{ $json.data.zestimate }}
  false:  {{ $json.error.code }}

Longer lists: Loop Over Items (Batch Size 50) in front of the Aggregate node

n8n gotchas

• Send exactly one of url, zpid or address per request. If an item can carry both a link and an address, use an expression that sends the link when there is one and the address otherwise.
• Without Never Error, the first not_found or address_ambiguous answer stops the run. Turn it on as shown, or set the node's On Error setting to Continue (using error output) and handle failed items on the error branch.
• Retry On Fail retries every failure, including answers that won't change, such as not_found. Route on the status code instead and retry only rate_limited and busy answers.
• Fields Zillow doesn't show for a home come back as null, so never read null as zero. Test for it before any arithmetic, for example with an If condition such as Number > is empty.

Keep going

• Zapier (Webhooks)
• Make (HTTP module)
• SDKs and integrations status
• Batch endpoint
• All fields and errors
• Other automation tools

Zillow API and n8n: questions