DOCUMENT OPS

On-Demand Two-Version Contract Compare via Slack

A Slack slash command lets anyone request a diff of two named contract versions; the flow pulls both from Dropbox, surfaces material clause deltas, and replies in the same channel.

CategoryDocument Ops
Enginesim
Difficultybeginner
Triggerchat
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSlack slash command naming two versionsSlack
  • ActionResolve and download both versions from DropboxDropboxDropbox
  • ActionCompare clauses; label added, removed, or amendedOpenAI
  • LogicKeep material deltas; note if versions are identical
  • OutputPost comparison summary to requesting Slack channelSlack

What it does

Exposes a Slack command where a user names two contract versions to compare. The flow fetches both files from the Dropbox contracts library, runs a clause-by-clause comparison, filters to substantive changes, and replies in-channel with a readable summary of what moved between the two versions, including added, removed, and amended clauses.

When to use it

Use it for self-serve, ad-hoc comparisons: a sales lead wants to know what changed between the version they sent Tuesday and the one received Friday, without opening a ticket with legal. Best when versions are already organized in Dropbox by predictable names.

How it works

  1. 1A Slack slash command with two version identifiers triggers the flow.
  2. 2The flow resolves and downloads both named files from Dropbox.
  3. 3An OpenAI step compares clauses and labels each delta added, removed, or amended, with a materiality flag.
  4. 4A logic step keeps only material deltas and notes if the two versions are substantively identical.
  5. 5It posts the comparison summary back to the requesting Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect DropboxFiles and folders.
  3. 3
    Connect OpenAIModels, embeddings, files.
  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.