Automatically generate documents from template and send to eversign for e-signing

This how-to guide describes a way to create a document from a template and send it for electronical signing to eversign.

We’ll create a sales contract in PDF from a Word template and will send to eversign using eversign delivery in Plumsail Documents processes.

As a result, we’ll get the sales contract electronically signed:

contract signed with eversign

To build the following automation, you need to have a Plumsail account. If you haven’t one yet, register to get a 30-day free trial.

Create new process

Go to the Processes section in your Plumsail account and add a new process. Then you’ll need to fill in the process name and select the template format. To stick to this guide, select DOCX:

create a new process

Configure document template

You have created the process and jumped into its first step - Configure template, consisting of two substeps:

  • Editor;

  • and Settings.

In Editor, you can compose document templates online, or upload pre-made ones and modify them in case of need.

Download the contract template we’ve prepared for this case and upload it to the process.

upload template file

Once you did it, you’ll see the template preview:

preview of document template

You may notice {{tokens}} in the document template. We highlighted a couple of them purple to attract your notice and describe how the templating syntax works.

Word DOCX templating syntax

Everything in {{curly braces}} is variables that the templating engine will replace by specified data. Also, in our template there are nested tags referring to products - {{}}, {{products.quantity}}, {{products.price}}, and {{products.cost}}.

They let the process know that we want to display properties from some object. In our example, it’s a collection of products. The templating engine will automatically understand that there are multiple products and create table rows for each of them.

nested tags in template

Find out more information on Plumsail Documents Word templates in the documentation.

Insert signing tags into the template

At the end of the sales contract template, we put special tags to define the location of signatures and other related fields for signers. You can’t see them as we’ve changed their font color to white.

These tags are from eversign; they ease the process of signing. Each signer will see where to place his signature and what fields are required to complete.

This is how tags look in the document template (we highlighted them black to make visible):

eversign signature tags

This is how they will appear for a signer:

eversign signature tags result 1

It’s easy to compose such signature tags. The logic is that they include a series of options in a specific order, divided with | symbol, and the whole tag is wrapped by [squire brackets].

For instance, the option going first is a field type. In our template, we have such types as sig (means signature), text, and date.

Learn more about using eversign signature and other related tags.

Test document template

You can test your template to check how the resulting document looks. For that, click the Test template button.

You’ll see a form with fields from your template tokens. You can adjust the default form. Find more information in the documentation.

Test template eversign

To test the contract template from our example, enter some data into the fields.


This is testing. You can pass data from an external system or web form to the process. See the Start process section.

Once you’ve tested the template, press Save&Next to proceed further - to the Settings substep.

Customize output file

On the Settings substep, you customize parameters of the output file.

Configure template
  • Mode. It affects whether the resulting file will have a Plumsail watermark or not. In Testing mode, it will, but you won’t pay for executions. In Active, it won’t have the Plumsail watermark; each process run will spend one credit.

  • Output filename. Use tokens from the document template to personalize the document name. They will work exactly the same way as in the template.

  • Output type. By default, it’s the same as the template. You can change it to PDF like we did.

  • Additionally, it’s possible to protect the resulting PDF file by a watermark or other security settings.

Send document to eversign for signing

Now it’time to set the process to send documents to eversign to collect electronic signatures. For that, we’ll add the eversign delivery.

add eversign delivery

Connect to your eversign account:

connect to eversign

After the connection between Plumsail and eversign accounts established, you’ll be able to customize the eversign delivery settings under your requirements.

Fill in the email subject and message. Here you can use tokens from the document template, too.

Add recipients. It’s possible to add as many as you need. Set their roles - either Needs to sign or Receives a copy. In our example, we have two recipients required to sign the document:

eversign general settings

To add an extra level of security, you can enable PINs for each signer. Click on the lock button, then set the PIN value.

set eversign PIN

Expand Advanced to customize more settings.

We enabled Sequential signing to set the strict order in which signers must sign the document. To change the order, drag and drop recipients.

And also, we enabled to Require all signers to sign to complete the document. If one of the signers rejects to sign, the document will be canceled.

eversign advanced settings

The eversign delivery is set. It’s possible to add as many deliveries as you need. Check out the full list of deliveries and how to set them.

Start process to generate documents and send them for signing

There are several ways of launching the process. We will start our process from the Plumsail web form.

Each form’s submission will trigger the process to create sales contracts and send them to eversign for signing.

Here is how our pre-made Plumsail form looks:

web form for sales contracts

Feel free to download the web form for creating sales contracts we have prepared. Then go to the Forms in your Plumsail account. Click on Create form, and you’ll move to a web designer of Plumsail Forms. There you can import the JSON file you’ve recently downloaded:

import form to web designer

Save, and that’s it - you have the required form.

We won’t go into much detail here on how to create Plumsail web forms. You can learn how to design web forms from the documentation.

Bind web form to process

Now you need to bind this web form to the process. On the step Start process, switch to a tab Web Form. Click on Bind form.

bind form to process

You’ll see the dialog with the dropdown showing all your Plumsail forms. Select the form for creating purchase agreements. Press Bind.

select form to bind

From now submissions of the bound form will launch the process. Submission data will populate the DOCX template, the process will convert it to PDF and will send it to eversign for digital signing.

Integrate with your services

It’s possible to trigger the process from your favorite services and pass their data to populate the template and send the result to eversign. For that, you can use such integration platforms as Zapier and Power Automate.

For instance, you can start the process of creating and sending contracts for eSignatures in eversign:

It’s just a couple of ideas out of many for you to get inspired. Find more in the integrations section.

Drop us a line to in case you encounter any difficulties or get any questions.