DOCUMENT OPS

Counterparty Markup Tracker: Log Liability Clause Edits from Dropbox to Notion

When a counterparty drops a revised contract into a Dropbox folder, it diffs against your last sent version and logs every changed liability or indemnity clause as a row…

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerRevised contract dropped in Dropbox folderDropboxDropbox
  • ActionFetch incoming draft and last sent versionDropboxDropbox
  • ActionDiff and classify clause changes by type and favorabilityOpenAI
  • LogicKeep only indemnity, liability, and termination edits
  • OutputAppend each clause change to Notion negotiation trackerNotionNotion

What it does

Monitors a Dropbox folder where counterparties return marked-up contracts, compares the incoming draft against the last version your side sent, and records each material change to liability, indemnity, or termination clauses as a structured entry in a Notion database. It turns scattered email attachments into an auditable clause-by-clause negotiation history.

When to use it

Use it when you exchange drafts with outside counsel or vendors over Dropbox and want a single tracker showing how each risk clause evolved across rounds. Good for teams that need a defensible record of who changed what and when, without maintaining it by hand.

How it works

  1. 1A revised contract file appears in the watched Dropbox folder, triggering the run.
  2. 2The workflow pulls the incoming draft and your previously sent version from Dropbox.
  3. 3An OpenAI step computes a clause-level diff and classifies each change by clause type and direction (more or less favorable).
  4. 4A logic step filters to only indemnity, liability, and termination changes.
  5. 5Each qualifying change is written as a new row in the Notion negotiation tracker with clause name, old text, new text, and round number.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DropboxFiles and folders.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  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.