DOCUMENT OPS

Kick Off a Signature Request When a Contract Lands in Dropbox

Watches a Dropbox intake folder, and when a new contract PDF appears, parses the counterparty email from a sidecar file, sends it for signature.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew file in Dropbox intake folderDropboxDropbox
  • LogicConfirm PDF plus matching signer sidecar exists
  • ActionRead signer email from sidecar metadataDropboxDropbox
  • ActionCreate signature request via provider webhookHTTP webhook
  • OutputLog new request as 'sent' row in AirtableAirtableAirtable

What it does

Lets your sales or ops team start a signing flow just by dropping a file. When a new PDF appears in a watched Dropbox "to-sign" folder alongside a small metadata file naming the signer, this workflow reads the signer details, initiates a signature request, and opens a tracking row so the document immediately enters your reminder and archival pipeline.

When to use it

Use it when non-technical teammates prepare contracts in tools that export to Dropbox and you want signing to begin without anyone logging into the e-signature app. Pairs naturally with the reminder and archive templates in this collection.

How it works

  1. 1A Dropbox folder-watch trigger fires when a new file lands in the intake folder.
  2. 2A filter confirms the file is a PDF and that a matching `.json` sidecar with signer name and email exists.
  3. 3The flow downloads the PDF and reads the sidecar to extract the counterparty's email.
  4. 4It posts the document and signer to your signature provider via an HTTP webhook to create the request.
  5. 5It creates an Airtable row with status "sent" and the sent timestamp as the final output.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DropboxFiles and folders.
  2. 2
    Connect HTTP webhookTrigger any URL on agent actions.
  3. 3
    Connect AirtableBases, tables, views, automations.
  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.