When to require human review, how to build approval gates, and escalation patterns.
Full automation is not always the right answer. Some decisions carry enough consequence — financial, legal, reputational — that a human must review before the workflow acts. Human-in-the-loop design is about knowing where those lines are and enforcing them architecturally.
Add approval gates when: the action is irreversible (sending to thousands of contacts, deleting records), the value is above a threshold (invoices over $X), the confidence score is below a threshold (AI classification under 85%), or the action is novel (first time a trigger fires for a new user).
Escalation paths must be fast and reliable. When a workflow pauses for human review, send an alert via the channel the reviewer actually monitors, include enough context to decide without opening the workflow, set a timeout so the decision does not block indefinitely, and log the reviewer's decision for audit.
Monitoring does not mean watching every execution. It means setting the right alerts: failures, anomalous volumes, unexpected durations, and decision distributions that drift from baseline.
💡 The best automation builders are not trying to remove humans — they are freeing humans from routine work so they can focus on the decisions that actually require judgment.
The best way to internalise these principles is to open a real workflow and audit it against this lesson's checklist. Pick any workflow from the workflow library and work through each principle point by point.
Browse workflows to practice →