
Automation fails in two directions. Too little and the work is manual; too much and a wrong action reaches a customer at machine speed. The useful middle is an approval step — a pause where a person confirms the one action that matters.
Two tools in the directory are built around that pause: Relay and Lindy.
The short answer
Put the approval immediately before the irreversible action, not at the start. Approving the plan is theatre; approving the send is a control.
Why approval at the start does not work
A workflow that asks for approval before running is approving an intention. The thing that will actually happen — the exact email, the exact refund, the exact record — is not known yet, so the approval cannot evaluate it.
Approval at the end, on the concrete action, is a different decision. The reviewer sees what will happen and can stop it.
Relay: the gate as a primitive
Relay treats approval as a step type, which shapes the whole workflow: a branch pauses, a person confirms in a queue, and the run continues. That is the right design for processes where an external action is the risk.
The cost is throughput. Every gate is a queue, and queues need someone watching them. An approval workflow nobody staffs is a workflow that silently backs up.
Lindy: the recurring agent
Lindy runs agents on a schedule: watch an inbox, reschedule, follow up. The natural design is a split between actions it can take alone (reading, drafting, scheduling) and actions that need a person (sending, cancelling).
The failure mode is scope creep in the name of convenience: the agent starts sending because the review queue was slow. The boundary should be written down before the queue gets slow.
The decision table
| Action | Reversible | Gate |
|---|---|---|
| Read a record | — | None |
| Draft a message | Yes | None |
| Create an internal note | Mostly | None |
| Send externally | No | Human |
| Change money or access | No | Human |
| Delete data | No | Human, twice |
The last row is not a joke. Deletions are the action where a single mis-scoped prompt is expensive, and a second confirmation is cheap.
What the reviewer needs to see
An approval that shows only 'workflow ready' is useless. It should show the exact action: the recipient, the text, the amount, the record id. If the reviewer has to open another tab to understand what they are approving, they will approve without understanding.
The measured version
Track approval rate and approval latency. A 99 percent approval rate means either the workflow is safe or the reviewers stopped reading. Latency tells you which: if approvals happen in two seconds across the board, nobody is reading.
Frequently asked questions
Is approval the same as a dry run? No. A dry run shows what would happen; approval decides that it should.
Can I approve in chat? Only if the chat shows the exact action. 'Shall I?' is not an approval surface.
What about volume? Batch similar actions for one approval — ten sends with a list is reviewable; ten separate prompts is not. See guardrails and automation tools.
Last checked: 16 November 2026.
Related: guardrails, Relay vs Zapier, and automation tools.


