DOCUMENT OPS

Flag last-minute clause changes when a signed PDF lands in Dropbox

Watches a Dropbox folder for the executed PDF, matches it to its negotiated draft.

CategoryDocument Ops
Enginepaperclip
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew executed PDF lands in Dropbox folderDropboxDropbox
  • ActionFind matching negotiated draft by contract IDDropboxDropbox
  • LogicAlign clauses and classify each change as cosmetic or material
  • LogicOnly continue if a material change exists
  • OutputPost clause-level diff to legal Slack channelSlack

What it does

When a counter-signed contract arrives in your Dropbox 'Executed' folder, this workflow pulls the matching negotiated draft, compares them clause by clause, and surfaces every wording change introduced between the last redline and signature. Legal sees a plain-English diff in Slack instead of re-reading the whole document.

When to use it

Run this when contracts are negotiated in one channel and signed elsewhere, and you need to catch a counterparty slipping in altered indemnity, term, or liability language at the eleventh hour. Ideal for sales-led deals where the rep, not legal, controls the signing flow.

How it works

  1. 1A new PDF in the Dropbox 'Executed' folder triggers the run.
  2. 2The workflow reads the executed file and searches Dropbox for the draft sharing the same contract ID in its filename.
  3. 3An agent extracts and aligns clauses from both versions, then classifies each difference as cosmetic or material.
  4. 4If any material change is found, it posts the diff and the changed clauses to the legal Slack channel.
  5. 5The signed file, draft, and verdict are logged for audit.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DropboxFiles and folders.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.