This tutorial shows how to streamline contract signatures by integrating SignatureAPI with Microsoft Forms, Power Automate, OneDrive, Dataverse, and Outlook.
{{employee.first_name}}
.
SignatureAPI replaces these fields with actual values when generating the document.
Learn more about document templates.
Placeholders
Placeholders mark where recipients should sign or enter information during the signing process. These are identified by double square brackets, for example: [[employee_signature]]
.
Learn more about placeholders.
In this tutorial, we will:
{{employee.first_name}}
{{employee.last_name}}
{{employee.email}}
[[employer_signature]]
[[employee_signature]]
[[salary_input]]
employer
. You’ll reference this key when assigning signature places.employee
.key: value
format.{{employee.first_name}}
with the value “Richard Roe”, set the item as employee.first_name: Richard Roe
.
You can use dynamic content from earlier steps to set values for each template field.
[[employer_signature]]
to indicate where in the document the employer will sign.
Now, add a Signature place to the document and associate this placeholder with the employer. Use the placeholder key employer_signature
to identify the place in the document and the recipient key employer
to identify the recipient.
employer_signature
.employer
, matching the recipient key you set earlier.[[salary_input]]
placeholder in the document with the employer.
To access this value programmatically and add it to the Dataverse table later, capture this value by setting the Capture As field (in advanced parameters). Learn more about captured values.
salary_input
.employer
, as before.salary_input
. This allows you to retrieve this value later in the flow.employee_signature
.employee
, matching the recipient key you set for the employee.salary_input
)..pdf
..pdf
) and set the Content field to the File Content from the Get a deliverable action.