Send personalized contracts from Typeform to Adobe Sign

By General Input

When a prospect submits your contract request form, the right template goes out for signature with a personal cover note, and every send is logged in a sheet.

Integrations

  • Typeform
  • Adobe Acrobat Sign
  • Google Sheets

Type

Agentic Task

Categories

  • Sales
  • Operations

Whenever a prospect submits our contract-request Typeform (fields typically include name, work email, company, deal size, and contract type), automatically pick the right Adobe Acrobat Sign template, draft a personalized cover message, send the agreement out for signature, and log the send to Google Sheets.

Trigger: a Typeform webhook fires on every new submission. Use Typeform's Create or Update Webhook once during setup to subscribe our workflow endpoint to the specific form ID (tagged so re-runs update in place rather than duplicating).

On each submission, read the answers and decide which Adobe Sign library document template to use. The mapping between the contract-type answer and the library document ID must be human-configurable at the top of the workflow (for example: NDA -> libDoc_xxx, MSA -> libDoc_yyy, Order Form -> libDoc_zzz, with a default fallback). If the contract-type answer is ambiguous or missing, fall back to the default template and flag the row in the log so a human can review.

Draft a short, personalized cover message (2 to 4 sentences) that references the submitter's company, the specific contract type they asked for, and the deal size if provided. Keep the tone consistent with the sales team's voice, no em dashes, and never invent facts the form didn't provide.

If the Typeform submission includes any file uploads (for example an existing draft they want mirrored), download each file and Upload Transient Document to Adobe Sign to obtain transient document IDs, then attach them alongside the library document when creating the agreement.

Call Adobe Sign's Create Agreement with state IN_PROCESS so the agreement is sent immediately rather than saved as a draft. The submitter is the first (and typically only) signer, populated from the form's name and email fields. The agreement name should be something like '<Company> - <Contract Type>' and the cover message becomes the agreement's message body.

Finally, Append Values to a Google Sheets tab named 'Contracts Sent' with one row per agreement: timestamp, submitter name, company, email, contract type, template name used, Adobe Sign agreement ID, deal size, and a 'needs review' flag when the template was chosen by fallback. This gives the sales team a durable paper trail.

If any step fails (template lookup missing, Adobe Sign returns an error, Google Sheets append fails), log the failure to the same sheet with an error column populated so nothing is silently dropped.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentLocal listing health board for every location you manageLet support send one-off Loops emails without an engineerStop cold emails to anyone with a live deal in PipedriveiMessage campaign console with pre-flight checks and delivery boardLinkedIn Ads budget pacing dashboard for every client accountFront desk appointment confirmation board for the next 3 daysGive your team Looker numbers without buying more seatsBuild audience segments from product usage and push to LoopsTurn the people who engage with your posts into Pipedrive leads