Operations Architect
3 Weeks
Process Automation
n8n, OneDrive API, Slack API, Airtable, Webhook
Document approval should not take five days. When it does, the delay is rarely about the decision itself. It is usually caused by the process surrounding it: the email that was missed, the approval that was given verbally but never recorded, or the document that was forwarded to the wrong person and sat unread in a secondary inbox.
The professional services client I worked with managed their entire approval process through email forwarding. There was no status visibility, no audit trail, and no reliable way to determine whether a document was pending, approved, rejected, or simply lost in an inbox.
The business impact was significant. Projects dependent on approved documents regularly waited up to five days before progressing. The operations team spent more than eight hours each week sending follow-up emails to chase decisions, and because approvals existed only within email threads, the organization lacked a reliable record of who approved what and when.
The objective was to redesign the approval process so decisions could be made faster, tracked automatically, and recorded in a centralized system without removing human accountability.
Before designing the automation, I mapped the complete approval workflow from document submission to final decision.
The audit identified three primary causes of delay:
These findings became the foundation of the solution architecture and guided every design decision that followed.
The workflow begins when a new document is uploaded to a designated OneDrive folder.
n8n retrieves document metadata such as department, document type, and urgency level, then applies conditional routing logic to determine the correct approver. The right stakeholder receives the request on the first send, eliminating the manual forwarding process that was one of the largest sources of delay in the original workflow.
Approvers receive an instant Slack notification containing document details and two interactive options: Approve or Reject.
The entire decision can be made directly within Slack without opening email threads or navigating to a separate system. Once an action is selected, a webhook sends the decision back to n8n, allowing the workflow to continue automatically.
By embedding approvals inside the team’s primary communication tool, the process became significantly faster and easier to action.
Every approval decision is logged immediately in Airtable with the approver, timestamp, document reference, and final decision.
Approved files are automatically archived to the appropriate destination folder, while Airtable provides real-time visibility into pending, approved, and rejected requests.
The result is a centralized audit trail that eliminates manual tracking and provides complete transparency across the approval lifecycle.
A simpler implementation would have routed every document to a single approver or Slack channel regardless of document type.
I intentionally designed conditional routing logic so different document categories were automatically directed to the appropriate stakeholder based on metadata. This reduced delays, eliminated unnecessary forwarding, and ensured approval requests reached the correct decision-maker immediately.
Email notifications compete with every other message in an inbox.
I moved approval requests into Slack because it was already the client’s primary communication platform. Notifications delivered in Slack were significantly more likely to be seen and actioned quickly than those delivered through email.
The addition of interactive approval buttons further reduced friction by allowing decisions to be made without leaving Slack.
A fully automated approval process could have eliminated delays entirely, but it would also have removed accountability.
The approval stage existed for a legitimate business reason. The goal was not to replace human judgment but to make exercising that judgment as efficient as possible.
One click inside Slack provided the right balance between operational speed and governance.
The automation reduced average document approval time from five days to under twenty-four hours.
The operations team recovered more than eight hours each week previously spent sending follow-up emails and manually tracking approval status. Approval requests no longer disappeared into inboxes, and every decision became visible, traceable, and auditable.
The Airtable audit trail gave stakeholders real-time visibility into pending and completed approvals for the first time, eliminating the compliance risk associated with email-based approval processes.
Beyond reducing approval times, the workflow established a standardized approval framework that could be reused across additional departments and business processes. Because routing, notifications, audit logging, and archiving were designed as modular components, the architecture provides a scalable foundation for future approval workflows without requiring a complete redesign.
Approval Time (Down from 5 Days)
Recovered Per Week
Auditable Decision Log
Lost Approval Requests
That is exactly where I do my best work. Tell me what is frustrating you operationally, even if you cannot name it precisely yet. I will ask the right questions and tell you what I would fix first.