https://media.gohallway.com/ops_walkthrough.mp4

What this system does

I operate a short term rental, and it runs on the same stack I build for clients: Notion as the record, n8n as the automation, and Claude drafting fixes for novel errors that I approve. This walkthrough follows one invented test reservation from the property management software into Notion, shows a stale record correcting itself, and then shows what happens when something breaks. Known failures are fixed automatically and reported by email. Unknown failures are never guessed at. They become a flagged task and a Needs Review email with everything needed to diagnose them. Every name, date and contact detail on this page is made up.

How the pieces connect

flowchart LR
  A["Booking platform"] --> B["Property management software"]
  B -->|"guest messages and turnover notices"| G["Guests and cleaners"]
  B -->|"reservation event"| C["n8n"]
  C -->|"verified and matched"| D["Notion records"]
  C -.->|"any failure"| E["Diagnosis pipeline"]
  E -->|"known pattern"| F["Auto fix plus email"]
  E -->|"unknown"| H["Flagged task plus email"]
  E -.->|"novel errors"| I["Claude drafts a fix, a human approves"]

Where the property management software fits

The property management software sends the booking confirmation, the check in instructions and the cleaner notices on its own schedule. n8n does not touch those messages. n8n starts from the reservation event and keeps the records in Notion in step with it.

What it looks like running

<aside> 🖼️ The reservation workflow in n8n. A webhook from the property management software, a secret check, a lookup in Notion, then create or update. The lower row is the daily reconcile that closes out past stays.

</aside>

<aside> 🖼️ The same reservation in Notion. The older stay was marked Completed by the daily reconcile. The new one is Upcoming.

</aside>

<aside> 🖼️ A known failure, fixed automatically. The email says what broke in plain English, which saved pattern matched, and what changed.

</aside>

<aside> 🖼️ An unknown failure. Nothing is patched. A flagged task lands in Notion, and a Needs Review email carries the error and a block ready to paste into Claude.

</aside>

Recorded on a sanitized replica running on invented test data. The workflow logic matches the production system. Identifiers, credentials and records are removed or invented.