DOCUMENT OPS

Email-attached contract triage with value-based approval routing

Parses contracts attached to inbound Gmail, extracts the deal value and key terms, and routes to the right approver tier in Slack based on contract value thresholds.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Gmail with contract attachmentGmailGmail
  • ActionExtract attachment textGmailGmail
  • ActionExtract deal value and terms with LLMOpenAI
  • LogicRoute to approver tier by contract value
  • OutputNotify the right approver in SlackSlack

What it does

Monitors a shared Gmail inbox for emails carrying contract attachments, reads each attached agreement, and routes it to the correct approver based on the contract's total value so small deals move fast and large ones get senior eyes.

When to use it

Use it when contracts arrive by email and your approval authority is tiered by dollar amount. Good for finance and sales-ops teams that need an automatic gate between a rep's deal and the right signer.

How it works

  1. 1A new Gmail message with an attachment in the contracts inbox triggers the run.
  2. 2The attachment text is extracted from the email.
  3. 3OpenAI pulls the total contract value, term length, and payment schedule.
  4. 4A logic step picks the approver tier: under 10k auto-approves, 10k to 100k routes to a manager, above 100k routes to the VP.
  5. 5The summary and required approver are posted to the matching Slack channel for sign-off.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  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.