n8n Booking Conflict Detection & Automatic Invoicing

n8n Booking Conflict Detection & Automatic Invoicing

Problem Property-viewing requests came from several channels. Agents could be booked for two viewings at the same time, cancellations required manual updates, and invoices for high-value properties depended on someone remembering to create them.

Solution / Workflow I built an n8n workflow that processes bookings and cancellations, checks confirmed appointments for time conflicts, updates records, and alerts the team when a viewing needs to be rescheduled. Confirmed bookings above €300k also trigger automatic invoice creation using a defined business rule.

What I built • Booking and cancellation processing • Agent/date/time conflict detection • Data Table status updates • Telegram alerts for conflicts, confirmations, and invoices • Timezone-safe date handling for Europe/Nicosia

Tech n8n, JavaScript, Data Tables, Telegram, Luxon

Result The final QA run correctly produced two conflicts and two confirmations, including one automatic invoice. Double bookings are detected before the appointment, and invoicing no longer depends on a manual reminder.

Portfolio demo built with anonymized test data.