DOCUMENT OPS

Contract intake from Google Drive with clause extraction and Slack approval

Watches a Google Drive intake folder for new contracts, extracts key clauses with an LLM, and posts a structured summary to Slack for one-click approval routing.

CategoryDocument Ops
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew file in Drive intake folderGoogle DriveGoogle Drive
  • ActionRead contract text from DriveGoogle DriveGoogle Drive
  • ActionExtract key clauses with LLMOpenAI
  • LogicFlag high-risk if uncapped liability or auto-renew
  • OutputPost clause summary to Slack for approvalSlack

What it does

Turns a shared Google Drive folder into a contract intake queue. Every new agreement dropped in is parsed, its risk-bearing clauses pulled out, and a clean summary is posted to the legal channel so a reviewer can approve or escalate without opening the file.

When to use it

Use it when sales, vendors, or partners send contracts as files and your legal or ops team needs a fast, consistent first read. Best for teams drowning in PDFs who want a triage step before anyone reads the full document.

How it works

  1. 1A new file landing in the watched Drive folder triggers the run.
  2. 2The file's text is read from Google Drive.
  3. 3OpenAI extracts the parties, term, auto-renewal, liability cap, termination notice, and governing law into a structured object.
  4. 4A logic step flags the contract as high-risk if liability is uncapped or the term auto-renews.
  5. 5A summary card with the clause table and a risk flag is posted to the Slack legal channel with approve and escalate actions.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.