Walk every manual case yourself, then put a branch in the flow for the ones that fail.

People buy automation because they are tired of the main path. They describe the main path. We build the main path. Then Tuesday arrives with a missing field and the flow writes garbage, or retries until it doubles a send. That is not a surprise. That is what happens when you only drew the yes.

Before we turn a flow on, we walk the job the way the current person walks it. We write down every time they stop, ask someone, or open a second tool. Each of those stops is a branch, a queue, or a human step. If we cannot name the branch, we do not automate that part yet.

What a branch looks like in n8n, Make, or your own code

A branch is not a vibe. It is a condition you can point at: this field is empty, this amount is over a limit, this file has two tables, this student question has no still, this invoice currency is not the one we expected. The flow goes left, or it waits, or it writes to the stuck list. It does not invent a default so the chart stays pretty.

n8n and Make both do this well if you use them that way. They also let you hide the branch behind a default value. We do not. Defaults are how half-checked data becomes “production.”

You still have to press the cases yourself

Do not outsource the first test week to the model. Sit down and send the ugly examples through. Watch the branch fire. Watch it fail. Fix the condition. Do it again. If you skip that week, you have hired a clerk you have never seen work.

On Peter’s desk the branch was “this lesson needs his own voice.” On Birchgold it was “this row has no owner.” On Waterware it was “this line item does not match the invoice.” Different companies. Same rule. Draw the no. Then the yes can be boring, which is what you wanted.