This tutorial shows how to streamline contract signatures by integrating SignatureAPI with Microsoft Forms, Power Automate, OneDrive, Dataverse, and Outlook.
This tutorial guides you through automating the employment contract process using SignatureAPI integrated with Microsoft tools such as Forms, Power Automate, OneDrive, and Dataverse.
You will build an automated workflow that begins when a new employee submits a form. The flow generates a personalized contract, sends it for signing using SignatureAPI, captures any information filled during signing, and stores the results automatically. HR is notified when the process is completed.
Sign up for a free account to get your test API key. Use it to generate non-binding envelopes and test your integration with SignatureAPI.
The flow follows these steps:
Here’s what your final Power Automate flow will look like:
Begin by preparing your employment contract template in DOCX format. This template is used to generate personalized contracts.
You need to add two types of annotations to your document: template fields and placeholders.
Template Fields
Template fields insert data into the document before it is sent to recipients. These fields are marked with double curly brackets, for example: {{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:
To prepare your template:
{{employee.first_name}}
{{employee.last_name}}
{{employee.email}}
[[employer_signature]]
[[employee_signature]]
[[salary_input]]
We use Microsoft Forms to collect employee details such as name and email address.
We will store employee details in a Dataverse table.
Now that you have the contract template, the form, and the Dataverse table set up, create a Power Automate flow that runs whenever someone submits the form.
Set up the flow trigger so it runs when a new form response is submitted.
Get the details submitted by the employee.
Fetch the contract template stored in OneDrive.
In SignatureAPI, an Envelope is a container that holds one or more documents to be sent to recipients. It defines and manages the signing process for those documents.
Start by creating the envelope in your flow:
Add the first recipient — the employer.
employer
. You’ll reference this key when assigning signature places.Add the second recipient — the employee.
employee
.Next, add your contract template to the envelope and populate it with employee data.
key: value
format.For example, to fill the field {{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.
When preparing the template, you set a placeholder [[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.In a similar way, add a Text Input Place to link the [[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.As you did for the employer, add a Signature Place for the employee.
employee_signature
.employee
, matching the recipient key you set for the employee.This step indicates the envelope is ready to be sent for signing. At this point, the envelope is fully assembled and sent to recipients.
Use the Wait for envelope action to pause the flow until all recipients have signed the document.
At this point in the flow, recipients have signed, the envelope is completed, and the deliverable (the signed document) is generated.
You can now retrieve the captured value from the salary input field the employer filled during the signing ceremony.
salary_input
).Now, add a row to the Dataverse table using the employee details and the captured salary amount.
In SignatureAPI, the deliverable is a PDF containing the signed documents and the audit log. See an example of a deliverable. Retrieve the deliverable so you can save it later.
Now, save the signed contract to OneDrive.
.pdf
.Finally, notify HR that the contract was signed and attach the signed document.
.pdf
) and set the Content field to the File Content from the Get a deliverable action.Test the entire process end-to-end.
In this tutorial, you learned how to use SignatureAPI together with Microsoft Forms, Power Automate, OneDrive, and Dataverse to automate the employment contract process. You saw how to fill a document template, add signature and input fields, and send documents to recipients for signing.
You also learned how SignatureAPI captures additional data from recipients, tracks the status of the envelope, and provides a signed deliverable once the process is completed. The tutorial showed you how to automatically save signed contracts and employee details, streamlining your workflow.
With these steps, you can now use SignatureAPI to manage and automate other document signing processes in your organization.
Happy Automating!
This tutorial shows how to streamline contract signatures by integrating SignatureAPI with Microsoft Forms, Power Automate, OneDrive, Dataverse, and Outlook.
This tutorial guides you through automating the employment contract process using SignatureAPI integrated with Microsoft tools such as Forms, Power Automate, OneDrive, and Dataverse.
You will build an automated workflow that begins when a new employee submits a form. The flow generates a personalized contract, sends it for signing using SignatureAPI, captures any information filled during signing, and stores the results automatically. HR is notified when the process is completed.
Sign up for a free account to get your test API key. Use it to generate non-binding envelopes and test your integration with SignatureAPI.
The flow follows these steps:
Here’s what your final Power Automate flow will look like:
Begin by preparing your employment contract template in DOCX format. This template is used to generate personalized contracts.
You need to add two types of annotations to your document: template fields and placeholders.
Template Fields
Template fields insert data into the document before it is sent to recipients. These fields are marked with double curly brackets, for example: {{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:
To prepare your template:
{{employee.first_name}}
{{employee.last_name}}
{{employee.email}}
[[employer_signature]]
[[employee_signature]]
[[salary_input]]
We use Microsoft Forms to collect employee details such as name and email address.
We will store employee details in a Dataverse table.
Now that you have the contract template, the form, and the Dataverse table set up, create a Power Automate flow that runs whenever someone submits the form.
Set up the flow trigger so it runs when a new form response is submitted.
Get the details submitted by the employee.
Fetch the contract template stored in OneDrive.
In SignatureAPI, an Envelope is a container that holds one or more documents to be sent to recipients. It defines and manages the signing process for those documents.
Start by creating the envelope in your flow:
Add the first recipient — the employer.
employer
. You’ll reference this key when assigning signature places.Add the second recipient — the employee.
employee
.Next, add your contract template to the envelope and populate it with employee data.
key: value
format.For example, to fill the field {{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.
When preparing the template, you set a placeholder [[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.In a similar way, add a Text Input Place to link the [[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.As you did for the employer, add a Signature Place for the employee.
employee_signature
.employee
, matching the recipient key you set for the employee.This step indicates the envelope is ready to be sent for signing. At this point, the envelope is fully assembled and sent to recipients.
Use the Wait for envelope action to pause the flow until all recipients have signed the document.
At this point in the flow, recipients have signed, the envelope is completed, and the deliverable (the signed document) is generated.
You can now retrieve the captured value from the salary input field the employer filled during the signing ceremony.
salary_input
).Now, add a row to the Dataverse table using the employee details and the captured salary amount.
In SignatureAPI, the deliverable is a PDF containing the signed documents and the audit log. See an example of a deliverable. Retrieve the deliverable so you can save it later.
Now, save the signed contract to OneDrive.
.pdf
.Finally, notify HR that the contract was signed and attach the signed document.
.pdf
) and set the Content field to the File Content from the Get a deliverable action.Test the entire process end-to-end.
In this tutorial, you learned how to use SignatureAPI together with Microsoft Forms, Power Automate, OneDrive, and Dataverse to automate the employment contract process. You saw how to fill a document template, add signature and input fields, and send documents to recipients for signing.
You also learned how SignatureAPI captures additional data from recipients, tracks the status of the envelope, and provides a signed deliverable once the process is completed. The tutorial showed you how to automatically save signed contracts and employee details, streamlining your workflow.
With these steps, you can now use SignatureAPI to manage and automate other document signing processes in your organization.
Happy Automating!