Daily build log — Intervale Mountain Lodge 🏔️
Two bugs today, and both turned out to be "the code's not lying, you're just misreading it" situations.
Bug #1: SMS approvals silently failing
We've got a workflow where an SMS like "approve [guest name]" matches against open inquiries and moves the booking forward. Testing it kept returning "couldn't find a pending inquiry matching ''" — empty name, every time.
Dug into the parsing code and found it: the node strips the command word off the front of the message to isolate the name — so it needs the message shaped exactly like "approve John Smith", command first. Any other phrasing and the regex strip does nothing useful, name comes out blank, and it silently routes to the fallback branch instead of throwing an error. No crash, no red flag — just a wrong-looking result that looks exactly like a real matching bug until you actually read the extraction logic line by line.
Bug #2: The invoice email that wasn't missing
Got a report that a test guest never got their invoice. Went straight to the API response from the invoice-send call, fully expecting to find a failed request or a wrong recipient field.
Instead: both the SMS and email legs came back successful. "msg": "Email queued successfully", correct recipient, correct invoice link, all of it. So where'd it go? Spam folder. The email was sent from GHL's shared sending domain rather than a verified custom one, and Gmail flagged it as "similar to messages identified as spam in the past."
Good reminder for myself: before assuming an automation is broken, check whether the thing actually did happen and just landed somewhere unexpected. Would've been easy to burn an hour re-debugging a workflow that was working exactly as built.
Real takeaway from today though — this isn't just a one-off test annoyance. Every guest-facing GHL email (invoices, confirmations, review requests) is riding on that same shared domain, so it's a deliverability risk across the whole system, not just this workflow. Adding "set up a verified custom sending domain (SPF/DKIM/DMARC)" to the pre-launch checklist.
Next up: Calendar booking automation (Workflow 3) — still waiting on Stripe to go live so we can run one real end-to-end payment test instead of simulated ones.
Still blocked on: Stripe connection + SMS carrier registration (A2P), plus the new email domain item above — all need to close out before a full real-data run across all 5 workflows.
16
5 comments
Okasha Khan
5
Daily build log — Intervale Mountain Lodge 🏔️
Brendan's AI Community
skool.com/brendan
A free community for AI Voice Agents, Claude Code & n8n.
Join to learn, share ideas, and build real systems for the future.
Leaderboard (30-day)
Powered by