DOCUMENT OPS
Inbound email contract attachment to Salesforce
Catches signed contract PDFs that arrive as Gmail attachments, extracts the parties and terms.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Gmail email with contract PDF attachedGmail
- ActionRead attachment and extract terms with OpenAIOpenAI
- LogicMatch counterparty to Salesforce opportunitySalesforce
- ActionAttach summary and file to opportunitySalesforce
- OutputAlert Slack when no match is foundSlack
What it does
Monitors a Gmail inbox for incoming contract attachments, pulls the structured terms from each PDF, matches it to the right Salesforce opportunity by counterparty, and posts the summary plus the file there.
When to use it
Use this when signed agreements come back by email and reps have to manually find the opportunity, type in the terms, and upload the document. Best for sales teams running deals in Salesforce.
How it works
- 1A new Gmail message with a PDF attachment matching the contract filter fires the trigger.
- 2The attachment is read and OpenAI extracts counterparty, signed date, contract value, and term.
- 3A logic step looks up the matching open opportunity in Salesforce by counterparty name.
- 4If a match is found, the extracted summary is logged to the opportunity and the PDF is attached.
- 5If no match is found, a Slack alert flags it for manual linking so nothing is silently lost.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SalesforceAccounts, opportunities, cases.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Document Ops workflows
Flag redline deviations when a contract lands in Drive
Watches a Google Drive folder for incoming counterparty contracts, diffs each clause against your approved template library.
Gate contract signing on clause-deviation approval
When a contract is submitted for signature via webhook, diffs its clauses against approved templates and either auto-approves clean documents or holds them in Slack for explicit…
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
Log contract clause deviations to a Notion review register
On a daily schedule, scans a Drive contracts folder, diffs clauses against approved templates with OpenAI.
Weekly audit of clause drift across the contract repository
Each week, scans all executed contracts in Drive, measures how far each clause has drifted from approved templates.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.