DOCUMENT OPS

Triage emailed contracts and route high-risk clauses to legal

Monitors a contracts inbox, extracts and risk-scores key clauses from any attached agreement.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerContract attachment hits intake inboxGmailGmail
  • ActionExtract key clauses from attachmentOpenAI
  • ActionRisk-score clauses against playbookOpenAI
  • LogicBranch on unacceptable clause present
  • OutputFast-track or escalate to legal in SlackSlack

What it does

It reads contracts arriving as email attachments, extracts the high-stakes clauses (liability, indemnity, termination, IP, auto-renewal), and scores each against your accepted positions. Low-risk agreements get marked for fast-track approval; anything with an unacceptable clause is escalated to legal with the exact offending language.

When to use it

Use it when sales or procurement forwards counterparty contracts to a shared mailbox and legal becomes the bottleneck. It separates the routine 80% from the genuinely risky 20% so reviewers spend time where it matters.

How it works

  1. 1A new email with a contract attachment arrives in the monitored Gmail inbox and triggers the run.
  2. 2The attachment text is extracted and the model pulls the key clause set with verbatim quotes.
  3. 3Each clause is risk-scored against playbook thresholds and an overall verdict is computed.
  4. 4A logic branch checks whether any clause crossed the unacceptable line.
  5. 5Clean contracts post a fast-track summary to Slack; risky ones page the legal channel with the flagged clauses and a recommended counter.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  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.