Power Automate workflow · Acrobat Sign

Turn a Microsoft Forms request into a signed agreement from a Word template

A form response fills a Word template, converts it to PDF and sends it for signature — no copy-and-paste.

TriggerMicrosoft Forms — When a new response is submitted
ConnectorsMicrosoft Forms · Word Online (Business) · OneDrive for Business · Adobe Acrobat Sign
CategoryAcrobat Sign

The problem

Staff retype the same names, IC numbers and amounts from emails into Word templates, then send them for signature manually. Typos slip into legal documents.

The outcome

Requesters fill a short form; the agreement is generated and sent in under two minutes with data exactly as entered.

Before you start

  • A Word template with content controls (Developer tab → Plain Text Content Control) named e.g. CustomerName, Amount, StartDate.
  • The template stored in OneDrive or SharePoint.
  • A Microsoft Form with matching questions.

Build it step by step

  1. Get the response — Trigger on the form, then Get response details to read each answer.
  2. Populate the template — Add Populate a Microsoft Word template. Each content control appears as a field — map the form answers. Format dates for Malaysia on the way in.
    Expression / setting
    formatDateTime(outputs('Get_response_details')?['body/rStartDate'], 'dd MMMM yyyy')
  3. Save the draft — Add Create file in OneDrive with a meaningful name, e.g. Agreement - @{CustomerName} - @{utcNow('yyyyMMdd')}.docx.
  4. Convert to PDF — Add Convert file (OneDrive) with target type PDF so the signer receives a locked layout.
  5. Send for signature — Upload the PDF to Acrobat Sign and create the agreement with the customer's email from the form.
  6. Confirm to the requester — Send the requester an email with the agreement name and the Acrobat Sign agreement ID for tracking.

Connector action names are shown as they appear in Power Automate at the time of writing; Microsoft and Adobe occasionally rename actions or add new versions.

Error handling

  • Validate required answers with a Condition before populating the template — an empty content control produces an agreement with blanks.
  • Wrap steps 2–5 in a Scope and add a failure branch that emails the requester and IT.

Licensing

  • Populate a Microsoft Word template is a premium action — the flow owner needs a Power Automate Premium (per-user) licence or the flow needs a Process licence.
  • Acrobat Sign licence for the sending account.

Variations

  • Replace Microsoft Forms with a Power Apps form for richer validation.
  • Use Adobe's Document Generation API instead of Word Online if you need complex tables or conditional sections.

Common in: Education · Hospitality · Retail · Healthcare