Customer application forms: Acrobat Sign web form → Dataverse → case created

Customers complete and sign an Acrobat Sign web form on your website; data creates a case or lead and documents are filed.

TriggerAdobe Acrobat Sign — When an agreement workflow is completed successfully (web form)
ConnectorsAdobe Acrobat Sign · Microsoft Dataverse · SharePoint
CategorySales & CRM

The problem

Application PDFs are downloaded, printed, filled, scanned and emailed back.

The outcome

A fully digital application: signed, structured data in Dataverse, and a case ready for processing.

Before you start

  • An Acrobat Sign web form embedded on your website.
  • A Dataverse table or Dynamics 365 Customer Service.

Build it step by step

  1. Trigger — Filter to the web form's agreements.
  2. Read form data — Get the form field data and parse it.
  3. Create the record — Add a new row (lead, case or custom application table).
  4. Attach documents — Save the signed PDF and audit trail; add a note or file column on the row.
  5. Acknowledge — Email the applicant a reference number.

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

  • De-duplicate by IC/passport number or email before creating a new contact.

Licensing

  • Dataverse is premium.

Variations

  • Use Power Pages for a logged-in portal experience and Acrobat Sign only for the signature step.

Common in: Insurance · Banking · Education