An automation needs more than a successful demonstration. Someone needs to know what happens when information is missing, a connection stops working or a decision needs a person.
Give exceptions an owner.
During scoping, we identify the cases that should stop or wait: an unknown client, a missing field or a document that cannot be confidently matched. We agree who receives the exception and what information they need to resolve it. An unclear record should not silently move forward as complete.
Put approval before the action.
For an accounting intake workflow, preparing a follow-up and sending it are separate steps. Our proposed approach keeps the message available for staff review before it goes out. The review should show the client, the missing items and the intended recipient.
Where an n8n AI Agent uses tools, n8n supports human approval for selected tool calls. The workflow pauses for approval or denial before that tool executes. This is a configuration choice, not a guarantee that every action in a workflow is automatically reviewed. Read n8n’s human review documentation.
Plan for failed runs.
n8n supports error workflows that respond to execution failures, for example by sending an alert. We scope the notification recipient, the useful context and the recovery procedure. A retry should be checked against the risk of sending a duplicate message or creating a second record. Read n8n’s error-handling documentation.
Who owns the workflow?
Where are exceptions reviewed?
How is it paused or restarted?
Who maintains the connected accounts?
What changes require a new quote?
Separate care from new work.
We discuss monitoring, fixes and agreed maintenance as ongoing care. Adding a new system or changing the business process can require additional implementation work. We make that boundary explicit so a care arrangement does not become an undefined development backlog.
The handover, acceptance checks and any care arrangement belong in the agreed scope. They help the team understand what it is taking ownership of.