DOCUMENT OPS

Agent-driven audit of the contract repository for missing metadata and gaps

On demand, an agent crawls the Postgres contract index against the Dropbox source folder, finds unindexed files and records with missing fields.

CategoryDocument Ops
Enginepaperclip
Difficultyadvanced
Triggermanual
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOperator starts repository audit
  • ActionRead Postgres index and list Dropbox originalsPostgreSQLPostgres
  • LogicDiff to find unindexed files and missing fields
  • ActionRe-extract from source PDFs and backfill PostgresDropboxDropbox
  • OutputPublish gap audit report to NotionNotionNotion

What it does

Indexes drift over time — files get added without indexing, fields land empty, records lose their source link. This agent-driven workflow reconciles the Postgres index against the Dropbox folder of originals, identifies every gap, re-extracts metadata from the source PDFs to backfill what it safely can, and publishes a clean audit report of whatever still needs a human.

When to use it

Run it periodically, or before an audit or board review, to trust your contract repository. Built for teams that have accumulated a backlog and need confidence the index is complete and accurate.

How it works

  1. 1A manual run kicks off the audit.
  2. 2The agent reads the full Postgres index and lists the Dropbox source folder to find unindexed files and records with missing fields.
  3. 3For each gap, it decides whether the original PDF can supply the missing data and re-extracts when possible.
  4. 4Confidently recovered fields are written back to Postgres; ambiguous cases are left untouched and logged.
  5. 5The agent publishes an audit report to Notion summarizing what it fixed and what still needs human review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect DropboxFiles and folders.
  3. 3
    Connect NotionPages, databases, comments.
  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.