TriggerAdobe Acrobat Sign — When an agreement workflow is completed successfully
ConnectorsAdobe Acrobat Sign · SharePoint or Microsoft Dataverse · Data Operation
CategoryAcrobat Sign
The problem
Signers fill in fields (bank account, address, emergency contact) inside the agreement, but the data stays trapped in a PDF.
The outcome
Every completed agreement creates a row in a list, ready for Power BI or onward systems — no retyping.
Before you start
- Form fields in the Acrobat Sign template with clear names (e.g.
bank_name,account_no). - A SharePoint list with matching columns.
Build it step by step
- Trigger on completion — Use the Acrobat Sign completion trigger, filtered to the template or web form you care about.
- Get the field values — Add the Acrobat Sign action that returns form field data for an agreement (CSV format).
- Parse the CSV — Split the CSV into lines, take the header and first data row, and build an object. A simple approach: Compose the header row and value row, then Select to pair them.
Expression / setting split(body('Get_form_field_data'), decodeUriComponent('%0A')) - Create the record — Create item in SharePoint (or Add a new row in Dataverse) mapping each field.
- Mask sensitive values — Store only the last 4 digits of account numbers in the list; keep the full value only inside the signed PDF.
Expression / setting concat('****', substring(variables('accountNo'), sub(length(variables('accountNo')), 4), 4))
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
- Signers sometimes type commas in free-text fields — use a proper CSV parse (or the JSON form data endpoint via HTTP) for production volumes.
Licensing
- SharePoint target: standard. Dataverse target: premium (Power Automate Premium).
Variations
- Push the data to Dynamics 365 or your HR system instead of a list.
Common in: Banking · Insurance · Education