Building for the Person Who Can't Debug It

Description and use

An n8n workflow was refactored for a non‑technical client: IF logic clarified, unnecessary webhook data removed, and a clear doc created to simplify debugging.

Problem

The workflow needed to be understandable and maintainable for a non‑technical client who would be the first to notice failures.

Outcome

The workflow became more legible and easier for a non‑technical user to understand and troubleshoot, reducing the likelihood of silent failures.

Workflow

• 1. Flip the IF node logic to "if phone OR email is not empty, continue". 2. Redesign the Set node to explicitly map Name, Phone, Email, Service address, and Message, defaulting Message to "No message provided". 3. Create a separate documentation file explaining the workflow steps and troubleshooting steps. 4. Export the workflow JSON for import into n8n and keep the doc separate for human reference.

Evidence

I could have left it. The extra keys wouldn't have broken anything downstream — Sheets and Slack only read what I told them to read.

Source

For troubleshooting, I didn't invent hypothetical failure cases — I used one that had actually happened.

Source