Collect e-signatures for your Formstack Documents with the use of Formstack Sign or third-party applications like OneSpan Sign.
How does this work?
Step 1: Generate a document. In the template include the signature tag(s): {literal}{{esl:signer1:signature}}{/literal}
Note: Including the {literal} tags on the side helps prevent validation errors during the merge process.
Step 2: Upload template into Formstack Documents. From the Documents page in Formstack Documents, select the New Document button and enter a name. in the next step, choose Office Document as the document type and then pick the file from your computer.
Modify options like name and file extension within the Settings tab.
Step 3: Set up delivery to save in OneSpan. On the Deliver tab, select the New Delivery button and select OneSpan from the list.
To authenticate OneSpan, enter the API key. If you don’t already have merge fields in your template, choose <
Step 4: Set up integration with a CSM tool. For example, if you are using OneSpan to close deals you may use tools like Pipedrive.
Use the webhook builder for Pipedrive: https://www.webmerge.me/scripts/pipedrive. Then inside Pipedrive use the generated webhook URL and install the webhook for when a deal is updated. This will trigger the webhook when a deal is marked as won.
Step 5: Test to ensure all fields populate. Update a deal and mark as won. This expected result is the webhook will trigger to send data over to Formstack Documents and your contract will be generated and sent to OneSpan Sign.
NOTE: To delay other deliveries until the document is signed (ie only send the signed document to other deliveries), you can turn on the Delay Other Deliveries under More Options in your OneSpan Sign delivery, then check the box next to each delivery you want to delay.