DOCUMENT OPS

Match each new contract's counterparty to the Attio CRM and link the record, creating it if new

When a contract is filed, extracts the counterparty name, searches Attio for a matching company, links the contract to that CRM record.

CategoryDocument Ops
Enginesim
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew page in Notion contract registerNotionNotion
  • ActionExtract and normalize counterparty nameOpenAI
  • ActionSearch Attio for matching companyAttio
  • LogicBranch on match vs no match
  • OutputLink contract to existing Attio recordAttio
  • ActionCreate new Attio company when no matchAttio

What it does

Keeps contracts and your CRM in sync. For every newly filed contract it resolves the counterparty against Attio, dedupes against existing companies, and attaches the contract to the right account record so sales and legal see the same source of truth.

When to use it

Use this when contracts get filed in Notion but never get tied back to the company in your CRM, leaving account owners unaware of active agreements. It makes every contract visible from the company record.

How it works

  1. 1A new page in the Notion contract register triggers the run.
  2. 2OpenAI extracts and normalizes the counterparty legal name from the contract metadata.
  3. 3Attio is searched for a company matching the normalized name and domain.
  4. 4A logic branch handles match vs no-match.
  5. 5On a match, the contract details and Notion link are attached to the existing Attio company record.
  6. 6On no match, a new Attio company is created and then linked, so the next contract resolves cleanly.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect NotionPages, databases, comments.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect AttioReal-time CRM with structured data + powerful views.
  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.