Jaeger Immobilien Morsbach

Jaeger Immobilien Morsbach is a modern real estate website built in Webflow to provide a structured, scalable platform for presenting properties, company content, and editorial content.

The website combines a custom Webflow build with dedicated CMS structures for property listings and blog content, allowing dynamic pages and reusable content while maintaining a consistent design across the site.

A key part of the project was connecting the website with Propstack CRM. Using Make and Cloudflare Workers, property data can be transferred from the CRM into Webflow CMS, reducing the need for duplicate manual entry and helping keep property information synchronized between the internal CRM workflow and the public website.

The project brings together responsive Webflow development, CMS architecture, API integration, workflow automation, and SEO-focused implementation in a single maintainable system designed around the agency’s day-to-day real estate workflow.

I approached the project as both a website development and systems integration project. The first priority was to establish a clean Webflow structure that could support the agency’s public-facing content independently of the automation layer.

I designed the CMS architecture around two main content systems: property listings and blog content. Property fields were structured to support detailed real estate data while allowing individual sections and values to appear only when relevant. The Blog CMS followed a reusable content structure for consistent publishing and presentation.

For the property workflow, I treated Propstack as the source of property data and mapped the relevant CRM information to the corresponding Webflow CMS fields. This required aligning two different data structures while preserving the way each property needed to be presented on the website.

Make was used to orchestrate the automated workflow, while Cloudflare Workers handled the additional processing required between the connected systems. This separated automation and transformation logic from the presentation layer and kept Webflow focused on rendering the final website experience.

I implemented and tested the integration incrementally, validating property data, statuses, media, optional fields, and frontend conditional visibility rather than attempting to automate the entire workflow at once. This made it possible to identify mapping and presentation issues early while keeping the system maintainable.

Development began with the Webflow structure and reusable components, followed by the CMS architecture required for both property listings and blog content. The property collection was designed to accommodate detailed real estate data while keeping the frontend template flexible enough to handle properties with different sets of available information.

The dynamic property template was built around conditional visibility. Property descriptions, characteristics, pricing and cost information, areas, condition, energy and heating data, features, images, and other optional information are rendered only when the corresponding CMS data is available. This prevents incomplete records from creating empty or irrelevant sections on the live website.

Property features were structured through CMS relationships, while the image gallery and carousel were designed to work dynamically with the available property media. Status-specific presentation logic was also incorporated so that the frontend could respond appropriately to changes in a property’s marketing state.

The next stage was the Propstack integration. Relevant property information from the CRM was mapped to the corresponding Webflow CMS structure, creating a consistent relationship between the internal property-management workflow and the public website.

Make was used to orchestrate the automation between the systems, while Cloudflare Workers provided an additional server-side processing layer where required. Together, these components handle the transformation and transfer of data before it reaches the Webflow CMS, allowing the website to remain focused on presentation rather than integration logic.

The Blog CMS was implemented as a separate dynamic content system with reusable post templates. Finsweet Attributes were integrated for the table of contents and estimated reading time, while a reading progress indicator improves navigation through longer articles. Heyflow was integrated where required for interactive lead-generation forms.

Throughout development, the responsive layouts, CMS conditions, property data mappings, media behavior, automation workflow, and generated pages were tested incrementally to ensure that information arriving from the connected systems was represented correctly on the frontend.

This project reinforced the importance of designing the CMS architecture before building the automation layer. When an external CRM becomes the source of property data, the structure of the website CMS needs to anticipate how that data will be mapped, transformed, and presented on the frontend.

Integrating Propstack with Webflow also demonstrated that connecting two platforms is more than simply transferring field values. Different data structures, optional information, property statuses, media, and presentation requirements need to be translated into a consistent website experience.

Separating responsibilities between Propstack, Make, Cloudflare Workers, and Webflow proved especially valuable. Propstack remains the source of property data, Make coordinates the workflow, Cloudflare Workers handle additional processing where required, and Webflow CMS remains focused on structured content and presentation.

The project also reinforced the value of incremental testing. Building and validating the integration step by step made it easier to identify mapping, conditional visibility, and presentation issues before expanding the automation.

Most importantly, the project showed how Webflow can extend beyond a traditional CMS website when combined with external systems and automation, creating a workflow that reduces repetitive content management while preserving full control over the frontend experience.