I build automations for local businesses — trades, clinics, restaurants. Over
the last weeks I built four flows in n8n and published each one with its
workflow file and its validator output.
I am publishing the caveat with the numbers, because I think that part is
usually missing:
Missed Call Rescue — 8 nodes, 0 errors, 0 warnings, tested against real
Twilio and Telnyx call payloads
Review Request — 10 nodes, 0 errors, 0 warnings, 5 real Jobber and
Housecall Pro payloads, 6 decision cases
Quote Follow-Up — 10 nodes, 0 errors, 0 warnings, 6 payload shapes,
7 decision cases
Appointment Reminder — 15 nodes, two triggers, 0 errors, 0 warnings,
9 appointment shapes and 19 reply shapes
None of the four has run against a live phone system, job system or calendar
with real customers. The validator checks the shape of a workflow, not
reality. So these are builds, not results.
Two things I got wrong that might save someone else the time:
- respondToWebhook after a Wait node does nothing useful. With
responseMode: “responseNode” the caller sits there until the wait is over
— three days, in the quote follow-up. The respond node has to come before
the wait. - An unclear reply is not a confirmation. My first reminder flow counted
anything that was not “no” as a yes. “maybe”, “I’ll try” and an emoji all
became confirmed appointments.
Descriptions and the flows are here:
Happy to be told where these are wrong.