Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Next »

You need a DocuSign Business Pro account to connect your company's DocuSign account to Sighten. If you do not have a Business Pro account with DocuSign, no problem! The connection will default to Sighten's DocuSign account. You don't need to connect your own.

If you do not have a Business Pro DocuSign account but have already inputted your credentials in the Integration settings in Sighten, please send an email to support@sighten.io so that we can revert your account to using Sighten's DocuSign.

In Sighten

First, get in touch with Sighten's support team through chat or at support@sighten.io so we can help arrange some settings on the backend.

You need to insert your DocuSign credentials in Sighten. To do so, click on the "menu" icon > Settings > Integrations and insert your DocuSign login and password in the appropriate fields.

If you do not see the DocuSign username and password fields in Settings > Integrations, please contact your Sighten account manager and send an email to support@sighten.io 


External Applications Integration

In DocuSign

Please have your account administrator log into your DocuSign account and follow the steps below to ensure completed DocuSign envelopes return to Sighten.

1. Log in as the admin account and go to Go to Admin by clicking on the top right nav

Go To Admin in DocuSign Account

2. Click on Connect under Account Administration in the bottom left of the screen

Connect in DocuSign

3. Click Add Configuration dropdown and select Custom:

Add Custom Configuration in DocuSign


4. Configure the Connection with the following, required elements:

  • Name:  This is name of the Connect configuration. The name helps identify the configuration in the list. 
    • Input: Engine
  • URL to Publish: This is the web address and name of your listener or Retrieving Service endpoint. You must include the protocol (HTTP: or HTTPS:) in the web address for Demo account. You must include HTTPS:// in the web address for Production accounts because SSL is required in Production. 
  • Enable Log: Select this option to enable logging for this configuration. It is recommended that you enable this option to facilitate troubleshooting any problems. If you do not want to enable logging for this configuration, clear this box. DocuSign will keep the last 100 log entries for all Connect configurations for the account. The log entries can be viewed by clicking Logs on the Connect page.
  • Require Acknowledgment: Select this option so that failed callbacks of documents are reattempted by DocuSign. What this means is that DocuSign will resend any callbacks that fail to reach Sighten. For example, if Sighten misses callbacks during release downtime, they will be resent as long as this is turned on.

  • Trigger Events - Envelope Signed/Completed: Select this option so that Sighten application is updated when the document or recipient actions are completed.

(Sample)

Example DocuSign Connection Settings

6. Click Add to save the configuration.

7. (Optional) Advanced settings - here are the descriptions for the options above.  If you have any questions, please don't hesitate to reach out.

  • Include Document PDFs: Select this option to have Connect send the PDF documents along with the XML update. If you do not want to receive the PDF documents with the updates, clear this box. 
  • Include Certificate of Completion: Select this option to have Connect include the Certificate of Completion with completed documents. If you do not want to receive the Certificate of Completion with the updates, clear this box.
  • Trigger Events - Additional Events: (Only relevant for Webhooks) Select the trigger events for updating your system. There are two categories of trigger events - Document Events and Recipient Events. The difference between document events and recipient events is that document events are only triggered when the document status changes, while recipient events are triggered each time information for a recipient change

Related articles

You might also want to check out these related topics:

  • No labels