DOCUMENT OPS
Triage emailed signed contracts and book renewal reviews from Gmail
Reads countersigned contracts arriving as Gmail attachments, decides whether each needs a renewal review, files a record in Airtable.
How it runs
The automated pipeline, trigger to output.
- TriggerGmail message arrives with a contract PDF attachmentGmail
- ActionAgent extracts parties, dates, and notice periodOpenAI
- LogicClassify as renewal-sensitive or discard non-contract
- ActionRecord renewal-sensitive contract in AirtableAirtable
- OutputBook renewal review meeting in Google CalendarGoogle Calendar
What it does
It catches contracts that arrive by email instead of a shared drive. When a signed PDF lands as a Gmail attachment, an agent reads it, extracts the parties and renewal date, judges whether the agreement is renewal-sensitive (auto-renew, notice period, or escalating price), logs it, and books a review meeting so your team prepares before the window closes.
When to use it
Use it when counterparties email you the executed copy and those attachments otherwise rot in an inbox. Best for teams without a formal contract intake process who still want renewals on the calendar.
How it works
- 1A Gmail message with a PDF attachment matching your contract filter arrives and triggers the run.
- 2An agent extracts the counterparty, effective and renewal dates, notice period, and auto-renew status from the attachment.
- 3A decision step classifies the contract as renewal-sensitive or low-risk and discards non-contracts.
- 4Renewal-sensitive contracts are recorded in Airtable for tracking.
- 5A Google Calendar review event is booked one notice-period before the renewal date, with the extracted terms in the description.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 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.
