DOCUMENT OPS
Reconcile contract amendments and supersede stale renewal dates
Detects amendment and addendum documents in Dropbox, links them to the original contract in Airtable.
How it runs
The automated pipeline, trigger to output.
- TriggerNew amendment or addendum PDF added to DropboxDropbox
- ActionExtract original reference and changed dates with OpenAIOpenAI
- ActionMatch and update parent contract record in AirtableAirtable
- LogicCheck whether the renewal date actually changed
- OutputReplace stale Google Calendar reminder with corrected dateGoogle Calendar
What it does
It keeps renewal dates correct when contracts get amended. When an amendment or addendum is uploaded, it extracts the referenced original agreement and any changed dates, matches it to the existing contract record in Airtable, and if the renewal or term date moved, it deletes the outdated calendar reminder and seeds a new one so you never act on a superseded date.
When to use it
Use it when contracts change after signature through addenda and your reminders drift out of sync with reality. Built for legal and ops teams managing long-lived agreements that get renegotiated mid-term.
How it works
- 1A new amendment or addendum PDF is added to the Dropbox contracts folder and triggers the run.
- 2OpenAI extracts the referenced original contract, the amendment type, and any new renewal or term dates.
- 3The workflow matches the amendment to its parent record in Airtable and updates that record.
- 4A logic step checks whether the renewal date actually changed; unchanged amendments stop here.
- 5When the date moved, the stale Google Calendar reminder is removed and a corrected renewal event is created against the new date.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect AirtableBases, tables, views, automations.
- 4Connect Google CalendarEvents, attendees, availability.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.