DOCUMENT OPS

Weekly Digest of All Changed Clauses Across Dropbox Contracts

On a weekly schedule, scans a Dropbox contracts folder for documents revised in the last seven days, diffs each against its prior version.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionList Dropbox contracts revised in the last 7 daysDropboxDropbox
  • ActionDiff each pair and summarize changed clausesOpenAI
  • LogicGroup by contract and rank by materiality
  • OutputPost the consolidated digest to SlackSlack

What it does

Once a week this workflow sweeps your Dropbox contracts folder, finds every agreement that was revised in the last seven days, computes a clause-level diff for each, and assembles one consolidated digest. It posts the digest to Slack so the team starts the week with a single view of everything that moved across the deal book.

When to use it

Use it when individual edits are handled in real time but leadership wants a periodic, low-noise roll-up. It is the weekly briefing layer on top of per-document review, ideal for legal ops standups.

How it works

  1. 1A weekly schedule starts the run.
  2. 2The workflow lists Dropbox files modified within the past seven days and pairs each with its prior version.
  3. 3An OpenAI step diffs every pair and summarizes the changed clauses per contract.
  4. 4A logic step groups changes by contract and ranks them by materiality.
  5. 5The summaries are merged into one formatted digest.
  6. 6The digest is posted to the legal Slack channel with links back to each Dropbox file.

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 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.