top of page
DynamicDocs logo.png

Auto-generate documents directly from your board

Introducing DynamicDocs !

The way for you to auto-generate documents based on the content on your board 

DynamicDocs is a super powerful feature for your integration.

From template to eSignature in one click

  1. You create a document template and specify what type of content you wish to be automatically filled from the board and where you want it on the page

  2. OP.Sign fetches the content for you and creates a PDF, and ... 

  3. ... sends the document out for eSignature

Getting DynamicDocs to work on your documents is very easy and requires no change of the integration recipe.

A few notes on the DynamicDocs implementation

  • DynamicDocs work on docx, doc and Google docs. PDFs are currently not supported

  • DynamicDocs use the OP. Dynamic tag starting with {{ and ending with }}

  • The syntax for DynamicDocs within the document is {{ field name}} 

  • DynamicDocs are case sensitive

  • DynamicDocs require for a checkbox type field named Autocomplete to exist on the board and to be checked for the line/row we with to run it on

  • DynamicDocs support the following types of fields:

    • text

    • long-text

    • email

    • date

    • link

  • Each document can contain many DynamicDoc tags

  • DynamicDocs can work in parallel to the Signature Guides, creating a document that is both automatically generated and contains specifications of the places signatures and other data in required from the signer (more on Signature guides in this tutorial

Let's see how it's done

1. Create your board

In this example we'll be using a demo board called "Dynamic board". It contains real estate data for a fictional real estate company called the "Real Estate Demo Company Inc."

In addition to the fields required to run the OP.Sign integration (as described in this "Getting started" tutorial) we will add a few fields

1.1 A checkbox type field called Autocomplete
This is required in order to run DynamicDocs (note that field names are case sensitive)

DD 1.1.png

1.2 We have also created three optional fields for the purpose of the demo. 
We named them:

  • A text type field  - Tenant name

  • A text type field  - Property address

  • A text type field  - Rental price

  • A date type field - Date

You can add as many fields as you wish and name them however suits you.

Just make sure you populate them in the board with values and add them to your document template.

Which is exactly what we'll do next... 

2. Create a new document template

DynamicDocs work on Docx, Doc and Google docs.
I'll create a new document called "Demo Rental Agreement".

In this simple document I'll add the following tags - corresponding to the field names created in the previous step

  • {{Tenant name}}

  • {{Property address}}

  • {{Rental price}}

  • {{Date}}

DD 2.png

Notice that for demo purposes, I added the {{Tenant name}} tag to two location in the page and that the {{Rental price}} tag has a $ prefix. As your template is a Word or a Google doc, there is no limit to the times you add a tag to the document or to the prefixes and suffixes you can add to any tag.

The demo document also contains the {{Signer:1}} tag, which is a Signature guide and tells the signer exactly where his.her signature is required (Signature guides tutorial).

3. Create a new line in your board
Give it a name you'll remember like "DD Test #1",

DD 3.png

Complete the required data (as described in detail in the Getting started tutorial)

and send it our for signatures. The first to get it will be Signer:1 (the first email address specified in the signer field)

4.  Sign the document


As detailed in the Test your integration page, 
Open your mailbox and locate the incoming message from "OP.Sign App", click on the "Review and sign" button, enter your name and click Next

Let's see what the document contains:

DD 4.png

We can see that all the tags were replaced with the values in the fields in the line we created in the previous step,

The Tenant name (Boney M.) appears twice, the address is where it should be and the date was entered correctly. 

(In addition, the {{Signer:1}} tag generated a Signature guide, marked by a yellow dot).

The document was automatically generated and sent out for signature.

Mission accomplished!

5. Start working

Now you can apply Signature guides to your OP.Sign documents within your boards.
good luck and happy signing!

For any issues or questions, please send us a note to with the words "Using OP.Sign with" in the title and describe the issue you encountered.

We're here to help!

That's it!

We're done!

bottom of page