Collecting, organizing, and sharing data amongst your team can be a difficult task, but when you have a tool like Smartsheet, the process is drastically improved.  Much like a spreadsheet, you can easily save information and share it with your team members, but you can also reference other sheets and more advanced features.

In this example, we’re going to show you how you can automatically generate a non-disclosure contract for customers that we add to one of our Smartsheet sheets.  This contract will also be automatically sent over to CudaSign, so that the customer can sign it.

To get started, we’re going to setup the template for our NDA using a Microsoft Word document.  This contract looks like any other NDA, except we’re going to add merge fields where we want our customer’s information to go.  These merge fields are just text that you type in the document and look like {$FirstName}, {$Address}, etc.

Here’s what our NDA template looks like:

Since we’ll be collecting a signature via CudaSign, we need to add a signature tag to the document so that the signature is placed in the correct spot on the document.  You can do that with a tag like this (more info): {literal} {{t:s;r:y;o:"Signer";}} {/literal}

Once we have our template ready to go, we need to upload it to WebMerge.  From the Documents page in WebMerge, click the New Document button then type in a name for the document.  On the next step, you’re going to pick Office Document, then choose the file from your computer.

After you upload the document, you’re going to be taken to the Settings tab where you can modify options like the type of file that is produced and the name of the file.  For this example, we’re going to generate a PDF and then include the name of our customer in the name of the file.

Next, we’re going to setup the delivery of our document to CudaSign so that it will automatically be sent out for signature.  From the Deliver tab, click the New Delivery button then pick CudaSign from the list.  You’ll have to login to your CudaSign account to authenticate WebMerge to send documents to your account.

After you’ve logged into CudaSign you’ll be taken back to WebMerge where you’ll see the delivery settings.  You’ll need to define the subject of the email that the signer receives and then who the signer is.

Once you save the CudaSign delivery, we’re all done with the setup in WebMerge!  To help with the integration to Smartsheet, we’re going to use our friends over at Zapier.

Inside Zapier, go ahead and create a New Zap and for the Trigger service you’re going to pick Smartsheet.  For the trigger, you’re going to choose New Row.

Next, Zapier will have you authenticate your Smartsheet account and then they’ll have you pick the sheet that you want to monitor.  In our case, we’re going to monitor the New Customers sheet.

After you’ve finished the trigger setup, we’re going to pick WebMerge as the action service and then Create Document Merge as the action.

After you’ve authenticated your WebMerge account, Zapier will load a list of the documents that are in your WebMerge account.  Go ahead and pick the contract that you just setup and then Zapier will load a list of the merge fields in that document.

For each of the merge fields, you’ll need to pick the corresponding Smartsheet field. This tells Zapier how to send the Smartsheet data over to WebMerge so that it goes to the right spot in your template.

Once you’ve mapped all of the fields, go ahead and finish the zap and turn it on.  Now we’re ready for a test!  Log into Smartsheet and enter a new customer into your sheet.  Zapier will then detect that you’ve added a new row and it will send that data over to WebMerge, the contract will be generated, then sent out for signature.

Here’s what our contract looked like waiting for signature:

Congrats, you’re all done!  You can now automatically populate all kinds of documents from your Smartsheet account.  Can you think of any other ways that you could use WebMerge to streamline your paperwork process?


Signature and  Field Tags

CudaSign also has the ability to embed fields and place signature box in specific locations using Field Tags.  This is simply text that is in your documents that is detected by CudaSign and turned into a field.

For example: {{t:s;r:y;o:"Signer";}}     (documentation below)

If you are using the online document builder or any of the office documents, you will need to wrap the field tags in {literal}{/literal} tags so that the brackets do not interfere with WebMerge merge field tags.   Any code inside the literal tags is ignored by WebMerge

For example: {literal} {{t:s;r:y;o:"Signer";}} {/literal}


Here is the full documentation from CudaSign, which can also be found at

The order in adding the test tags is:

KEY What does it mean? Accepted format & values When fields need this KEY?
t TYPE of the field

s (for signature)

i (for initials)

t (for text)

d (for dropdown)

For every field

y (for required)

n (for optional)

For every field
o ROLE "<role name>" For every field
l LABEL "<label of this field>" Only for Text and Drop down fields
dd DROPDOWN "option1, option2, option2, ...." Only for Drop down fields
f FILE "<filename>.pdf" File attachment

The full set looks like the following:


  1. To create a  field of TYPE signature, with required REQUIREMENT, and ROLE 'Signer'
  2. To create a Field of TYPE Text, with optional REQUIREMENT, with ROLE 'Signer', and with LABEL "notes":
  3. To create a Field of TYPE Initial, with optional REQUIREMENT, and ROLE 'Signer':
  4. To create a Field of Type Drop down, with required REQUIREMENT, with ROLE 'Employee', with LABEL 'Date', and with DROPDOWNS '2012,2013,2014':


Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk