Put a Human Approval Before Documents Get Filed
Full automation is easy to build and hard to trust. Most teams do not want the workflow to stop — they want to be asked before the one step that would be awkward to undo.
The short answer
The Ask a Person to Approve step pauses a workflow and waits for a human decision before the steps after it run. Everything before the pause — reading the document, naming it, deciding where it goes — still happens automatically, so the person approving sees a finished proposal rather than a raw file. On approval the workflow continues on its own. This is how you automate filing without giving up the judgement call on documents where being wrong matters.
Steps this uses
Before and after
What actually changes
As they arrive
- contract-draft.pdf → workflow pauses
After the workflow
- Approved by Dana, 14:02 → Contracts/2026-09-14-contract-acme.pdf
The naming and destination were decided before anyone was asked. The approval was one click.
Setting it up
Described once, then it runs
Automate up to the decision
The workflow reads the document and works out the name and the destination before anyone is asked. The approver reviews a proposal, not a task.
Insert the approval
The Ask a Person to Approve step pauses the run and waits. Nothing after it happens until someone answers.
Continue automatically on yes
The Rename and Move steps run as soon as approval lands. The person makes one decision rather than doing the work.
Tell someone it happened
The Send a Message step can post to Slack or send an email when the run completes.
Approve the proposal, not the task
The value of putting the approval late is that the person is not being asked to do the work. By the time they see it, the document has been read and a name and destination proposed. Approving is a judgement on a finished answer, which takes seconds; the alternative — asking a person first and automating afterwards — just relocates the work.
Where an approval is worth the friction
Anything outward-facing or hard to reverse: a contract filed to a client folder, a document going to an external party, anything touching a records set someone audits. Routine internal filing rarely justifies it, and an approval on every document trains people to click yes without looking, which is worse than no approval at all.
Where the notification goes
The Send a Message step reaches Slack and email. It does not reach Microsoft Teams. If your approvals live in Teams, the approval itself still works — the notification is what would need to go somewhere else.
FAQ
Common questions
Can I add a human approval step before documents are filed?
Yes. The Ask a Person to Approve step pauses the workflow and waits for a decision. Steps before the pause still run automatically, so the approver reviews a proposed name and destination rather than a raw file, and the workflow continues on its own once approved.
What happens while a workflow is waiting for approval?
It stays paused. No step after the approval runs until someone answers, and the run resumes automatically when they do.
Should every document need approval?
No. An approval on everything trains people to click yes without reading, which is worse than having none. Reserve it for documents that are outward-facing or hard to undo.
Can approval notifications go to Microsoft Teams?
No. The Send a Message step reaches Slack and email only. The approval step itself works regardless of where your team talks.
Automate the work, keep the judgement.
The workflow pauses for a person, then finishes on its own.
Try The Drive AI Free5 GB free · No credit card required