DOCUMENT OPS
Sync new contract renewal dates to Google Calendar and a Postgres register
On each new signed contract in Dropbox, extracts the effective date, renewal date, and notice deadline, upserts the contract into a Postgres obligations table.
How it runs
The automated pipeline, trigger to output.
- TriggerNew signed contract added to Dropbox folderDropbox
- ActionExtract dates and obligations with OpenAIOpenAI
- LogicCompute notice deadline; skip calendar if no renewal date
- ActionUpsert contract and obligations into Postgres registerPostgres
- OutputCreate Google Calendar reminder before notice deadlineGoogle Calendar
What it does
Gives renewal management a system of record plus a calendar nudge. It captures the date trio from each contract, stores the contract and its obligations in a Postgres register your other systems can query, and books a calendar event before the notice window closes.
When to use it
Use it when your obligations data needs to live in your own database (for dashboards or downstream automation) and you want renewal deadlines to show up on a shared team calendar automatically.
How it works
- 1A new file in the Dropbox `/Signed Contracts` folder triggers the run.
- 2The PDF text is extracted and OpenAI returns the parties, obligations, effective date, renewal date, and notice-period length.
- 3A logic step computes the notice deadline (renewal date minus notice period) and skips calendar creation if no renewal date was found.
- 4The contract and its obligations are upserted into the Postgres obligations register.
- 5A Google Calendar event is created a configurable buffer before the notice deadline, titled with the contract and counterparty.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.