DOCUMENT OPS

Deduplicate NDA counterparties and maintain a master index in Airtable

After a signed NDA is logged, normalize the counterparty name, check it against the master counterparty table in Airtable.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew NDA record created in AirtableAirtableAirtable
  • ActionNormalize counterparty name into canonical match keyOpenAI
  • ActionSearch master counterparty table for existing matchAirtableAirtable
  • LogicBranch on whether a matching counterparty exists
  • OutputLink NDA to existing or newly created counterpartyAirtableAirtable

What it does

Keeps your counterparty index honest. When a new NDA record is created, this workflow normalizes the company name (stripping suffixes like Inc., LLC, Ltd.), searches your master counterparty table, and links the NDA to the right entity instead of spawning duplicate "Acme" and "Acme, Inc." rows.

When to use it

Use it once your NDA register grows past a few dozen entries and the same companies start appearing under slightly different names. It turns a messy list into a clean entity graph you can trust for renewals and conflict checks.

How it works

  1. 1A new NDA record in Airtable triggers the run.
  2. 2A model normalizes the raw counterparty string into a canonical legal name and a stripped match key.
  3. 3The workflow searches the master counterparty table for an existing match on the key.
  4. 4A branch decides: if a match exists, link the NDA to that counterparty; if not, take the create path.
  5. 5On the no-match path it creates a new counterparty record, then links the NDA to it as the final indexed result.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.