DOCUMENT OPS

Send a weekly digest of new contract risks from the register

On a weekly schedule, reads the Coda risk register for contracts added since the last run, summarizes the high- and medium-risk clauses across all of them.

CategoryDocument Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionQuery Coda register for contracts added this weekCodaCoda
  • LogicSkip if no new contracts were logged
  • ActionSummarize risks by severity and clause typeOpenAI
  • OutputEmail rolled-up digest to legal and procurementGmailGmail

What it does

Turns the running contract risk register into a once-a-week briefing. Instead of per-contract pings, it gathers everything logged in the last seven days, groups the risks by severity and clause type, and produces one readable digest: what came in, what's risky, and what still needs review.

When to use it

Use it when contracts arrive steadily and stakeholders want a predictable weekly pulse rather than real-time alerts. Pairs well with the Dropbox intake template, which fills the register that this one summarizes.

How it works

  1. 1A weekly schedule triggers the workflow.
  2. 2It queries the Coda risk register for rows added in the past week.
  3. 3A logic step skips sending if no new contracts were logged.
  4. 4OpenAI summarizes the period: counts by risk level, the top high-risk clauses, and any contracts still marked unreviewed.
  5. 5The digest is emailed via Gmail to the legal and procurement distribution list with links back to each register row.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CodaDocs, packs, automations.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect GmailRead, draft, send, label.
  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.