DOCUMENT OPS
Register a contract's baseline hash when it's sent for signature
When a finalized contract is filed to Dropbox for signing, computes and stores its canonical SHA-256 and signature fingerprint in a registry so later integrity checks have…
How it runs
The automated pipeline, trigger to output.
- TriggerNew PDF in Dropbox /contracts/outboundDropbox
- ActionCompute SHA-256 and signature-field fingerprintShell
- ActionUpsert baseline registry row keyed by contract IDPostgres
- OutputConfirm baseline locked in SlackSlack
What it does
Integrity checking is only as good as the baseline it compares to. This workflow establishes that baseline: the moment a finalized, pre-signature contract is placed in your outbound folder, it computes the canonical SHA-256 of the document and captures a fingerprint of its existing signature fields, then records both alongside the contract ID and counterparty in a registry. Later sentinel runs read this row to detect any post-send modification.
When to use it
Set this up first, before the verification workflows, so every outbound contract has a registered fingerprint. Run it on the version you consider the source of truth at send time.
How it works
- 1A new PDF in the Dropbox `/contracts/outbound` folder triggers the run.
- 2The file is downloaded and a shell step computes its SHA-256 plus a signature-field fingerprint.
- 3The workflow upserts a registry row in Postgres keyed by contract ID, storing both fingerprints and a timestamp.
- 4A confirmation with the contract ID and recorded hash is posted to the deal desk Slack channel so the team knows the baseline is locked.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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
Batch-narrate a Google Drive PDF folder in multiple languages
On a schedule, finds PDFs in a Google Drive folder that lack audio, then generates ElevenLabs narrations in each configured language and files them into per-language subfolders…
Executed Contract Exhibit & Initials Completeness Gate
When a signed contract lands in a Dropbox intake folder, verify every required exhibit, schedule, and initialed page is present.
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.
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Narrate new Dropbox PDFs into MP3 audio versions
When a PDF lands in a watched Dropbox folder, extract its text and generate an ElevenLabs voice narration.
On-demand PDF narration via webhook with emailed audio link
Accepts a PDF URL through a webhook, generates an ElevenLabs narration with the requested voice, stores the MP3, and emails the requester a download link.
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.