Today we’ll outline DocuSign integration with TeamDesk. An embedded eSignature is a vital option that helps streamline e-signing documents generated by your online database. Signing documents electronically allows to establish completely paperless legal procedures, as long as eSignature provider credibility is widely recognized.
The following sample database demonstrates an eSignature integration mechanism that may be implemented in your database. Let’s explore this mechanism and make it work for you.
Please follow the link below to explore the DocuSign Integration template:
As integration relies on DocuSign eSignature API, first thing you’ll need is to register DocuSign Developer Account.
From DocuSign Account Overview page please note API Account ID (1) and Account Base URI (2). Then add an app (3)
When app is added, please note Integration Key (4), Secret Key (5) and add https://www.teamdesk.net/secure/oauth.aspx to Redirect URI list (6). If you are running on custom domain, please correct URL accordingly.
Ok, now in the database, visit Setup | Database tab | Database section | Variables and fill in DocuSign API Account ID and DocuSign Account Base URI variables with values copied from (1) and (2) respectively. Let’s go back to Database tab | Tools section | 3rd-Party Accounts | DocuSign Signature copy (4) into Client ID and (5) into Client Secret. Click Authorize button. Then Save button.
Ok, we are ready to go!
What’s in the database?
There is a People table that acts merely as an address book. Add some test entries there. But all the hard work revolves around Documents table.
Let’s add new Document record. Upload the document you want to sign and select signers. Add a subject and a body for e-mail message, save. Then, click Send to Sign button.
Wait until document is signed.
Behind the scenes there is a DocuSign e-Signature API’s Create Envelope method. When you click Send To Sign, we pack the document, list of signers, and subject and message into envelope and send it to DocuSign using Call URL action. While, for demonstration purposes we keep the sample as simple as possible, there are tons of other options, feel free to tweak them according to your needs.
On our side there is a webhook listening to the notifications about the changes in envelope status. We are handling four types: recipient signed/declined and envelope signed/declined. First two update the status of the signer. Latter two update the status of the document. Once document’s status is set to Completed it’s time to download signed document via another Call URL action.
Please note, webhook URL is passed to Create Envelope method, so webhook does not need any kind of special registration in order to let it work.