DOCUMENT OPS

Triage Redlined Contracts from Email Into a Slack Review Queue

When a counterparty emails back a marked-up contract, an agent pulls the attachment, compares it to the last sent version.

CategoryDocument Ops
EngineSim + Paperclip
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCounterparty reply with contract attachment arrivesOutlook
  • ActionExtract attachment and counterparty detailsOutlook
  • ActionDiff against last sent version and explain changesOpenAI
  • LogicKeep material clause edits, drop formatting noise
  • OutputPost threaded review card to SlackSlack

What it does

Monitors a shared legal inbox for replies carrying contract attachments. On arrival it grabs the document, compares it to the version your side last sent, and isolates substantive edits — never formatting noise. Each material change is summarized against the relevant playbook position and posted to a Slack review channel as a threaded card the deal owner can act on immediately.

When to use it

Use it when redlines arrive over email and get lost in busy inboxes, and you want the legal channel to surface incoming changes the moment they land. Ideal for active negotiations where turnaround speed wins deals.

How it works

  1. 1A new email with a contract attachment hits the monitored Outlook inbox and triggers the run.
  2. 2The agent extracts the attached document and the counterparty's identity from the message.
  3. 3An OpenAI step diffs the new version against the last sent text and explains each substantive deviation.
  4. 4A logic step filters out whitespace and reference-only edits, keeping material clause changes.
  5. 5Slack receives a threaded review card per contract, summarizing changes by risk and tagging the deal owner.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  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.