DOCUMENT OPS
E-sign completion webhook to archive and database
Fires when an e-signature platform reports a contract fully executed, archives the signed PDF to S3, extracts the final terms.
How it runs
The automated pipeline, trigger to output.
- TriggerE-sign completion webhook receivedHTTP webhook
- LogicConfirm envelope is fully executed
- ActionArchive signed PDF to S3AWS S3
- ActionExtract final terms with OpenAIOpenAI
- OutputInsert executed record into PostgresPostgres
What it does
Closes the loop on signed contracts. When your e-sign provider posts a completion webhook, the workflow grabs the executed PDF, files it to durable storage, extracts the final agreed terms, and records them in a queryable database.
When to use it
Use this when contracts are signed through an e-signature platform that sends webhooks, and you need a permanent, reportable record of executed agreements separate from any UI. Ideal for finance and compliance teams that run analytics on signed paper.
How it works
- 1The e-sign platform posts a completion webhook, which fires the trigger.
- 2A logic step confirms the envelope status is fully executed and ignores partial or voided events.
- 3The signed PDF is downloaded and archived to an S3 bucket with a deterministic key.
- 4OpenAI extracts the final parties, value, and effective date from the executed copy.
- 5An insert writes an immutable executed-contract record to Postgres including the S3 archive path.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect AWS S3Buckets, objects, signed URLs.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect PostgresAny Postgres URL — query, write, migrate.
- 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.