DOCUMENT OPS

Sync signed-contract terms to Salesforce when e-sign completes

Receives an e-signature completion webhook, retrieves the executed PDF, diffs it against the draft on the opportunity.

CategoryDocument Ops
Enginepaperclip
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerE-sign completion webhook receivedHTTP webhook
  • ActionFetch executed PDF and draft from DropboxDropboxDropbox
  • LogicExtract final terms and diff clauses against draft
  • LogicSet change flag if material differences found
  • OutputUpdate Salesforce opportunity with final terms and verdictSalesforce

What it does

When an e-signature platform fires its completion webhook, this workflow fetches the executed PDF, compares it to the negotiated draft attached to the opportunity, and pushes the final terms back onto the Salesforce record. If clauses changed between draft and signature, it sets a 'changed at signing' flag so the deal isn't closed on stale terms.

When to use it

Use it to keep CRM in lockstep with what was actually signed, especially when reps negotiate in docs but close in Salesforce. It prevents booking revenue against terms that shifted in the final version.

How it works

  1. 1An e-sign completion webhook triggers the run with the contract and opportunity IDs.
  2. 2The workflow pulls the executed PDF from Dropbox and the draft stored on the opportunity.
  3. 3An agent extracts final terms and diffs the clauses against the draft.
  4. 4If material changes exist, it marks the opportunity's change flag and notes the altered clauses.
  5. 5It updates the Salesforce opportunity with final terms and the diff verdict.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect DropboxFiles and folders.
  3. 3
    Connect SalesforceAccounts, opportunities, cases.
  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.