Home
ES · Ver en español

Work project

Real Estate Landing with a Synced Inventory

The inventory the agency already keeps in Wasi, published every day on its own site

A real estate agency's lead capture site, which shows the properties the company already keeps in Wasi, synced every day before dawn, and takes requests for advice, contact and visits.

Recreation of a fictional agency's listing, with filters by operation, type, city and price, cards with badges and the summary of the last sync with Wasi. (open the full-size image)
Recreated with fictional data; the real system is private.
Recreation of a fictional property's page with its gallery, its facts, the loan calculator and the form to book a visit. (open the full-size image)
Recreated with fictional data; the real system is private.

What it is about

A real estate agency with most of its inventory in Bogotá and nearby towns keeps its properties in Wasi, its real estate software. This site shows them with filters and a page per property, and takes requests for advice, contact and visits.

The interface, the calculators and the request form were built with Lovable. The sync with the Wasi API and the workflows that schedule it and deploy the site are separate code in the same repository. The photos reach Wasi from Zoho CRM through a service of the Zoho toolkit.

What it does

  • Every day before dawn, a GitHub Actions workflow downloads the inventory from the Wasi API, publishes only the available properties and, when something changed, commits and starts the deployment.
  • The listing and its filters read a columnar index of 25 fields per property; each property's full record lives in its own file, fetched when its page opens.
  • When a property leaves Wasi, the next sync deletes its detail file.
  • Requests for advice, contact and visits reach a Supabase Edge Function that validates them and stores them in PostgreSQL.
  • Mortgage and buying capacity calculators with the fixed installment of a French amortization, and a yield calculator that takes vacancy and building fees out of the rent.
  • It ships to the agency's VPS with the same deployment workflow as the admissions landing pages.

How it works

From Wasi to the site

The sync that runs every day before dawn writes the data the site reads; requests go to Supabase.

  1. Source

    • Wasi API
    • Photos that arrive from Zoho CRM

  2. Daily sync

    • GitHub Actions workflow at 3 a.m.
    • Columnar index of 25 fields
    • One file per property

  3. Site

    • Listing with filters
    • Page of each property
    • Mortgage, buying and yield calculators

Requests

  • Advice, contact and visit
  • Supabase Edge Function
  • PostgreSQL

Decisions and their costs

  1. An index for the listing, a file per property

    The listing and the filters need only 25 fields of each property.

  2. Publish only what is available

    In Wasi, a sold or rented property stays active until someone unpublishes it.

  3. Deploy only when something changed

    The sync runs every day, even when the inventory has not changed, and a push made with the workflow's own token does not trigger the deployment.

Stack

Pick a technology to see the projects that use it.

Related