Integrate DocuSign with Nintex DocGen
Before the DocuSign delivery option can be used, you need to add and configure DocuSign as an integration and select the authorization method you are going to use.
In order to integrate DocuSign for use as a delivery option in Nintex DocGen, the following requirements must be met:
-
DocuSign must be added as an integration in Nintex Admin
-
DocuSign must be authorized to work with Nintex DocGen. Refer to Add and authorize DocuSign as an integration
-
Envelope Status needs to be configured for use with the DAL delivery option in Salesforce Lightning. Refer to Configuring Envelope Status to update when using a DocuSign delivery option in Salesforce Lightning
Add and authorize DocuSign as an integration
Important: Each Salesforce Org you manage (Production, Developer, Sandbox, Scratch) also needs to be authorized and set up with an integration. It is highly recommended to do whatever testing your organization requires before updating each Salesforce Org.
There are several ways to authorize DocuSign for use with Nintex DocGen, and depending on the use case may determine what type of authorization you plan on using. Review the table below to determine which type of authorization to use and then refer to each of their individual topics for more information on how to configure each authentication method with Nintex DocGen.
Available authorization methods for DocuSign:
| Authorization Option | Description |
| OAuth - Admin Consent |
The standard authentication method for the delivery option. Before the DocuSign delivery option can be used, you need to add and configure DocuSign as an integration and select the authorization method you are going to use. This method requires DocuSign Admin Tools to be able to claim a domain. It may also ask for Admin Consent approval when adding this setting for the first time. Allows for a single DocuSign Admin Tools administrator to authorize all users under a single DocuSign account. No action is required on the part of the end-users side once Admin Consent has been configured. Every call made to DocuSign is authorized by a single administrative user but done in context of the user sending out the DocGen Package.
|
| OAuth - Individual Consent |
Allows a user to make a one-time authorization to DocuSign limited to that user's account. Each user that needs to run a DocuSign delivery option for a DocGen Package will need to authorize their account. During set up of OAuth - Individual Consent admins can send out a URL that user's can use to authorize their account prior to sending out a Document Package. User's can also authorize their account by clicking the Authorize and Send to DocuSign button. This authentication method is also available for the Legacy DocuSign delivery option.
|
| Legacy Authentication (Legacy) | The standard authentication method for Legacy versions of DocuSign. DocuSign has since deprecated their legacy authentication options, and this option can no longer be used. If you were previously using this option you will need to switch to either OAuth - Admin Consent or OAuth - Individual Consent. |
| Send on behalf of (SOBO) (Legacy) | Used for prompting the user for a login to DocuSign, used for the Legacy versions of DocuSign. DocuSign has since deprecated their legacy authentication options, and this option can no longer be used. If you were previously using this option you will need to switch to either OAuth - Admin Consent or OAuth - Individual Consent. |
Troubleshooting DocuSign integration issues
If you are experiencing issues when trying to set up DocuSign integration or experiencing issues during run or design time using the DocuSign delivery option, refer to our DocuSign Troubleshooting guide.
Some common issues are
Authorization errors
When setting up the DocuSign integration there is a chance you may encounter errors that you can troubleshoot.
If you receive an error, refer to the Authorization issues section.
Envelope Status not appearing
If you are using Envelope Status on one of your page layouts, you should start seeing information related to packages after sending out of a package using DocuSign. If you do not see any information in the Envelope Status section, the most common cause is that Salesforce is not properly connected to your instance of the DocuSign Salesforce app.
For more information on how to connect Salesforce to DocuSign, see Troubleshooting DocuSign Issues.
Users are being prompted to log in to DocuSign and authorize their account when trying to use the DocuSign delivery option
DocuSign has deprecated their legacy authentication methods, and some of the previously available authentication methods are no longer available for use. If you are using OAuth - Individual Consent, users will need to authorize their DocuSign account to use the DocuSign delivery option when they go to access Document Custom Fields or when trying to use the Authorize and Send to DocuSign button. For more information on OAuth - Individual Consent, refer to Add and authorize DocuSign as an integration
After enabling OAuth - Indvidual Consent, DocGen Packages connected to automated processes are no longer being sent
If DocGen Packages configured for use with automated workflows or the autosend function no longer send out documents after switching to OAuth - Individual Consent, the most common cause for this issue is that the user who is trying to use Autosend or the Service account has not been authorized for DocuSign. For more information on authorizing an account, refer to Authorize a service account or individual users for OAuth - Individual Consent. You can check to see if a user is authorized for use with DocuSign by checking the Connected Apps section in the user's DocuSign account.