DOCUMENT OPS

Log filed Dropbox contracts into a Notion contract registry

Indexes each new Dropbox contract into a structured Notion database with counterparty, type, effective date, renewal date, and value for a searchable single source of truth.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew contract filed in Dropbox /Contracts/ClientsDropboxDropbox
  • ActionExtract structured contract metadata with OpenAIOpenAI
  • LogicBranch: does a Notion row for this file already exist?
  • ActionCreate new Notion registry pageNotionNotion
  • OutputUpdate existing Notion row in placeNotionNotion

What it does

Builds a living contract registry in Notion. Every contract added to Dropbox becomes a row with its key metadata extracted automatically, so the whole team can search and filter agreements without opening files.

When to use it

When leadership keeps asking "how many active vendor contracts do we have and when do they renew?" and the answer lives in scattered PDFs. Use it to maintain an always-current contract inventory alongside the source files.

How it works

  1. 1A new file added under Dropbox `/Contracts/Clients` triggers the run.
  2. 2OpenAI extracts counterparty, contract type, effective date, renewal date, term length, and annual value into a structured object.
  3. 3A branch checks whether a Notion row already exists for that Dropbox file (by file path) to avoid duplicates.
  4. 4If new, the workflow creates a Notion database page with all extracted fields plus a link to the Dropbox file.
  5. 5If it already exists, the existing Notion row is updated in place with the latest values.

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