DOCUMENT OPS

Send a weekly digest of contract obligations coming due

On a weekly schedule, queries the obligation database for commitments due in the next 14 days, groups them by owner.

CategoryDocument Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule (Monday morning)
  • ActionQuery obligations due in next 14 days and overduePostgreSQLPostgres
  • LogicGroup by owner and sort overdue first
  • ActionDraft a readable digest with an LLMOpenAI
  • ActionPost digest to team Slack channelSlack
  • OutputReturn count of obligations included

What it does

Runs on a weekly schedule against the obligation tracker database (populated by your clause-extraction workflows), finds every obligation due in the coming two weeks, groups them by responsible owner, and posts a clean, prioritized digest to Slack. Overdue items are called out at the top.

When to use it

Use this once obligations are being captured into a database and you need a recurring nudge that keeps owners accountable to their contract commitments without anyone manually scanning the tracker.

How it works

  1. 1A weekly schedule trigger starts the run every Monday morning.
  2. 2A Postgres query selects obligations due in the next 14 days plus any past-due items.
  3. 3A logic step groups results by owner and sorts overdue items first.
  4. 4An LLM drafts a concise, readable digest from the grouped data.
  5. 5The digest is posted to the team Slack channel.
  6. 6The number of obligations included is returned as the output.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  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.