Using a tool like ClinchPad to manage your sales process can be a great way to keep your entire team on the same page and closing deals.  Add Formstack Documents to your sales process and you can instantly populate all kinds of documents from ClinchPad like quotes, contracts, proposals, and more.

In this example, we’re going to show you how to automatically populate a contract when we move a deal to the Send Contract stage and then instantly send the contract over to eversign for e-signature.

To get started, we’re going to setup the template for our contract using a Word document.  Inside Word, we’re going to add our logo, contact info, and boilerplate contract details.  For the spots that you want to insert the customer / deal info, you’ll use merge fields that look like {$Name}, {$DealAmount}, etc.

Here’s what our template looks like:

Since we’ll be sending out contract over to eversign for signature, we need to insert a signature tag in the document so that eversign knows where to place the signature.  This tag is text like any other field and looks like:  [sig|req|signer1]

Once we have our template ready, we need to upload it to Formstack Documents.  From the Documents page in Formstack Documents, click the New Document button.  Enter a name and then on the next step, choose Office Document as the document type then select the file from your computer.


After you’ve uploaded your contract template, you’ll be taken to the Settings page where you can modify various options like the type of file that is generated and the name of the file.  For this example, we’re going to create a PDF and include the name of our customer in the merged contract name.

We’re also going to turn on Debug Mode so that we can see the data that’s coming over from ClinchPad (more on this later).


Next, we’re going to setup the delivery of our document so that it is automatically sent over to eversign.  Under the Deliver tab, click the New Delivery button and select eversign from the list.  Once you authenticate your eversign account, you’ll need to pick the merge fields you want to use for the signer’s name and email address.

If you don’t have a field in your document for the name/email address, select <<Other>> from the dropdown then enter something like {$Email} in the box.


Once you have saved your eversign delivery, we are done with the setup process inside Formstack Documents and we’re ready to integrate with ClinchPad.  To help with the integration, we’re going to use our friends over at Zapier.

Inside Zapier, we’re going to create a New Zap.  For the trigger, we’re going to choose ClinchPad as the app, then New Lead as the trigger.


Once you authenticate your ClinchPad account, Zapier will load a test lead to make sure everything is working correctly.

Next, we’re going to create the Action of our zap.  For the app, choose Formstack Documents, then Create Document Merge as the action.


Once you’ve authenticated your Formstack Documents account, Zapier is going to load a list of the documents in your account.  Go ahead and pick your contract template that you just setup and Zapier will load a list of the merge fields in your template.

For each merge field, you need to pick the corresponding fields from ClinchPad.  This tells Zapier how to send your data over to Formstack Documents so that it is populated in the correct spot on your template.


Once you have matched up all of your merge fields, you are ready to test!  Turn your Zap on then add a new lead in ClinchPad and Zapier will send your lead info over to Formstack Documents and your contract will be populated and sent over to eversign for signature.

Here’s what our contract looked like ready to sign:

Congrats, you’re all finished!  You can now generate all kinds of documents from your ClinchPad account.  Can you think of any other ways you can use Formstack Documents to simplify your paperwork process?

Signature Tags

eversign allows you to embed signature tags in your document so that they know where to place signatures, initials, dates, etc in your document during signing. Below are a few examples. Click here for full documentation.

Signer 1 Signature [sig|req|signer1]
Signer 1 Date [date|req|signer1]
Signer 1 Text (optional) [text|noreq|signer1]
Signer 2 Signature [sig|req|signer2]
Signer 2 Initials [init|req|signer2]


Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.