DOCUMENT OPS
Approved-Purge Execution with Cold Archive to S3
Triggered when an operator approves the purge queue, it copies each past-retention document to an encrypted S3 cold archive, deletes the live copy from Dropbox.
How it runs
The automated pipeline, trigger to output.
- TriggerPurge-approval webhook receivedHTTP webhook
- LogicVerify items still past-retention and not on hold
- ActionCopy approved files to encrypted S3 cold archiveAWS S3
- ActionDelete live copy from Dropbox vaultDropbox
- ActionAppend disposition record to Airtable logAirtable
- OutputPost archive-and-purge confirmation to SlackSlack
What it does
This workflow carries out the actual disposition step of the retention lifecycle, but defensibly: nothing is hard-deleted without first landing a copy in a long-term cold archive and writing a tamper-evident disposition log. It turns "we deleted it" into "we archived and disposed of it on this date, here is the record."
When to use it
Run this only after the purge queue has been reviewed and approved, when you need to physically clear past-retention documents out of the working Dropbox vault while retaining a recoverable, audit-grade archive.
How it works
An approval webhook fires with the list of approved document IDs. A logic step confirms each item is still flagged past-retention and not under any legal hold. Confirmed files are copied from Dropbox into an encrypted AWS S3 cold-archive bucket, then the live Dropbox copy is deleted. A disposition record (file, archive location, date, approver) is appended to the Airtable log, and a final Slack confirmation reports what was archived and removed.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect DropboxFiles and folders.
- 3Connect AWS S3Buckets, objects, signed URLs.
- 4Connect AirtableBases, tables, views, automations.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Document Ops workflows
Flag redline deviations when a contract lands in Drive
Watches a Google Drive folder for incoming counterparty contracts, diffs each clause against your approved template library.
Gate contract signing on clause-deviation approval
When a contract is submitted for signature via webhook, diffs its clauses against approved templates and either auto-approves clean documents or holds them in Slack for explicit…
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
Log contract clause deviations to a Notion review register
On a daily schedule, scans a Drive contracts folder, diffs clauses against approved templates with OpenAI.
Weekly audit of clause drift across the contract repository
Each week, scans all executed contracts in Drive, measures how far each clause has drifted from approved templates.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.