Klaviyo and Webhook: Saved-Search Property Alert Template

When a new listing matches a buyer's saved-search criteria, this Spojit template fires a Klaviyo event so a property-alert email reaches them within minutes.

What It Builds

A Webhook trigger receives each new listing as it is published. A Connector node in Agent mode reads the listing details and checks them against your buyers' saved-search criteria (price range, beds, suburb, property type), using a Response Schema to return a clean list of matching contacts. For each match, a Klaviyo Connector node sends a custom event so your existing property-alert flow delivers the email automatically.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow that triggers on a webhook whenever a new property listing is published. Compare the listing's price, bedrooms, suburb, and property type against my buyers' saved-search criteria, and for each buyer it matches, send a Klaviyo event called "saved_search_match" with the listing address, price, and a link so their property-alert email flow sends them the match.

Connectors Used

  • Webhook trigger - starts the run each time a new listing is published from your portal or MLS.
  • Klaviyo - sends the custom event that fires your property-alert email flow.
  • HTTP - if your saved-search records live in a portal or CRM without a native tile, Miraxa connects to its API to look them up.

Customize It

Change the matched fields (add lot size or price-drop), rename the Klaviyo event to match your flow's trigger, or adjust which listing details ride along in the event so your email template can render them.

Tips

  • Give your Klaviyo connection write access to events and profiles before running.
  • Use the Connector node's Response Schema so matches always come back as structured JSON you can loop over.
  • Send one event per matching buyer so each person enters the Klaviyo flow independently.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.