Daily build log — Intervale Mountain Lodge 🏔️

Spent today chasing down a gnarly bug in our guest review automation (Workflow 5).

We'd already built the whole flow: guest gets texted for a rating after checkout → reply gets parsed and matched to their booking → host gets a summary with one-tap approve/reject → approved reviews auto-publish to the website via our partner's Supabase endpoint.

Today I went back in to stress-test it using a real opportunity from GHL, and hit a wall — the Supabase publish call came back with a 500 error: "Cannot coerce the result to a single JSON object."

First instinct is always "did I mess up the n8n config?" — so I went through the URL, auth, and body one more time. All correct. That ruled out n8n and pointed at Supabase itself.

That specific error is a classic sign that a query expected to find/update exactly one row and found zero. Working theory: the test booking I used predates our review-linking feature, so it was never tagged with the matching opportunity ID on the Supabase side — not a bug in the automation, just a stale test record.

To confirm that without touching anything fragile, I ran a clean end-to-end test instead: submitted a brand-new inquiry through the pipeline, approved it, and now have a fresh opportunity to re-run the review-publish test against. That'll tell us definitively whether it's a missing-tag issue on old data or something deeper.

Nothing shipped today, but good progress narrowing down a real production bug before it hits a live guest.

Next up: Calendar booking automation (Workflow 3) — waiting on the partner to confirm how Airbnb's iCal sync currently works before I build against it.

Still blocked on: Stripe connection + SMS carrier registration (A2P) — both needed before we can do a full real-data test across all 5 workflows.

5 comments

Daily build log — Intervale Mountain Lodge 🏔️