Scano Immobiliare: listings synced from APIMO
Case study
- My role
- I built the website and the integrations with APIMO and the CRM.
- Duration
- Started in July 2025
The problem
The agency manages properties in APIMO and contacts in GoHighLevel. The website had to show listings that are always up to date without entering them twice, and send requests straight into the CRM.
What I did and why
- Listings from APIMO: the site reads properties from the management software and turns numeric codes into readable labels, in Italian and English.
- Shareable filters: type, price, size, rooms and features, with the state in the URL.
- Complete property pages: photos, floor plans, videos and energy rating.
- Contacts in the CRM: the general form and the one to propose a property write to GoHighLevel.
Results
- APIMOlistings read from the management software, no double entry
- GoHighLevelcontacts from the site straight into the CRM
- IT + ENlistings and site in two languages
Stack highlights
- Next.js 15
- APIMO API
- GoHighLevel
- next-intl
- nuqs
- Zod
- GSAP
Working on something similar? Let's talk.
Get in touchThe agents already work in APIMO, so the website must not become a second place to upload properties. It reads the listings from the management software, turns numeric codes into readable labels and shows them with filters for type, price, size and features, with the search state in the URL. Requests from the site, including the form to propose a property, go straight into the agency's GoHighLevel CRM.
I wrote about how I connected APIMO to Next.js in the post Integrating the APIMO API in Next.js.
What I bring to an agency or a small business from this project
- A website that reads data from the software the client already uses, instead of making them enter it twice.
- CRM integrations, so contacts coming from the site don't get lost.
- Searches with filters that can be shared with a link.
Realized for Scano Immobiliare in collaboration with DVC Consulting
